Instruments 7.0: Crash when clicking a line of code in an allocation trace
| Originator: | dieter.komendera | ||
| Number: | rdar://22170734 | Date Originated: | 06-Aug-2015 05:27 PM |
| Status: | Open | Resolved: | |
| Product: | Developer Tools | Product Version: | Instruments 7.0 (58132) |
| Classification: | Crash/Hang/Data Loss | Reproducible: | Always |
Summary: Crash when clicking a line of code in an allocation trace in the Leaks profiling tool Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Application Specific Information: *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[XRHitComment initComment:run:ofFragment:value:formatter:percentage:backtraces:context:symbol:]: unrecognized selector sent to instance 0x7feee8538160' terminating with uncaught exception of type NSException abort() called Application Specific Backtrace 1: 0 CoreFoundation 0x00007fff876837dc __exceptionPreprocess + 172 1 libobjc.A.dylib 0x00007fff906ab052 objc_exception_throw + 48 2 CoreFoundation 0x00007fff8768689d -[NSObject(NSObject) doesNotRecognizeSelector:] + 205 3 CoreFoundation 0x00007fff875bfe71 ___forwarding___ + 1009 4 CoreFoundation 0x00007fff875bf9f8 _CF_forwarding_prep_0 + 120 5 MemoryPlugin 0x000000010e0ead52 ObjectAllocEventNameForType + 19690 6 InstrumentsPlugIn 0x0000000103b0c2d6 -[XRRunQuery main] + 223 7 Foundation 0x00007fff922b0a33 -[__NSOperationInternal _start:] + 654 8 Foundation 0x00007fff922b051f __NSOQSchedule_f + 194 Steps to Reproduce: * profile using Leaks instrument * click a line in an allocation trace of an object Expected Results: showing the line in context Actual Results: crash Regression: probably a regression to Instruments 6 but I didn’t test that Notes:
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!