instruments

Instruments tells that there are "misaligned images" which are animated by core animation. What does that mean? UPDATE: I've seen that in Instruments.app > Core Animation. I'd love more information about where you're seeing this, but my suspicion is that it's referring to an image that is not pixel-aligned. Quartz allows you to draw at fractional pixels (recall that CGPoint takes CGFloats, not NSIntegers), but it's more expensive and tends to create a bit of blurriness. You can't really draw on a fractional pixel, so Quartz has to do anti-aliasing to pull it off. That takes time and certainly

Hey. I'm trying to launch Instruments from shell with iPhone specified as target. As for this apple doc I should be able to specify target with '-w' parameter but I don't know what should be there. I've tried iPhone name, I've tried its UUID but nothing worked - constantly I get 'Unknown hardware device specified'. I also checked content of some saved trace document, but inside I see UUID of the iPhone. Maybe it is some prefix/suffix that should be added to the UUID ? In the end i would like to get the following working: instruments -t /Users/user/Template.tracetemplate -D /Users/user/res

int* foo = new int[10]; foo = NULL; sleep(60); Instrument is not finding any leak in above code, how do I use Instrument tool to find C or C++ code leaks. I have stack overflowed most of the explanation is based on objective C codes... The issue is that compiler will optimize out the call to new in the following code fragment: int* foo = new int[10]; foo = NULL; sleep(60); as it's smart enough to know that it's not being used. If you add code to use foo then compiler won't do this and you should see the leak you are expecting: int* foo = new int[10]; foo[3] = 23; foo[8] = 45; printf("%d %d\n",

I have been trying to read a .trace file, which I had generated using a custom instruments template(instruments: Automator , Allocations , Leaks ) using Instruments . The best help I found in this stackoverflow answer . Basically the author created a custom Objective-C program( Traced ) to read a specific type of Apples .trace file(instrument: OpenGL ES Driver ). His answer is geared towards XCode 4.6 . The code still works with XCode 6.1 , but the trace-file seems to have changed slightly. You have to find the *.run.zip file within the .trace package and unzip it. In the extracted folder you

This is on iOS, device is iPad. Here's what happens: I run app on device or debug and run using Xcode. After 5 minutes I receive a memory warning of level 1. A minute later I receive a memory warning of level 2. Another minute later, Program received signal: “0”. I checked for leaks using Leaks in Instruments and detected no leaks . However, according to Activity Monitor, my app initially uses 30 MB, and grows in size to over 100mb over time (about 200kb per second!). So, apparently Leaks doesn't detect all memory leaks. So my question: if Leaks can't detect it, are there any general tips to

I noticed some weird behavior in a UIAutomation script I had written a while back that I hadn't ran in a while. My assertions were failing; after doing some digging, I saw that when iterating a UIAElement's .elements() , subelements do not appear to be equal to themselves. This has worked for me as expected in the past, but appears to be broken in at least XCode 4.3.2 To repro: create a single-view app throw some elements in the view, set Accessibility Labels on the elements so they get picked up by UIAutomation Run the following script in UIAutomation: var elements = UIATarget.localTarget()