bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#15946: 24.3; Mac OS X, Mavericks, distnoted process


From: Jan Djärv
Subject: bug#15946: 24.3; Mac OS X, Mavericks, distnoted process
Date: Tue, 14 Jan 2014 23:10:14 +0100

Hello.


14 jan 2014 kl. 21:09 skrev canoeberry <emacs@jpayne.net>:

> This is what I see if I run the "leaks" program on my Mac on the emacs 
> process:
> 
> Leak: 0x1109f7b20  size=160  zone: DefaultMallocZone_0x100659000   
> OS_dispatch_source  ObjC  libdispatch.dylib
>       0x76964c20 0x00007fff 0x00000001 0x00000000      L.v............
>       0x89abcdef 0xffffffff 0x769666c0 0x00007fff     .........f.v....
>       0x00000000 0x00000000 0x00000000 0x00000000     ................
>       0x00000000 0x00000000 0x00000000 0x00000000     ................
>       0x00000000 0x00000000 0x00000000 0x00000000     ................
>       0x00000001 0x00000000 0x0002940d 0x00000000     ................
>       0x8896290c 0x00007fff 0x013000a0 0x00000001     .)........0.....
>       0x109f7c10 0x00000001 0x00000002 0x0000004c     .|..........L...
>       ...
> 
> A bazillion of them.
> 
> I also ran it on a distnoted which I just killed and restarted because the 
> existing one was over 2Gb of real memory (or so it said). It claimed there 
> were no leaks.
> 
> This leaks program is pretty cool. It's like a conservative GC algorithm that 
> assumes every integer could be a pointer. So by definition is is conservative.
> 
> Anyway - does this piece of information help any smart hacker types?

They are not all like that, somewhere in there is the real leak.  You need to 
save all output, and put it somewhere it can be read.  If it is large, better 
not send it to the list.
But if you are doing this, do it on a more recent version than 24.3.

        Jan D.







reply via email to

[Prev in Thread] Current Thread [Next in Thread]