Re: leaks and MallocStackLogging
Re: leaks and MallocStackLogging
- Subject: Re: leaks and MallocStackLogging
- From: Jerry <email@hidden>
- Date: Fri, 18 Jul 2008 20:09:17 +0100
On 18 Jul 2008, at 19:36, j o a r wrote:
On Jul 18, 2008, at 11:27 AM, Jerry wrote:
My experience of turing on MallocStackLogging is that although it's
invaluable for finding leaks, it's also likely to make your
application crash. I seem to remember some threads here in the past
about it not being threadsafe.
True, but fixed in 10.5.
Well, it still crashes my app in 10.5 :-( Running out of space to
store all those stack traces maybe.
That should no longer be a problem, since they're paged out to disk
and not stored in RAM on 10.5 IIRC.
I've also never really had any problem with using MallocStackLogging
on earlier versions of Mac OS X. Perhaps it depends on what you're
trying to do, but I've used MallocStackLogging on very memory
intensive, and very busy, multithreaded applications on at least
both 10.3 and 10.4.
That said - and to reiterate what I said earlier in this tread - Why
are you not using Instruments?
Actually, I am using Instruments, but it still crashes :-( It's a
great tool though, even when it crashes.
Jerry
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden