From: Andy Moreton <andrewjmoreton@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 12832@debbugs.gnu.org
Subject: bug#12832: 24.3.50; Emacs lockup when idle
Date: Fri, 09 Nov 2012 18:38:36 +0000 [thread overview]
Message-ID: <509D4DAC.1060901@gmail.com> (raw)
In-Reply-To: <83390izlxm.fsf@gnu.org>
On 09/11/2012 18:11, Eli Zaretskii wrote:
>> Date: Fri, 09 Nov 2012 13:14:45 +0200
>> From: Eli Zaretskii <eliz@gnu.org>
>> Cc: 12832@debbugs.gnu.org
>>
>> > Date: Fri, 09 Nov 2012 10:48:31 +0000
>> > From: Andy Moreton <andrewjmoreton@gmail.com>
>> > CC: 12832@debbugs.gnu.org
>> >
>> > I have some files open via tramp (pscp method) on another machine. This uses
>> > putty for ssh (plink.exe) and scp (pscp.exe) for file tranfers. At the time of
>> > the lockup, emacs had a CMD.EXE subprocess running plink.exe.
>>
>> Thanks. I wanted to know this to try to reproduce the lockup here. I
>> will try that as soon as the problem with crashes on Windows is
>> resolved.
>
> The latest trunk is up and running for more than 3 hours with no
> problems. I have a shell buffer running plink and a remote file
> fetched with pscp. I also have display-time active.
I have seen this once again, after doing a full bootstrap from tip this
morning to ensure I wasn't seeing artifacts of a broken build. It seems to
happen about once a day.
> Any other features you have on that could trigger periodic processing
> of any kind?
Not that I know of. The emacs-server is running, but I not used anything that
connects to it, so it should be doing anything. I do use gnus to read news,
but quit gnus after I've read some groups (the lockup was several hours later).
The compiler update may be at issue, so I'll try downgrading back to MinGW gcc
4.7.0 and doing a full bootstrap.
Anything else I should look for in gdb ?
AndyM
next prev parent reply other threads:[~2012-11-09 18:38 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-08 12:57 bug#12832: 24.3.50; Emacs lockup when idle Andy Moreton
2012-11-08 16:28 ` Eli Zaretskii
2012-11-08 18:33 ` Andy Moreton
2012-11-09 9:56 ` Eli Zaretskii
2012-11-09 10:48 ` Andy Moreton
2012-11-09 11:14 ` Eli Zaretskii
2012-11-09 18:11 ` Eli Zaretskii
2012-11-09 18:38 ` Andy Moreton [this message]
2012-11-09 19:12 ` Eli Zaretskii
2012-11-09 19:15 ` Eli Zaretskii
2012-11-13 12:59 ` Eli Zaretskii
[not found] ` <509BAC2E.2000702-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-11-13 13:13 ` Fabrice Niessen
2012-11-13 13:39 ` Dani Moncayo
2012-11-13 14:07 ` Eli Zaretskii
2012-11-13 14:25 ` Andy Moreton
2012-11-13 15:16 ` Eli Zaretskii
2012-11-13 16:00 ` Andy Moreton
2012-11-13 16:35 ` Eli Zaretskii
2012-11-13 16:40 ` Andy Moreton
2012-11-13 17:20 ` Eli Zaretskii
2012-11-13 17:04 ` Eli Zaretskii
2012-11-14 12:44 ` Andy Moreton
2012-11-14 16:29 ` Andy Moreton
2012-11-14 16:48 ` Lennart Borgman
2012-11-14 17:41 ` Eli Zaretskii
2012-11-14 17:49 ` Lennart Borgman
2012-11-14 17:53 ` Eli Zaretskii
2012-11-14 16:51 ` Eli Zaretskii
2012-11-14 20:17 ` Andy Moreton
2012-11-15 19:26 ` Andy Moreton
2012-11-15 20:22 ` Eli Zaretskii
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=509D4DAC.1060901@gmail.com \
--to=andrewjmoreton@gmail.com \
--cc=12832@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).