[TIMOB-9040] iOS: image view made with an array of images is crashing on iPad 1
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | High |
Status | Closed |
Resolution | Invalid |
Resolution Date | 2012-05-24T20:56:33.000+0000 |
Affected Version/s | Release 2.0.1 |
Fix Version/s | Release 2.1.0, Sprint 2012-11 API |
Components | iOS |
Labels | SupportTeam, api |
Reporter | Federico Casali |
Assignee | Blain Hamon |
Created | 2012-05-07T17:56:12.000+0000 |
Updated | 2012-06-18T17:09:03.000+0000 |
Description
Problem description
image view is composed by an array of images, being displayed in sequence. On iPad 1 device the app crashes. On iPad 2 or 3 and simulator the app works fine.Steps to reproduce
See sample code and images included in attached zip file. Attaching log.Additional notes
Customer ticket: http://support-admin.appcelerator.com/display/APP-817556 Escalating for customer priority request (already past his deadline for the project)Attachments
File | Date | Size |
---|---|---|
APP817556.txt | 2012-05-07T17:56:12.000+0000 | 7900 |
imageStressTest.zip | 2012-05-24T18:58:16.000+0000 | 2509748 |
testimageview.zip | 2012-05-07T17:56:12.000+0000 | 6614149 |
While I'm working on this, I have to ask. 51 full-screen images is awfully expensive, and is causing memory panics (thus the crash on iPad 1). Why not use a video player and play this as a video clip? It'll be smoother and less a drain on resources.
I will be submitting a pull request as I did find ways we can shave some waste cycles and bytes when generating an image that is the same of the previous image. However, this will not solve the customer's issue. 51 full-sized images, even with fancy tricks, is too much for an iPad 1. I was able to recreate the memory-induced crash using as minimal and simple a native app as possible. In other words, Titanium is not at issue here.
Proposing this be marked invalid, and will be doing a pull request on related/linked issue.
Crash is caused by 51 images requiring too much RAM to be used on iPad 1. Could recreate natively.
Closing issue as invalid as per Blain's comments