-3

These are the memory leaks that I am getting: http://twitter.com/AWEHOFFICIAL/status/221182174811004929/photo/1/large

James
  • 193
  • 7

1 Answers1

0

If you open the righthand pane you should see a stacktrace of the leak, which will help you track it down. You might also attempt to profile with the debug version of your app, in order to get better symbol info. This can be achieved by modifying the project's scheme within Xcode.

trojanfoe
  • 120,358
  • 21
  • 212
  • 242
  • Apparently according to this http://stackoverflow.com/questions/9880336/obj-c-memory-leak-of-malloc-48-bytes-in-strdup-frame this leak has nothing to do with my code. Since it's Malloc 48. Users have said that this is a bug with the framework. – James Jul 06 '12 at 10:28
  • @James check the stacktrace anyway; I don't think you can rely on the size of the malloc to tell if it's framework or your code. – trojanfoe Jul 06 '12 at 10:34
  • Yes indeed if you would kindly follow this link https://twitter.com/AWEHOFFICIAL/status/221191740730781696/photo/1/large can you tell me if it is my code or framework please? – James Jul 06 '12 at 10:41
  • @James It looks like you called `[NSNotificationCenter addObserver]`; did you call `[NSNotificationCenter removeObserver]`? – trojanfoe Jul 06 '12 at 10:46
  • I dont remember calling [NSNotificationCenter addObserver]; – James Jul 06 '12 at 10:50
  • @James OK, so it must be part of the NIB loading process, so you're in the clear by the look of it. – trojanfoe Jul 06 '12 at 10:51
  • Thats good to hear thank you for your help. As I said before It must be a bug with the framework – James Jul 06 '12 at 10:53