Hmm, thought MMS exploit and deleted e-mail bug would be the last things I would hear about iPhone OS 3.0 issues. It was destined to be so, if I didn’t stumble upon this insightful write up.
I am kinda fancying developers were afraid of Apple invoking the SDK agreement if they blurt out about this problem. Well, this doesn’t seem to me like a minor problem (that deserve silence) even though I don’t know the nuts and bolts of developing an iPhone game/app.
Thanks to Rama Krishna from iPhone Developer Labs for giving a detail explanation of the ‘known bug’ (so replied Apple in their response when the issue was made known as bug report).
The bug is associated with UIImageView and its memory usage. Creating an image and leaving it alone won’t invoke the killer bug. However, if you have a naughtily creative scheme to move the image or resize it, the screen memory usage starts increasing according to the developer. That sounds not only strange but scary.
Official release of iPhone OS 3.0 is already into its third month and not even a whisper about this problem? Strange!! Throughout this time, developers were waiting for the update that never seem to be coming till date. I am now down to wondering how many developers’ apps/games are plagued with this unreported bug.
In good will this developer/reporter seem to have waited for Apple to fix this major bug while his application goes on getting negative reviews and ratings in the App Store and losing customers everyday.
Here is part of Apple’s response mail to the bug report:
This is due to a bug in the graphics system that mis-reports how it is allocating memory to ObjectAlloc, which causes it to display memory usage as continuously increasing.
&h=58&w=110&zc=1" alt="thumbnail" />
&h=58&w=110&zc=1" alt="thumbnail" />
