unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Antoine Levitt <antoine.levitt@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 11350@debbugs.gnu.org
Subject: bug#11350: Nasty hangup
Date: Fri, 27 Apr 2012 15:52:33 +0200	[thread overview]
Message-ID: <87ehr9nuxq.fsf@gmail.com> (raw)
In-Reply-To: <83k412ip7m.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 26 Apr 2012 16:42:53 +0300")

26/04/12 15:42, Eli Zaretskii
>> From: Antoine Levitt <antoine.levitt@gmail.com>
>> Date: Thu, 26 Apr 2012 15:21:18 +0200
>> 
>> I'm seeing a very nasty bug, description below. I use bzr trunk and
>> update it quite regularly, but the last commits seem pretty harmless
>> ... the only change I can see in my environment is that I started using
>> org-clock today. The bugs happened when I was working, using python with
>> a comint interaction buffer.
>> 
>> So anyway, when it happens, I get 100% CPU usage, and emacs just
>> hangs. I can only get out of it by sending it a SIGUSR2. In which case
>> it gives out a useless backtrace (saying it's at top level, as if it
>> wasn't doing anything). Once I quit the debugger or access a python
>> buffer, it hangs again. The only solution I have is to kill it.
>> 
>> Sorry I can't provide more information, it only happens sporadically
>> (three times today ...)
>
> There's advice in etc/DEBUG about how to investigate "hangs".  (Search
> for "If the symptom of the bug is that Emacs fails to respond".)  If
> you could follow that advice and post here what you find, that would
> be valuable information.

Thanks for that. Should have thought of it before, I tend to get a bit
panicked when emacs hangs :) I haven't had this bug again, if I do I'll
attach a gdb and see.





  reply	other threads:[~2012-04-27 13:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-26 13:21 bug#11350: Nasty hangup Antoine Levitt
2012-04-26 13:42 ` Eli Zaretskii
2012-04-27 13:52   ` Antoine Levitt [this message]
2012-07-07  9:09     ` Chong Yidong
2012-07-07  9:11       ` Antoine Levitt

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.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87ehr9nuxq.fsf@gmail.com \
    --to=antoine.levitt@gmail.com \
    --cc=11350@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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.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).