[TIMOB-886] Android: Possible memory leak in ImageView
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Medium |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2011-04-17T01:54:34.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Release 1.4.0 |
| Components | Android |
| Labels | android, defect |
| Reporter | Don Thorp |
| Assignee | Don Thorp |
| Created | 2011-04-15T02:38:33.000+0000 |
| Updated | 2011-04-17T01:54:34.000+0000 |
I would add that I can get this to happen on windows that do not contain ImageView's too. It just seems to happen faster on windows that do. I have a window that has just a tableview, web service call, and it does the same thing. Typically my app will crash within 5 minutes of normal use from the out of memory error.
(from [a9c3a67dfb35553d0934b56257d719f63e2881ba]) [#886 state:resolved] This fix specifically addresses issues related to images and the VM Budget Exceeded exception. There is still an issue with Tableview not releasing resources correctly that will follow. http://github.com/appcelerator/titanium_mobile/commit/a9c3a67dfb35553d0934b56257d719f63e2881ba"> http://github.com/appcelerator/titanium_mobile/commit/a9c3a67dfb355...