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

[Jan D.]

Steve Purcell skrev 2014-06-11 19:37:
> Yes! That would make sense. Let me compile locally and repeat the experiment...

I checked in a change in trunk where I made the check at runtime.
Also, another (but unrelated to distnoted) leak was plugged.

        Jan D.

> On 11 Jun 2014, at 18:29, Jan D. <jan.h.d@swipnet.se> wrote:
>
> > Steve Purcell skrev 2014-06-11 18:40:
> > > Okay, done. I fired up Emacs with MallocStackLogging enabled, sent it some input 
> > > events via mouse & keyboard, turned off blink-cursor-mode then ran 
> > > garbage-collect. Finally I captured the leaks output, which reported 2MB leaked:
> > >
> > > https://dl.dropboxusercontent.com/u/3739665/leaks.txt.gz
> >
> > Are you still using nightlies from emacsformacosx.com?
> > This:
> >
> >         Call stack: [thread 0x7fff76a9b310]: | start | main | Frecursive_edit | 
> > recursive_edit_1 | internal_catch | command_loop_2 | internal_condition_case | 
> > command_loop_1 | read_key_sequence | read_char | 
> > detect_input_pending_run_timers | gobble_input | ns_read_socket | 
> > -[NSApplication run] | -[NSApplication _installMemoryPressureDispatchSources] | 
> > dispatch_source_create | _os_object_alloc_realized | class_createInstance | 
> > calloc | malloc_zone_calloc
> > Leak: 0x10080b650  size=16  zone: DefaultMallocZone_0x1006cb000
> >
> > shows that Emacs is not built on OSX 10.9 where it is run.
> > This is an OSX bug with 10.9 that we have worked around, but only if Emacs is 
> > built on 10.9.  I guess that is your problem right there.
> >
> > I could try to make it a runtime check instead.
> >
> >         Jan D.