How to better use of PLCrashReporter? about maobjcruntime HOT 1 CLOSED

Sorry, I didn't see this for a while.

Finding performance problems with a snapshot like this is going to be tricky, since you only capture a single moment in time. It should be possible to get some useful information, though, assuming that it's likely to be in the middle of whatever is taking a lot of time when you trigger the stack trace. You'd have to look at every thread and see if any of them is doing something costly. In your first image, for example, the fact that thread 0 is in cellForRowAtIndexPath indicates that might be a hot function. (I assume you inserted a sleep just to make it look slow.)

Any symbolication solution that works on crash reports should also work on these not-quite-crash reports. They still look just like crash reports.

Feel free to e-mail me directly rather than continuing here, [email protected]

from maobjcruntime.