0

According to this answer, locating the method causing memory leak is pretty simple with the help of Instruments.

But in my situation, the "extended detail" column doesn't show any of my custom methods, as shown below: Xcode screenshot

How should I locate the leak point now?

Thanks,

snakeninny

Community
  • 1
  • 1
snakeninny
  • 213
  • 4
  • 8
  • Finding leaks is easy with Instruments. Finding what causes them is not. Try to determine when you would expect the object to be released, and which object is holding a reference to it, preventing that. Note that that is likely one of the objects in the list on the right. – fishinear Jul 15 '16 at 16:35
  • Note, by the way, that the hexadecimal codes on the right are references to your code, but apparently Instruments has no access to your source code. – fishinear Jul 15 '16 at 17:07
  • @fishinear any ideas on how to symbolicate the addresses on the right pane? – snakeninny Jul 18 '16 at 02:37

1 Answers1

0

The key is to launch Instruments via Xcode -> Product -> Profile. And then choose Leaks manually, you'll be able to see all the leaking symbols now.

snakeninny
  • 213
  • 4
  • 8