instruments

The documentation just says it means "the number of time the symbol calls itself", but what does this mean? And what does "# Self" mean? When I use Instruments, if "# Self" is equal to 100, then "Self" is also 100.0. I think the documentation you read must be incorrect. Self in the Time Profiler refers to the amount of time spent in the given function itself, excluding time spent in other methods that it calls. Self % is the same thing but expressed as a percentage of the total running time. # Self is the number of actual profiler samples that hit this function or method. The Time Profiler

I have a bit of a dilemma — no matter what I do, I cannot get Apple's Instruments.app to symbolicate any of the included instruments while I'm profiling on my devices (it works OK in the iOS Simulator). I've tried just about everything I can think of, including: Checking that I'm actually building a dSYM Switching between Debug and Release build schemes Making sure that the signing certificate being used in my Development cert Adding and removing my Derived Data folder from Spotlight's Privacy list Clean & Build before profiling Removing the Derived Data folder before building and profiling I

In previous versions of Instruments I had no problem but now (v6.2) for some reason Allocations won't list any of my app's objects. I've tried Debug and Release Mode: Note, the filter "VC" should catch all the ViewControllers. And without the filter... Any ideas? I tested this out with both 6.2 and 6.3 and encountered the issue. Also I was using the iOS 8.2 and 8.3 simulators. However, when I switched to the iOS 8.1 simulator, it worked properly. So it's not so much a bug with Instruments as it is an iOS bug, it appears, or at the very least a combination of the two. So a workaround for now is

I was looking some instrument like Android ADB in order to debug iOS devices. I've found iOS instrument , a tool of the XCode that is able to debug app on mobile iOS devices. This instrument is helpful if you have to test your application or some other open source app. I need to test the iOS device, more than my apps, so I was looking for something like Android ADB for iOS devices. Is there something like it? You asked: I would like to know if it's possible execute a touch on the iOS device, such as input events like "tap", "swipe", "drag", "flick" in similar manner of adb shell for android

I have built an iOS app that is almost done, however, I have recently experienced that it crashes after while due to "Memory pressure". So I started profiling the memory allocations in Instruments and sure, the app does use quite a lot of memory and it only seems to increase during usage. However, relatively new to Instruments memory allocation I am not quite able to decipher where 52 % of the allocations are made, as seen in the screenshot below: It has obviously got something to do with Core Animation, but what exactly is hard for me to determine, so I thought that some clever minds out

Please help me track down an iOS memory leak. Thanks! I'm using xCode 4.0.1 and I tried to activate NSZombie to track a memory leak, but it doesn't seems to work as before, with xCode 3.x I can't find out where the memory leak is coming from, as Instruments points this out: Leaked Object -> GeneralBlock-32 Address -> 0x4c8600 Size -> 32 Bytes Responsible Library -> libsystem_c.dylib Responsible Frame/Caller -> strup At this point I don't know If I'm using Instruments with NSZombie the right way with xCode 4, as it doesn't show the NSZombie option when I click "i" for more information, under

Above given images is of my application leaks. Here I want to understand that, in Extended Detail - you can see different colors like light green, light pink, light brown, light purple. What does each color indicates? Now the other confusion is "How to locate the code which is creating a memory leak?" Upto what limit of memory leak - the actual iPhone can go on with. (suppose 10 bytes no problem, 20 bytes no problem & 200 bytes a problem) What does each color indicates? Which color indicates our code / From which detail we can get to the code where we have allocated the object & forgot to