GNU bug report logs - #20220
severe memory leak on emacs 24.4.1

Previous Next

Package: emacs;

Reported by: Mario Valencia <mariovalspi <at> gmail.com>

Date: Sat, 28 Mar 2015 23:40:03 UTC

Severity: normal

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

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Daniel Colascione <dancol <at> dancol.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 20220 <at> debbugs.gnu.org, monnier <at> iro.umontreal.ca, mariovalspi <at> gmail.com
Subject: bug#20220: severe memory leak on emacs 24.4.1
Date: Wed, 01 Apr 2015 09:01:13 -0700
[Message part 1 (text/plain, inline)]
On 04/01/2015 07:26 AM, Eli Zaretskii wrote:
>> Date: Wed, 01 Apr 2015 00:53:56 -0700
>> From: Daniel Colascione <dancol <at> dancol.org>
>> Cc: 20220 <at> debbugs.gnu.org
>>
>> Whatever bit of code is starting a thread (or otherwise permanently
>> consuming resources) on ShellExecute is broken, not Emacs. I don't think
>> I've seen that behavior myself.
> 
> As I wrote, I only see something similar on one particular system out
> of 4 I tried this on.  And I'm not yet sure what I see there is what
> happens on Mario's system.
> 
>> What's the thread start function on that new thread?
> 
> SHWLAPI.dll!IUnknown_QueryService+0x87 on my system where I see this.
> 
>> What's on its stack?
> 
> This:
> 
>   wow64win.dll+0x3fe3a
>   wow64win.dll+0x1aeac
>   wow64.dll!Wow64SystemServiceEx+0xd7
>   wow64cpu.dll!TurboDispatchJumpAddressEnd+0x2d
>   wow64.dll!Wow64SystemServiceEx+0x1ce
>   wow64.dll!Wow64LdrpInitialize+0x42a
>   ntdll.dll!RtlIsDosDeviceName_U+0x23a27
>   ntdll.dll!LdrInitializeThunk+0xe
>   USER32.dll!DispatchMessageW+0x5c
>   SHLWAPI.dll!Ordinal173+0x287b
>   ntdll.dll!RtlInitializeExceptionChain+0x63
>   ntdll.dll!RtlInitializeExceptionChain+0x36
> 
> Mario, can you tell if you see similar things on your system?  I
> suggest you verify that you have the same issue, by installing the
> Process Explorer and looking in the Properties for the Emacs process,
> in the Threads tab.  There you should see a new thread created each
> time w32-shell-execute is invoked, and also the symbolic Start Address
> of each such thread.

On what OS version is that thread running?

[signature.asc (application/pgp-signature, attachment)]

This bug report was last modified 10 years and 29 days ago.

Previous Next


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