Since swift isn't using prefix anymore, it's really hard our own objects. I can think two solutions to make it working with this kind of projects:

• Filtering using the project module instead of using a simple prefix
• Add a search field which can make easier to track our own objects

crash stack:

crash code:

the log output: 2016-03-16 22:55:04.864 Weiyun[3862:2294084] zone address:0x1042ac000 index:0 2016-03-16 22:55:05.123 Weiyun[3862:2294084] zone address:0x104518000 index:1 2016-03-16 22:55:05.123 Weiyun[3862:2294084] zone address:0x13784a000 index:2 2016-03-16 22:55:05.124 Weiyun[3862:2294084] zone address:0x1047f8000 index:3 2016-03-16 22:55:05.124 Weiyun[3862:2294084] zone address:0x19f939e70 index:4 2016-03-16 22:55:05.124 Weiyun[3862:2294084] zone address:0x137179800 index:5 2016-03-16 22:55:05.130 Weiyun[3862:2294084] zone address:0x1042ac000 index:0 2016-03-16 22:55:05.636 Weiyun[3862:2294084] zone address:0x104518000 index:1 2016-03-16 22:55:05.636 Weiyun[3862:2294084] zone address:0x13784a000 index:2 2016-03-16 22:55:05.637 Weiyun[3862:2294084] zone address:0x1047f8000 index:3 2016-03-16 22:55:05.637 Weiyun[3862:2294084] zone address:0x19f939e70 index:4 Weiyun(3862,0x1a05f9000) malloc: Attempted to register zone more than once: 0x16fd99c18 2016-03-16 22:55:05.637 Weiyun[3862:2294084] zone address:0x137179800 index:5 2016-03-16 22:55:05.637 Weiyun[3862:2294084] zone address:0x16fd99c18 index:6

I don't know what happed, It's crash everytime I want stop record or tap the Heap Bar.

Thanks

In my app, I record the memory usage, but it too slow. One operation may cost ten minutes.

If run for a while, the app may killed because the memory:Message from debugger: Terminated due to Memory Error I Test this in iPhone 6 & iphone 5c. The project is large and many objects are alloced when running.

somebody has the same problem? how should I resolve this. Thanks!

Can you show how this could be used without a GUI? e.g.. in app extensions that can't display a full UI? A simple way using NSLog() would be much appreciated.

I am confused by the algorithm of Retain Count. in HeapInspector,Retain Count = alloc+retain+strong -release, but is not always equals to CFGetRetainCount((__bridge CFTypeRef)object), why?

ld: library not found for -lPods-HeapInspector clang: error: linker command failed with exit code 1 (use -v to see invocation)

@tapwork if use pods, will start .xcworkspace file, but project no this file

If obj is a instance of subclass of NSProxy, when calling class_getName([obj class]) will cause EXC_BAD_ACCESS crash. The case I met is when A2DynamicDelegate instance from BlocksKit is passed to static inline bool canRecordObject(Class cls); method, it crashes on the line const char *name = class_getName(cls);

Try to fix it by simply not testing its class, and just ignore it.

1. Check out code with tag 0.0.6, and run the HeapInspectorExample.
2. Tap Record button and Gallery button. It crash in NSObject+HeapInspector.m, Line 152, EXC_BAD_ACCESS.

BTW, it seams this was introduced in commit: 45fb730. The param backtrace is released in getBacktrace().

This pull requests corrects the spelling of CocoaPods 🤓 https://github.com/CocoaPods/shared_resources/tree/master/media

One day I’ll make a bot that looks through the READMEs of all Pods, looks to see if it uses “Cocoapods” and PRs “CocoaPods” :D

— Ørta (@orta) February 10, 2016

Created with cocoapods-readme.

HeapInspector-for-iOS is not compatible with ReactiveCocoa , because [obj class] in canRecordObject method will cause stack overflow when rac_signalForSelector is called in ReactiveCocoa.

I found the crash I mentioned in https://github.com/tapwork/HeapInspector-for-iOS/issues/2 is related to this bug.

It should return the address of copied object, via: http://clang.llvm.org/docs/AutomaticReferenceCounting.html

And according to the doc, if the object is no longer on stack (actually I didn't quite understand the meaning of on stack, retainCount > 0?), it should be retained instead of copied.

But with this fix, at least blocks won't crash with HeapInspector enabled.

when I install HeapInspector in my program,I find that your framework can product memory leak! Can you answer me the reason? I want to say my program has not memory leak. I just want to test your framwork,no except to see what it causes now.

When I run my app with HeapInspector, I start it in AppDelegate in didFinishLaunching, a couple of seconds in running it, the simulator freezes. Both the record and heap buttons, and everything in my app stops responding to inputs. Issue reproduces both on simulator and on device.

Debug navigator shows like 10-20% CPU activity and about 10mbps of ram, which is regular app usage.