[TIMOB-2650] iPad - difference in image loading behavior between device and emulator
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Medium |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2011-05-16T11:04:55.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Release 1.7.0, Sprint 2011-13 |
| Components | iOS |
| Labels | image, ios, ipad, placeholder |
| Reporter | Thomas Huelbert |
| Assignee | Stephen Tramer |
| Created | 2011-04-15T03:25:53.000+0000 |
| Updated | 2011-05-16T11:04:55.000+0000 |
Description
User provided content, found attached to ticket http://developer.appcelerator.com/helpdesk/view/61891">http://developer.appcelerator.com/helpdesk/view/61891
1.build project and install onto an ipad
2.run in simulator and compare
results: on device a number of images are left with default placeholders,
Probably not going to have time to give this proper attention this milestone.
Confirmed that this is due to a memory panic on boot. Probably because the app is loading 40 full-size images, plus creating an inordinately large number of proxies, and preparing all of its subviews for display at the same time.
Will investigate later - could actually be cleaned up by memory fixes proposed for 1.7, but those will probably only deal with 'stale' objects. Although we need to reduce the memory footprint of our living objects as well.
It looks like all iPad apps cause a memory panic at some point... bad mojo. We need to fix pronto in 1.7.0.
(from [3b5b9488400315e1a9c03e52ef64571bb1f72c5e]) [#2650 state:fixed-in-qa] Fix for fast resolution of image downloads. https://github.com/appcelerator/titanium_mobile/commit/3b5b9488400315e1a9c03e52ef64571bb1f72c5e"> https://github.com/appcelerator/titanium_mobile/commit/3b5b94884003...
Note: Can be tested with internal tests app 2636.
closed using noted app - 4.3 ipad2 [INFO] Titanium SDK version: 1.7.0 (05/10/11 19:34 879871b...)