unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: mariovalspi@gmail.com
Cc: 20220-done@debbugs.gnu.org
Subject: bug#20220: severe memory leak on emacs 24.4.1
Date: Thu, 23 Apr 2015 10:18:27 +0300	[thread overview]
Message-ID: <834mo72tz0.fsf@gnu.org> (raw)
In-Reply-To: <83mw2gtee5.fsf@gnu.org>

> Date: Fri, 10 Apr 2015 14:24:18 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 20220@debbugs.gnu.org
> 
> > Date: Fri, 10 Apr 2015 06:16:46 -0500
> > From: Mario Valencia <mariovalspi@gmail.com>
> > Cc: Daniel Colascione <dancol@dancol.org>, Stefan Monnier <monnier@iro.umontreal.ca>, 20220@debbugs.gnu.org
> > 
> > You are correct; the problem only happens with a file:/// url. The following
> > executes without problem and emacs memory stays constant:
> > (dotimes (i 100) (w32-shell-execute "open" "c:/users/mario/desktop/x.html"))
> > With a file:/// url it triggers the bug:
> > (dotimes (i 100) (w32-shell-execute "open"
> > "file:///c:/users/mario/desktop/x.html"))
> 
> Thanks, that's good to know.
> 
> So I think the solution is to change w32-shell-execute to convert
> file:/// URLs into the normal file-name format internally, and use
> that in the call to ShellExecute.

Now done in the development sources for Emacs 25.1 (commit f2e2cd5).

I'm closing this bug.  Feel free to reopen if some new information
emerges about this.





  parent reply	other threads:[~2015-04-23  7:18 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
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 [this message]
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=834mo72tz0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=20220-done@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 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).