• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
best way to track down memory leak in screen saver module?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

best way to track down memory leak in screen saver module?


  • Subject: best way to track down memory leak in screen saver module?
  • From: email@hidden (Jody Fairchild)
  • Date: Sun, 17 Feb 2002 20:20:31 +0900

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
_______________________________________________
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.

  • Follow-Ups:
    • Re: best way to track down memory leak in screen saver module?
      • From: David Remahl <email@hidden>
  • Prev by Date: Re: Synchronize menus
  • Next by Date: Substring in String?
  • Previous by thread: NSTextView Question
  • Next by thread: Re: best way to track down memory leak in screen saver module?
  • Index(es):
    • Date
    • Thread