unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Mario Valencia <mariovalspi@gmail.com>
To: Daniel Colascione <dancol@dancol.org>
Cc: 20220@debbugs.gnu.org
Subject: bug#20220: severe memory leak on emacs 24.4.1
Date: Sun, 29 Mar 2015 00:04:51 -0600	[thread overview]
Message-ID: <CA+3HrJU3FGLxAzsp4AOT1eD+Ybk-x-S9D_KZDZkU++i1QVz4Rg@mail.gmail.com> (raw)
In-Reply-To: <5517951C.9050204@dancol.org>

[-- Attachment #1: Type: text/plain, Size: 915 bytes --]

I have no idea my friend. How can I check?

2015-03-29 0:01 GMT-06:00 Daniel Colascione <dancol@dancol.org>:

> On 03/28/2015 04:39 PM, Mario Valencia wrote:
> > to reproduce it, i create a small emtpy html document. then i evaluate
> > the following expression:
> >
> > (dotimes (i 100) (browse-url-of-file))
> >
> > This causes emacs to start opening the file using google chrome. In the
> > task manager, i can see emacs' memory usage go up by about 5 megabytes
> > each time a tab is opened. When it opens about 30 tabs, emacs is using
> > 138 megabytes of memory, and it gives the error below.
> > the translation is something like this: "ShellExecute failed: Storage
> > space insufficient to process this command"
> > My harddrive has enough storage space btw.
>
> Do you happen to have any shell extensions installed?  ShellExecute can
> run arbitrary third-party code through this extension mechanism.
>
>

[-- Attachment #2: Type: text/html, Size: 1309 bytes --]

  reply	other threads:[~2015-03-29  6:04 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 [this message]
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
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=CA+3HrJU3FGLxAzsp4AOT1eD+Ybk-x-S9D_KZDZkU++i1QVz4Rg@mail.gmail.com \
    --to=mariovalspi@gmail.com \
    --cc=20220@debbugs.gnu.org \
    --cc=dancol@dancol.org \
    /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).