unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Colascione <dancol@dancol.org>
Cc: 20220@debbugs.gnu.org, mariovalspi@gmail.com
Subject: bug#20220: severe memory leak on emacs 24.4.1
Date: Wed, 01 Apr 2015 19:05:53 +0300	[thread overview]
Message-ID: <83sicjrfz2.fsf@gnu.org> (raw)
In-Reply-To: <551C1649.4050200@dancol.org>

> Date: Wed, 01 Apr 2015 09:01:13 -0700
> From: Daniel Colascione <dancol@dancol.org>
> CC: mariovalspi@gmail.com, monnier@iro.umontreal.ca, 
>  20220@debbugs.gnu.org
> 
> >   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?

64-bit Windows 7.





  reply	other threads:[~2015-04-01 16:05 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-28 23:39 bug#20220: severe memory leak on emacs 24.4.1 Mario Valencia
2015-03-29  6:01 ` Daniel Colascione
2015-03-29  6:04   ` Mario Valencia
2015-03-29 15:15     ` Eli Zaretskii
2015-03-29 15:35 ` Eli Zaretskii
2015-03-31  2:07   ` Mario Valencia
2015-03-31 12:46     ` Eli Zaretskii
2015-03-31 21:03       ` Stefan Monnier
2015-04-01  2:19         ` Mario Valencia
2015-04-01  2:47           ` Eli Zaretskii
2015-04-01 14:24             ` Eli Zaretskii
2015-04-01  7:53           ` Daniel Colascione
2015-04-01 14:26             ` Eli Zaretskii
2015-04-01 16:01               ` Daniel Colascione
2015-04-01 16:05                 ` Eli Zaretskii [this message]
2015-04-04 20:24                   ` Mario Valencia
2015-04-04 21:19                     ` Eli Zaretskii
2015-04-10 11:16                       ` Mario Valencia
2015-04-10 11:24                         ` Eli Zaretskii
2015-04-10 11:29                           ` Eli Zaretskii
2015-04-10 11:33                             ` Mario Valencia
2015-04-10 11:36                               ` Eli Zaretskii
2015-04-10 12:58                                 ` Stefan Monnier
2015-04-10 13:13                                   ` Eli Zaretskii
2015-04-23  7:18                           ` Eli Zaretskii
2015-04-01  7:50   ` Daniel Colascione
2015-04-01 14:25     ` 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=83sicjrfz2.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=20220@debbugs.gnu.org \
    --cc=dancol@dancol.org \
    --cc=mariovalspi@gmail.com \
    /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).