From: Eli Zaretskii <eliz@gnu.org>
To: Mario Valencia <mariovalspi@gmail.com>
Cc: 20220@debbugs.gnu.org
Subject: bug#20220: severe memory leak on emacs 24.4.1
Date: Wed, 01 Apr 2015 05:47:39 +0300 [thread overview]
Message-ID: <83oan8sgxg.fsf@gnu.org> (raw)
In-Reply-To: <CA+3HrJXBCxwEV1My11ofNqpNQsasMy6cjwojBJr=_ujgLSKEaw@mail.gmail.com>
> Date: Tue, 31 Mar 2015 20:19:27 -0600
> From: Mario Valencia <mariovalspi@gmail.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, 20220@debbugs.gnu.org
>
> > 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.
You can use the browser's "refresh" function instead, don't? That's
what I'd do, regardless of this problem.
> 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.
Did you actually see this problem in real life, not with your recipe?
Anyway, I still think you should look at your system's configuration,
since I see nothing similar to this large memory consumption on all
but 1 system where I tried this. So there are factors here at work
that depend on the system.
next prev parent reply other threads:[~2015-04-01 2:47 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83oan8sgxg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=20220@debbugs.gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.