emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Sebastien Vauban <sva-news@mygooglest.com>
Cc: 17055@debbugs.gnu.org
Subject: bug#17055: 24.3.50; Emacs hangs in Org mode file
Date: Fri, 21 Mar 2014 18:02:03 +0200	[thread overview]
Message-ID: <83ior75ymc.fsf@gnu.org> (raw)
In-Reply-To: <86ha6rd56s.fsf@somewhere.org>

> From: Sebastien Vauban <sva-news@mygooglest.com>
> 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.

  parent reply	other threads:[~2014-03-21 16:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.17749.1395401116.10748.bug-gnu-emacs@gnu.org>
     [not found] ` <86ha6rd56s.fsf@somewhere.org>
2014-03-21 16:01   ` bug#17055: 24.3.50; Emacs hangs in Org mode file Stefan Monnier
2014-03-21 16:02   ` Eli Zaretskii [this message]
2014-03-24 13:20     ` bug#16832: " Glenn Morris
2014-03-24 13:20     ` Glenn Morris
     [not found]     ` <o0ior368da.fsf@fencepost.gnu.org>
2014-04-08 17:20       ` bug#16832: " Glenn Morris
     [not found]       ` <mhioqjkaaa.fsf_-___12843.7314685018$1396977720$gmane$org@fencepost.gnu.org>
2014-04-09 15:38         ` Bastien
     [not found]   ` <83ior75ymc.fsf__18846.3120874532$1395419640$gmane$org@gnu.org>
     [not found]     ` <mailman.17773.1395420613.10748.bug-gnu-emacs@gnu.org>
     [not found]       ` <mailman.17773.1395420613.10748.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2014-03-21 20:09         ` bug#17055: " Sebastien Vauban

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83ior75ymc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=17055@debbugs.gnu.org \
    --cc=sva-news@mygooglest.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).