bug#17751: 24.4.50; More memory leaks under OS X Mavericks

["Jan Djärv" <jan.h.d@swipnet.se>]

Hello.

10 jun 2014 kl. 22:55 skrev Steve Purcell <steve@sanityinc.com>:

> Even with this recent nightly Emacs build from emacsformacosx.com, I've
> been suffering from the distnoted memory/CPU-ballooning issue addressed in
> #15946, with that process reaching > 100% CPU and several GB in
> memory. Quitting Emacs solves the problem.
> 
> In the discussion on #15946, Jan D suggested running "leaks" on Emacs to
> see what's going on, so I tried that:
> 
> Starting with an "emacs -Q", I can fire up the "leaks" command in a loop
> and watch Emacs start to leak memory.
> 
> While Emacs is the front-most application and the mouse is moving above
> it, new leaks appear. When the mouse stops, the leaks stop appearing.
> 
> While the cursor blinks (as it does, by default), new leaks appear. When
> the cursor stops blinking after a few seconds, the leaks stop
> appearing. (Unless the mouse is also moving.)
> 
> As I write this message in the clean "emacs -Q" instance, "leaks" tells
> me:
> 
>   Process 60460: 53511 leaks for 11106784 total leaked bytes.
> 
> So 11MB leaked in the space of a few minutes and a few lines typed, with
> just a couple of buffers open!
> 
> The leaks look like this:
> 
>  Leak: 0x10c1d62a0  size=160  zone: DefaultMallocZone_0x1006c5000   OS_dispatch_source  ObjC  libdispatch.dylib
>        0x762d8c20 0x00007fff 0x00000001 0x00000000      .-v............
>        0x89abcdef 0xffffffff 0x762da480 0x00007fff     ..........-v....
>        0x00000000 0x00000000 0x00000000 0x00000000     ................
>        0x00000000 0x00000000 0x00000000 0x00000000     ................
>        0x00000000 0x00000000 0x00000000 0x00000000     ................
>        0x00000001 0x00000000 0x00009cc4 0x00000000     ................
>        0x8979a90c 0x00007fff 0x014002f0 0x00000001     ..y.......@.....
>        0x0c1d6390 0x00000001 0x00000002 0x0000004c     .c..........L...
>        ...

You can not tuncate leaks output without loosing important information.  Post the whole leaks output, comressed.

Leaks is sometimes confused by Emacs memory allocation.  Relevant output can only be gotten just after you have run garbage-collect in Emacs.

Dmitry wrote:

> I don't know how 'leaks' works, but this doesn't look too representative for me.
> Could you please try valgrind? According to http://valgrind.org/info/platforms.html,
> it should work on OSX. Unfortunately you have to compile Emacs yourself to get
> bare (temacs) executable because regular binary will not work.

Valgrind really does not work on OSX, except for the simplest programs.  It is a waste of time to try it.

	Jan D.