[TIMOB-1599] Android: OutOfMemoryError in TiBaseTableViewItem.createHasChildDrawable
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Trivial |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2011-04-17T01:56:37.000+0000 |
Affected Version/s | n/a |
Fix Version/s | Release 1.5.0 |
Components | Android |
Labels | android, defect |
Reporter | Bill Dawson |
Assignee | Bill Dawson |
Created | 2011-04-15T02:57:03.000+0000 |
Updated | 2011-04-17T01:56:37.000+0000 |
Description
Example:
java.lang.OutOfMemoryError: bitmap size exceeds VM budget
at android.graphics.BitmapFactory.nativeDecodeStream(Native Method)
at android.graphics.BitmapFactory.decodeStream(BitmapFactory.java:468)
at android.graphics.BitmapFactory.decodeStream(BitmapFactory.java:528)
at android.graphics.drawable.BitmapDrawable.<init>(BitmapDrawable.java:144)
at ti.modules.titanium.ui.widget.tableview.TiBaseTableViewItem.createHasChildDrawable(TiBaseTableViewItem.java:64)
Though the bitmap is always the same, not changeable (static), we're loading it from stream for each row that uses it.
(from [993389ac0e70c01a22aaa2d160092c90eeb3ef5a]) [#1599] Reduce potential OOMs by caching the static bitmaps for hasCheck and hasChild http://github.com/appcelerator/titanium_mobile/commit/993389ac0e70c01a22aaa2d160092c90eeb3ef5a"> http://github.com/appcelerator/titanium_mobile/commit/993389ac0e70c...
Bump, just checking if your commit fixed the issue and we should mark as fixed?
closing, no testable failcase and we've had other tickets related to memory and drawables.