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


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

From: Mario Valencia <mariovalspi <at> gmail.com>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: 20220 <at> debbugs.gnu.org, Eli Zaretskii <eliz <at> gnu.org>
Subject: Re: bug#20220: severe memory leak on emacs 24.4.1
Date: Tue, 31 Mar 2015 20:19:27 -0600
[Message part 1 (text/plain, inline)]
> However, I think that
>"worthless" is too extreme, and not using it at all is too radical,
>even if you can do nothing in terms of your system configuration to
>bring down the amount of resources consumed by each invocation.  One
>thread and 8 MB of memory is not that large, unless you really invoke
>that command tens or times in a row.

You are wrong. Calling shellexecute tens of times is very common. Just
consider when editing an html file, saving and viewing the file may happen
more than once a minute, so in less than 30 minutes it will hit the bug. Or
when opening files with an external application in dired, if you open more
than 30 files with shellexecute, it will hit the bug, which is not
unlikely. Afterwards, after quitting the debugger, a few more times of
calling the function and emacs will hang permanently.
[Message part 2 (text/html, inline)]

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.