First, I want to commend the creators of Buzztouch and all of the fine people on this forum who offer advice and assistance. I've been having a wonderful time tinkering with the Buzztouch tools and reading the forum. OK, here's the issue I'm grappling with. Using version 1.5, I've built a pretty nifty application that I think will look great once it is complete. However, when I launch the app in XCode and view it in the simulator, the CPU usage on my MacBook Pro begins to spike at around 100 percent. The culprit, according to the OSX Actvitity Monitor, is indeed the app that I'm building. I also built an app using version 1.4 of Buzztouch, and that app uses very little CPU when opened in XCode and the simulator. Anyone else here experiencing similar problems? I'm concerned that once I load the app onto an actual iPhone, it will eat up CPU cycles on that device as well. Cheers!

Sounds like you found something we can all benefit from? We are admittedly not super-skilled at operating Xcodes built in Instruments package. However, we are very interested in doing all we can to minimize memory usage. Memory hog apps are no good for anyone. There are many thousands of these in the wild and we very rarely hear of memory issues or crashes due to the code. This doesn't mean there isn't anything wrong with it. If you can isolate the issue, re-post so we can post a fix for everyone. It's a trick thing finding CPU / MEMORY issues so it may take some tinkering? And, of course, there may be nothing wrong and something strange is happening with one of your screens or your setup? Who knows. See what you can find. Know for sure though that so many of these apps have been built that I'de be very surprised to find something obvious that hogs memory that knowbody else experieneces? Thanks tons for the insightful feedback...we look forward to your discoveries.

Hi David, Thanks for your reply. Perhaps the best thing for me to do will be remove one feature at a time from the app until I hopefully isolate the one that is causing the spike. I'll spend the next couple of days trying that, and then report back here my findings.

Sounds good in Tokyo. Thanks in advance for whatever you may find?

Update: I restarted my Mac today and then launched XCode and my 1.5 project. That was about 5 hours ago, and thus far the app has been using only a small percentage of the CPU — around 10 percent. It's no longer spiking to 100 percent as it was doing yesterday, when I started this thread.\ Makes me think the problem might have been with my Mac itself, and not the app. However, I'm going to continue to monitor the situation, and if I find the app causing the CPU to spike again, I'll report my findings here.

Good work. Good plan. Good news ;-)

David, This is completely off-topic, but I was just reading the about section on buzztouch.com, and noticed that you attended CSU Monterey Bay. Nice to such great things coming out of the CSU system! (I graduated from CSU Sacramento in 1987.)