[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] still seeing semi-regular lockups

From: Eric Abrahamsen
Subject: Re: [O] still seeing semi-regular lockups
Date: Thu, 15 May 2014 10:29:00 +0800
User-agent: Gnus/5.130012 (Ma Gnus v0.12) Emacs/24.4.50 (gnu/linux)

address@hidden writes:

> hi,
> on my machine wanderlust hangs from time to time when i am inside the company 
> net and
> the proxy has hiccups.
> then C-g (sometimes several) usually help.
> in the link below i found an interesting variable, debug-on-quit.
> when it is set, emacs enters the debugger when you hit C-g.

Whatever's going on here isn't network-related, it's pretty clearly
triggered by making editing changes to an org buffer. It's also
unsalvageable with C-g, or this whole thing would be much simpler!
There's an ongoing thread between Daimrod and Stephen that might
actually be the same issue, I'll check that out.

> sendings signal to emacs from external usually only kills it.
> the only signal which i am aware of that can be caught is SIGUSR1.
> i used to use it to notify emacs about network changes.

Good to know, thanks!

> hope this helps,
> dieter
> [1] 
> http://www.gnu.org/software/emacs/manual/html_node/elisp/Infinite-Loops.html#Infinite-Loops
>>---- Original Message ----
>>From: Eric Abrahamsen <address@hidden>
>>To: address@hidden
>>Sent: Wed, May 14, 2014, 10:36 AM
>>Subject: [O] still seeing semi-regular lockups
>>Hey there,
>>After Nicolas made the last round of improvements to the caching
>>mechanism I got far fewer hangs with Org, but they are still happening.
>>Maybe once a day or so, on average, editing something in an Org buffer
>>causes emacs to hang, and my fans to spin up, and there we are until I
>>kill emacs.
>>It happens often enough that I guess it's worth running emacs under some
>>kind of debugger -- at least, I assume that's the best way of catching
>>the bug. I'm not really sure how to go hunting, though, so if anyone had
>>any advice in this direction, that would be great.
>>In the meantime, is there any way of interrupting emacs so it quits
>>whatever its doing, without having to kill it? I've played around with
>>sending different signals using "kill", just for fun, but everything
>>I've tried either does nothing, or kills emacs altogether.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]