From: Stephen Berman <stephen.berman@gmx.net>
To: martin rudalics <rudalics@gmx.at>
Cc: 9006@debbugs.gnu.org
Subject: bug#9006: 24.0.50; Abort in unshow_buffer/kill-buffer
Date: Thu, 07 Jul 2011 11:32:29 +0200 [thread overview]
Message-ID: <871uy2qvv6.fsf@escher.fritz.box> (raw)
In-Reply-To: <877h7wxqjv.fsf@escher.fritz.box>
On Thu, 07 Jul 2011 10:23:51 +0200 martin rudalics <rudalics@gmx.at> wrote:
>> The Lisp backtrace shows vertical-motion being called just before
>> kill-buffer, which makes Emacs abort.
>
> I see.
>
>> I induced the abort again, under the same conditions as described above,
>> and got exactly the same backtrace. I'll leave the process running for
>> a few hours before I have to shut down the machine, in case anyone can
>> offer debugging suggestions.
>
> But did you observe the same sluggishness again this time and did you do
> the same things (delete text, type C-g)? How old was your Emacs session
> this time?
This time I wasn't editing but just moving around the buffer rapidly,
holding down keys like C-n, C-p, C-f, C-v etc. until Emacs didn't
respond anymore, then C-g, upon which Emacs aborted. The session was
not quite as old as the previous one, 9-10 hours. I had tried
unsuccessfully to induce the crash several times earlier in the session.
One thing that may play a role is that, when this induced abort
occurred, the machine was running another program that was consuming a
large amount of CPU cycles, which made Emacs (even more) sluggish
(though when the crash that prompted my OP occurred I wasn't running
that other program, yet Emacs was sluggish anyway). And indeed, I was
just able to induce the abort again with the same procedure: while
another CPU-intensive program was running, I moved point with C-n
etc. rapidly around in a Gnus buffer, until there was no response, hit
C-g (this time 3 times in succession; I can't remember if that was the
case with the other crashes), and Emacs aborted, with the same
backtrace. This time the session was 2-3 hours old. I then immediately
tried to induce the crash again with a fresh session under otherwise
identical conditions, but so far it hasn't crashed. If I do get another
crash, I'll leave the process running again.
Steve Berman
next prev parent reply other threads:[~2011-07-07 9:32 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 23:20 bug#9006: 24.0.50; Abort in unshow_buffer/kill-buffer Stephen Berman
2011-07-06 9:25 ` martin rudalics
2011-07-06 19:19 ` Stephen Berman
2011-07-07 8:23 ` martin rudalics
2011-07-07 9:32 ` Stephen Berman [this message]
2011-07-07 15:47 ` martin rudalics
2011-07-08 23:03 ` Stephen Berman
2011-07-09 8:44 ` martin rudalics
2011-07-09 11:57 ` Stephen Berman
2011-07-09 13:01 ` martin rudalics
2011-07-09 16:27 ` Stephen Berman
2011-07-09 16:54 ` Stephen Berman
2011-07-10 8:59 ` martin rudalics
2011-07-10 10:25 ` Stephen Berman
2011-07-10 13:30 ` martin rudalics
2011-07-10 20:31 ` Stephen Berman
2011-07-11 19:14 ` martin rudalics
2011-07-11 20:04 ` Stephen Berman
2011-07-12 8:36 ` martin rudalics
2011-07-12 8:51 ` Stephen Berman
2011-07-13 6:53 ` Stephen Berman
2011-07-13 7:24 ` Eli Zaretskii
2011-07-13 8:00 ` Stephen Berman
2011-07-13 10:03 ` Eli Zaretskii
2011-07-13 11:40 ` Stephen Berman
2011-07-13 8:37 ` martin rudalics
2011-07-13 10:05 ` Eli Zaretskii
2011-07-13 11:54 ` martin rudalics
2011-07-13 12:20 ` Stephen Berman
2011-07-13 11:39 ` Stephen Berman
2011-07-14 8:35 ` martin rudalics
2011-07-15 21:05 ` Stephen Berman
2011-07-10 8:58 ` martin rudalics
2011-07-09 12:44 ` Stephen Berman
2011-07-09 13:01 ` martin rudalics
2011-07-09 17:31 ` Eli Zaretskii
2011-07-10 8:59 ` martin rudalics
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871uy2qvv6.fsf@escher.fritz.box \
--to=stephen.berman@gmx.net \
--cc=9006@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.