[O] bug#17055: 24.3.50; Emacs hangs in Org mode file
Perhaps this is fixed now, according to comments at: http://lists.gnu.org/archive/html/emacs-orgmode/2014-03/msg01176.html (It would be great if someone would keep an eye on these Org bugs that get reported to Emacs and update them when appropriate. Although it seems better to report Org bugs to the Org-mode list rather than to Emacs.)
[O] bug#17055: 24.3.50; Emacs hangs in Org mode file
Bastien wrote: > Eli Zaretskii writes: > >> I hope Org maintainers could take a good look on this. > > Yes, I think Nicolas is on it. > > Speaking of that, this is one of the few remaining bugs > we want to fix before 8.2.3, I hope we will have time to > merge 8.2.3 into the emacs-24 branch then. Regarding the "few remaining bugs we want to fix" part, I'd advocate trying to solve the following 2 bugs as well before merging back into Emacs: - #16440: Some colors of the theme aren't respected in latest Emacs - #15298: Background color lost when highlighting a string Best regards, Seb -- Sebastien Vauban
[O] bug#17055: 24.3.50; Emacs hangs in Org mode file
> Still no prompt but Emacs survived this infloop (not an infloop, then) > after I don't know how much time (but more than a couple of minutes). Then try to M-x profiler-start RET RET <... reproduce ...> M-x profiler-report RET And the C-u RET on the + to expand the display. Stefan
[O] bug#17055: 24.3.50; Emacs hangs in Org mode file
> From: Sebastien Vauban > Date: Fri, 21 Mar 2014 14:58:19 +0100 > > Sebastien Vauban wrote: > > Today, 2 to 3 new infloops when editing in Org (but that's one of the > > two things I do: either be in Gnus, or in Org). > > > > Org-mode version 8.2.5h (release_8.2.5h-818-g0de200) > > > > I did not have time to look at the first ones; I do for this one. > > > > $ gdb -p 9696 > > ... > > [Thread 9696.0x1710 exited with code 0] > > [Thread 9696.0x23c4 exited with code 0] > > [Thread 9696.0x1e08 exited with code 0] > > > > The weird thing, here, is that my Bash terminal is stuck: I did not see > > more than 2 threads, and I don't have any GDB prompt yet. RET'ing does > > not change anything... > > > > Session still open (but no GDB prompt!). > > Still no prompt but Emacs survived this infloop (not an infloop, then) > after I don't know how much time (but more than a couple of minutes). > > BTW, it outputted the message "Emergency (alloc): Warning: past 95% of > memory limit". I think this is a duplicate of 16832. The same function, org-mode-flyspell-verify, causes this, and the effect is the same: it takes Emacs a lot of time to get out of that processing, whatever it is. I hope Org maintainers could take a good look on this.