{ "id": "62646", "key": "TIMOB-2014", "fields": { "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false }, "project": { "id": "10153", "key": "TIMOB", "name": "Titanium SDK/CLI", "projectCategory": { "id": "10100", "description": "Titanium and related SDKs used in application development", "name": "Client" } }, "fixVersions": [ { "id": "11225", "name": "Release 1.5.0", "archived": true, "released": true, "releaseDate": "2010-12-14" } ], "resolution": { "id": "7", "description": "", "name": "Invalid" }, "resolutiondate": "2011-04-15T03:08:11.000+0000", "created": "2011-04-15T03:08:07.000+0000", "priority": { "name": "Medium", "id": "3" }, "labels": [ "defect", "ios", "ipad", "iphone", "rplist", "scrollable", "view" ], "versions": [], "issuelinks": [], "assignee": { "name": "blainhamon", "key": "blainhamon", "displayName": "Blain Hamon", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2017-03-02T21:04:58.000+0000", "status": { "description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.", "name": "Closed", "id": "6", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "components": [ { "id": "10206", "name": "iOS", "description": "iOS Platform" } ], "description": "{html}
When a large amount of views are added to a scrollable view and\nscrolling has happened the app crashes. This is on iphone &\nipad using 4.1 and 1.4.2.
\nSee this ticket for more info and code:
\nhttp://developer.appcelerator.com/helpdesk/view/46321
About how many views would you consider \"a large amount\"?
50+
Appears to have been fixed by Blain's #2003, the\nimage view memory panic issue. No doubt caused by the fact that a\nlarge number of images were being loaded locally.
\nNote, the problem might persist for images which were cached\nfrom a remote source!
Whoops, gonna mark this fixed-in-qa for Thom to test and see if\nit was fixed by #2003.
With today nightly it is still crashing. In my sample I cache\njust 3 pictures and change them three by three.
This bugfix is currently in our master branch. It is not folded\ninto the nightly builds until the fix is approved, which should\nhappen sometime this week. If you need the fix before then, you may\ndevelop off of our (potentially unstable) master branch: http://github.com/appcelerator/titanium_mobile/tarball/master
tried with github - it crashes, but it took more time to\ncrash.
We will be able to respond to this ticket faster if you post a\ncrash log.
This is all I have in\n~/Library/Logs/CrashReporter/MobileDevice/my_device. Is there else\nI should look?
That's the only place you should need to look to find crash\nlogs. Unfortunately neither of these are very helpful; this is\nprobably a memory panic issue.
As long as you are keeping your image views attached to a window\nand not explicitly deleting them, the images that they use will\ncontinue to take up memory. Using so many image views all at once\nwithout loading/unloading them on demand is going to cause memory\nproblems. iOS will not unload these images from memory if they are\nstill in use somewhere and this will lead to memory panics and\ncrashes.
\nTitanium does require better memory management, but there is\nnothing we can do about excessive use of memory which is related to\nviews that are not cleaned up.
\nMarking invalid.
Note that although this bug is marked invalid, better memory\nmanagement for scrollable view may become a feature available in\nthe future. Depends on whether or not we can support dynamic\nload/unload of contents of scrollable view frames. See bug #2193.