On 2013 Jul 20, at 01:11, Kyle Sluder k...@ksluder.com wrote:
Allocations is more flexible than leaks. You can filter to just include
objects that are live at process termination.
OK.
On 2013 Jul 20, at 11:25, Jens Alfke j...@mooseyard.com wrote:
If you setenv 'MallocStackLogging' in your
On Fri, Jul 19, 2013, at 10:45 PM, Jerry Krinock wrote:
The 'leaks' tool has identified several NSString objects that my app is
leaking. But neither 'leaks' nor Instruments Leaks identifies the
responsible frame in my code. The 'leaks' tool gives me the string
value, but I still need more
On 2013 Jul 19, at 23:59, Kyle Sluder k...@ksluder.com wrote:
This method does not exist. In fact, as far as I can tell, there are no
initializers for __NSCFString *at all*:
Thank you, Kyle. Yes, I see the NSString documentation also mentions that it
has no designated initializer.
your
On Jul 20, 2013, at 1:04 AM, Jerry Krinock je...@ieee.org wrote:
Have you tried running under the Allocations instrument?
No, I'll study that. I'd thought that Leaks would be better because it
filters allocations to show only leaked allocations, whereas Allocations
shows the whole
On Jul 19, 2013, at 10:45 PM, Jerry Krinock je...@ieee.org wrote:
The 'leaks' tool has identified several NSString objects that my app is
leaking. But neither 'leaks' nor Instruments Leaks identifies the
responsible frame in my code. The 'leaks' tool gives me the string value, but
I
The 'leaks' tool has identified several NSString objects that my app is
leaking. But neither 'leaks' nor Instruments Leaks identifies the
responsible frame in my code. The 'leaks' tool gives me the string value, but
I still need more clues to find it in my code.
This string appears to be
