GNU bug report logs - #12832
24.3.50; Emacs lockup when idle

Previous Next

Packages: emacs, w32;

Reported by: Andy Moreton <andrewjmoreton <at> gmail.com>

Date: Thu, 8 Nov 2012 12:58:02 UTC

Severity: normal

Found in version 24.3.50

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


Message #59 received at 12832 <at> debbugs.gnu.org (full text, mbox):

From: Andy Moreton <andrewjmoreton <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 12832 <at> debbugs.gnu.org, fni <at> missioncriticalit.com, dmoncayo <at> gmail.com
Subject: Re: bug#12832: 24.3.50; Emacs lockup when idle
Date: Tue, 13 Nov 2012 16:40:29 +0000
On 13/11/2012 16:35, Eli Zaretskii wrote:
>> Date: Tue, 13 Nov 2012 16:00:30 +0000
>> From: Andy Moreton <andrewjmoreton <at> gmail.com>
>> CC: dmoncayo <at> gmail.com, fni <at> missioncriticalit.com, 12832 <at> debbugs.gnu.org
>>
>> The fact that thread 236140 is at ThreadStartRoutine makes me wonder if this
>> is related to the perils of DllMain (i.e. the loader lock).
>
> Sorry, I don't follow.  Can you say more about this problem, or point
> me to some accessible documentation about it?

The DllMain notifications for process and thread create/destroy are called 
with the (system internal) loader lock held. This means that anything called 
from these routines should not use locks, or deadlock is possible. So I was 
wondering if the thread manipulation for timer handling is interacting with 
those mechanisms.

Of course I don't know nearly enough about Win32 to actually say much useful 
here, so the actual problem is probably something else entirely.

    AndyM







This bug report was last modified 12 years and 275 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.