[TIMOB-7676] Android: ImageViews cause app to unexpectedly crash
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Critical |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2012-02-17T11:31:29.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Sprint 2012-04, Release 2.0.0, Release 1.8.2 |
| Components | Android |
| Labels | module_imageview, qe-testadded |
| Reporter | Junaid Younus |
| Assignee | Josh Roesslein |
| Created | 2012-02-15T15:13:28.000+0000 |
| Updated | 2012-02-27T10:28:06.000+0000 |
Description
Attachments
| File | Date | Size |
|---|---|---|
| testImageView.zip | 2012-02-15T15:13:28.000+0000 | 1627908 |
Junaid - Please try out the latest 1.8.2 build and confirm the issue.
Sent [PR #1455](https://github.com/appcelerator/titanium_mobile/pull/1455) to resolve issue.
The issue was caused by not having a valid jobject reference when calling into Java from V8/JavaScript. The patch resolves this by maintaining a weak reference when "detached" so we can re-attach on demand. Please verify the test case attached works. Also running some Drillbit passes for regression hunting would be a good idea. Running some of the memory tests (from timob-7409) to verify this doesn't create a regression in leaking proxies.
Sent [PR #1460](https://github.com/appcelerator/titanium_mobile/pull/1460) to cherry pick fix into 1_8_X.
Tested with 1.8.2.v20120217114657 on Nexus S 2.3.6