[TIMOB-8076] Android: V8: GC lag can cause crash on older devices
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | High |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2012-04-17T17:40:24.000+0000 |
Affected Version/s | Release 1.8.0.1 |
Fix Version/s | Release 2.1.0, Sprint 2012-08 |
Components | Android |
Labels | api |
Reporter | Opie Cyrus |
Assignee | Josh Roesslein |
Created | 2012-03-19T09:19:04.000+0000 |
Updated | 2017-03-06T18:17:38.000+0000 |
Description
On older devices like Droid 2, GC lag cause result in a crash when:
1) alot of object are created resulting in high memory allocation on the java side
2) said objects are available for cleanup (no reference maintained in JS)
3) GC has not scanned yet due to the memory overhead on the V8 side not causing enough pressure on the GC
We need a way to notify V8 that we are running low on memory so that a GC occurs sooner than V8 would normally do on it's own.
A ticket has been linked that provides a fail case for this issue (original test case in ticket - not the one attached in the comments)
Sent [PR #2023](https://github.com/appcelerator/titanium_mobile/pull/2023) to resolve issue. Please verify test case in TIMOB-7865 doesn't keep growing the heap and reaches a peak.
Closing ticket due to time passed.