instruments

In my app I have a scroll view and four table views. Each time one is dragged and then released, I get a 48 byte leak. This really adds up. As you can see, both groups of leaks have the same source. Has anyone seen a leak like this before? Edit 1: When I click on the arrow next to the leak, I get this information for the leak: What you are seeing is a known bug in iOS 5.1 and is being discussed in the iOS Developer Forums as such. You can find the relevant thread by searching in the forums for "strdup". See the thread titled "Elements App Memory Leak". Search for the post from an Apple

I've cleared my app of leaks using the leaks tool, but I still notice that the objectalloc tool jumps up in the number of objects allocated and footprint when I switch views. I'm especially seeing high numbers of: GeneralBlock-16 with mostly Foundation responsible with caller NSLogv and GeneralBlock-0 with mostly QuartzCore responsible Any tips on what I can do to further debug this? Thanks! The ObjectAlloc tool is designed to graph total object allocation over time, and it doesn't take deallocations into account. Essentially: it will always go up . What you can do is look at the Net Bytes and

I have been trying to perform some OpenGL ES performance optimizations in an attempt to boost the number of triangles per second that I'm able to render in my iPhone application, but I've hit a brick wall. I've tried converting my OpenGL ES data types from fixed to floating point (per Apple's recommendation ), interleaving my vertex buffer objects, and minimizing changes in drawing state, but none of these changes have made a difference in rendering speed. No matter what, I can't seem to push my application above 320,000 triangles / s on an iPhone 3G running the 3.0 OS. According to this