[TIMOB-8549] Android: Memory Managment Issue
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | High |
Status | Closed |
Resolution | Duplicate |
Resolution Date | 2012-04-17T13:10:28.000+0000 |
Affected Version/s | Release 1.8.2 |
Fix Version/s | n/a |
Components | Android |
Labels | SupportTeam, core |
Reporter | Junaid Younus |
Assignee | Josh Roesslein |
Created | 2012-04-05T10:34:17.000+0000 |
Updated | 2017-03-21T22:39:37.000+0000 |
Description
*Code*
http://pastie.org/3732988
*Steps to reproduce*
Run the app inside the emulator/device, load up ddms, watch the heap size increase.
*Expected behavior*
The code is creating and releasing Ti objects, so it should allocate and deallocate memory over time.
*Actual behavior*
It actually keeps building up and gradually increases the heap size, it doesn't seem to go down a lot, it mainly increases.
*Notes*
-You might have to run this for a few minutes, in order to replicate this behavior.
-The app is opening a new window, and releases it. So you will see the window going back and forth, which is the expected behavior. It will automatically open/close the window over time. You should only have to observe the 'heap size' and 'allocated' in ddms.
-Only tested on the emulator.
-HD ticket: http://support-admin.appcelerator.com/display/APP-341636
I can confirm that this behavior occurs on device as well as emulator
How is this coming? This issue has been a huge annoyance to our customers
Hey Ryan, This fix has been scheduled for 'Sprint 8', which will be released on the 22nd of this month. The issue should be fixed before that date. Hope that's okay with you.
Okay, appreciate the update
This looks to be related to the issue fixed in TIMOB-7779. Tested on emulator using 2.0.1 and the leak appears to be gone.
Closing ticket as duplicate.