GNU bug report logs - #15156
24.3; !MEM FULL!

Previous Next

Packages: emacs, w32;

Reported by: "Sebastien Vauban" <sva-news <at> mygooglest.com>

Date: Wed, 21 Aug 2013 20:28:01 UTC

Severity: normal

Tags: moreinfo

Found in version 24.3

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Sebastien Vauban <sva-news <at> mygooglest.com>
Cc: 15156 <at> debbugs.gnu.org
Subject: bug#15156: 24.3; !MEM FULL!
Date: Fri, 06 Sep 2013 12:58:23 +0300

> From: "Sebastien Vauban" <sva-news <at> mygooglest.com>
> Cc: 15156 <at> debbugs.gnu.org
> Date: Fri, 06 Sep 2013 11:42:40 +0200
> 
> > Anyway, putting a break at xmalloc conditioned by some large
> > allocation size might show who is requesting this much memory.  I
> > don't see how this can be investigated otherwise without some
> > debugging.
> 
> If you have a recipe which does not constrain too much my daily usage of
> Emacs, I'm willing to apply it.

Something like

  (gdb) break xmalloc if size > 10000
  (gdb) commands
         > bt
	 > continue
	 > end
  (gdb)

And similarly for xzalloc and xrealloc.

Then run Emacs as usual, and the code which allocates these large
chunks of memory will be shown in the backtraces.

> [1] I'd be interested by knowing what something similar you use...

Nothing.  I don't need that.
This bug report was last modified 11 years and 251 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.