{ "id": "110730", "key": "TIMOB-12987", "fields": { "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false }, "project": { "id": "10153", "key": "TIMOB", "name": "Titanium SDK/CLI", "projectCategory": { "id": "10100", "description": "Titanium and related SDKs used in application development", "name": "Client" } }, "fixVersions": [], "resolution": null, "resolutiondate": null, "created": "2013-03-07T00:13:11.000+0000", "priority": { "name": "Low", "id": "4" }, "labels": [ "core", "webview" ], "versions": [], "issuelinks": [ { "id": "26430", "type": { "id": "10011", "name": "Includes", "inward": "is included by", "outward": "includes" }, "inwardIssue": { "id": "105162", "key": "TIMOB-11810", "fields": { "summary": "Ti API: Address common WebView deficiencies", "status": { "description": "The issue is open and ready for the assignee to start work on it.", "name": "Open", "id": "1", "statusCategory": { "id": 2, "key": "new", "colorName": "blue-gray", "name": "To Do" } }, "priority": { "name": "Low", "id": "4" }, "issuetype": { "id": "6", "description": "gh.issue.epic.desc", "name": "Epic", "subtask": false } } } } ], "assignee": null, "updated": "2018-02-28T20:04:25.000+0000", "status": { "description": "The issue is open and ready for the assignee to start work on it.", "name": "Open", "id": "1", "statusCategory": { "id": 2, "key": "new", "colorName": "blue-gray", "name": "To Do" } }, "components": [ { "id": "10202", "name": "Android", "description": "Android Platform" } ], "description": "During the triage of TIMOB-10526 these are the problems I discovered\r\n1. releaseViews is overridden for TIMOB-7808 to get in parity with iOS which I think is a possible memory leak. Also the behavior in TIMOB-7808 is only on Android and iOS and not on MW. So a case can be made that we do not need parity.\r\n\r\n2. This ticket also introduced release() which overrides the method in KrollProxy and does not call the parent method which does something completely different. \r\n\r\n3. Webviews are tied to the activity lifecycle which is fine if the window is heavyweight but not if the window is lightweight (Look at the code in onDestroy)\r\n\r\n", "attachment": [], "flagged": false, "summary": "Android: Webview architecture problems", "creator": { "name": "vduggal", "key": "vduggal", "displayName": "Vishal Duggal", "active": false, "timeZone": "America/Los_Angeles" }, "subtasks": [], "reporter": { "name": "vduggal", "key": "vduggal", "displayName": "Vishal Duggal", "active": false, "timeZone": "America/Los_Angeles" }, "environment": null, "comment": { "comments": [], "maxResults": 0, "total": 0, "startAt": 0 } } }