Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am running the Instruments Tool (Leaks) and am receiving memory leaks in the QuartzCore library and don’t know exactly where in my code this is occurring. Usually I’m able to pin point the line where the leak is occurring, however the instrument tool isn’t giving me anywhere to view this type of information.
What would be some other things I could look at in terms of diagnosing such a leak?
First, try running this on the device. Sometimes the simulator will report leaks that do not exist on the device.
Secondly, open up the stack trace (right sidebar) and see what code of yours might be involved higher up in triggering this call, then you can think from there why that code might be leaking.
One additional bit of advice. Instead of playing with leaks there, switch over to ObjectAlloc and use the Heapshot feature – if you know about where the leak is, use the heapshot to set a base memory measurement and every time you hit the “heapshot” button after that you’ll see a kind of memory “diff” against that baseline you set. Solving any over-retained problems might also fix your leak.