We are seeing issues using objects of UIImageView in our applications. As long as these objects are not moved around, memory allocations seem to be stable, but as soon as their center/origin/frame is changed memory allocations increase.
If the image views are moved around using "timer" events, the object allocations keep increasing and they are never released. The most interesting aspect in this case is that the "application never receives any memory warnings", even when total memory used by the application crosses 25MB. Although this does not crash the application, it seems to be slowing down the app significantly and is really hard to trace/fix any memory/performance related issues.
Any one else facing same issue? any workarounds?
Here is the link to recent blog article we posted: http://www.iphonedeveloperlabs.com/2009/08/19/apple-at-it-again/
If the image views are moved around using "timer" events, the object allocations keep increasing and they are never released. The most interesting aspect in this case is that the "application never receives any memory warnings", even when total memory used by the application crosses 25MB. Although this does not crash the application, it seems to be slowing down the app significantly and is really hard to trace/fix any memory/performance related issues.
Any one else facing same issue? any workarounds?
Here is the link to recent blog article we posted: http://www.iphonedeveloperlabs.com/2009/08/19/apple-at-it-again/