Re: best way to track down memory leak in screen saver module?
Re: best way to track down memory leak in screen saver module?
- Subject: Re: best way to track down memory leak in screen saver module?
- From: David Remahl <email@hidden>
- Date: Sun, 17 Feb 2002 13:36:18 +0100
>
i've been playing with a screen saver over the past couple of days.
>
it's pretty much done, but i suspect that it may be leaking a little
>
memory, because i can see system prefs eating memory in top if i have
>
the screen saver selected (just running in the little preview window).
>
>
i don't see anything obvious (to me anyway) in the code that would
>
indicate a problem, so i was kind of hoping that a tool like
>
MallocDebug might help, but of course, since this is a screen saver,
>
it's pretty hard to be able to do anything else while it's running,
>
which makes it hard to use MallocDebug and/or ObjectAlloc ... note
>
also that linking to libMallocDebug didn't help either, i'm guessing
>
because the ss module isn't really an app anyway, it's just running
>
under system prefs.
>
>
anybody have any easy answers or suggestions before i start in on the
>
old fashioned way?
>
>
thanks,
>
-jf
I would suggest the Saver Lab application (www.versiontracker.com/macosx/).
Run your saver in there, and observe it in ObjectAlloc. It _should_ work to
do the same thing on System Prefs, since they both run in the same space...
/ Sincerely, David
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.