{ "id": "137994", "key": "TIMOB-17841", "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": { "id": "7", "description": "", "name": "Invalid" }, "resolutiondate": "2014-10-22T17:57:08.000+0000", "created": "2014-10-13T18:11:31.000+0000", "priority": { "name": "High", "id": "2" }, "labels": [ "qe-3.4.1" ], "versions": [ { "id": "15972", "description": "Release 3.4.0", "name": "Release 3.4.0", "archived": false, "released": true, "releaseDate": "2014-09-28" }, { "id": "16676", "description": "Release 3.4.1", "name": "Release 3.4.1", "archived": false, "released": true, "releaseDate": "2014-11-14" }, { "id": "16593", "description": "Release 4.0.0", "name": "Release 4.0.0", "archived": false, "released": true, "releaseDate": "2015-05-21" } ], "issuelinks": [], "assignee": { "name": "pwang", "key": "pwang", "displayName": "Ping Wang", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2014-10-27T18:21:08.000+0000", "status": { "description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.", "name": "Closed", "id": "6", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "components": [ { "id": "10202", "name": "Android", "description": "Android Platform" } ], "description": "h6.NOTE: 1. The android L x86 64 bit emulator is the first 64 bit emulator(similarly,nexus 6 will also be 64 bit). I am unsure if all apps built with titanium show this behaviour but, I have tried both the default apps (classic & alloy) along with kitchensink & all exibit the same behaviour. \r\nh6. 2. Installed a native app (made by wilson) & it works without any issues. (native app: monkey.apk attached)\r\n\r\nh5.Description:\r\n1. Build a classic or an alloy default app to android L x86 64bit emulator. \r\n2. Let the app launch on the emulator.\r\n\r\nh5.Actual Result:\r\n1. The app launches but clicking on the app gives \"app has stopped responding\".\r\n2. We get the following logs in android monitor:\r\n{code}\r\n10-13 13:30:02.265: I/InputDispatcher(1376): Application is not responding: Window{33d77c72 u0 com.app.androidtesttwo/org.appcelerator.titanium.TiActivity}. It has been 5010.0ms since event, 5010.0ms since wait started. Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.\r\n10-13 13:30:02.265: I/WindowManager(1376): Input event dispatching timed out sending to com.app.androidtesttwo/org.appcelerator.titanium.TiActivity. Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.\r\n10-13 13:30:02.265: I/am_anr(1376): [0,3089,com.app.androidtesttwo,11058756,Input dispatching timed out (Waiting because the touched window has not finished processing the input events that were previously delivered to it.)]\r\n10-13 13:30:02.275: I/Process(1376): Sending signal. PID: 3089 SIG: 3\r\n10-13 13:30:02.275: I/art(3089): Thread[2,tid=3095,WaitingInMainSignalCatcherLoop,Thread*=0xf77ffc90,peer=0x78d3f080,\"Signal Catcher\"]: reacting to signal 3\r\n10-13 13:30:02.295: I/art(3089): Wrote stack traces to '/data/anr/traces.txt'\r\n10-13 13:30:02.295: I/Process(1376): Sending signal. PID: 1376 SIG: 3\r\n10-13 13:30:02.295: I/art(1376): Thread[2,tid=1382,WaitingInMainSignalCatcherLoop,Thread*=0x7f8d253e52f0,peer=0x76036080,\"Signal Catcher\"]: reacting to signal 3\r\n10-13 13:30:02.525: I/Process(1376): Sending signal. PID: 1596 SIG: 3\r\n10-13 13:30:02.525: I/art(1596): Thread[2,tid=1602,WaitingInMainSignalCatcherLoop,Thread*=0x7f8d253e6f80,peer=0x76034080,\"Signal Catcher\"]: reacting to signal 3\r\n10-13 13:30:02.535: I/art(1376): Wrote stack traces to '/data/anr/traces.txt'\r\n10-13 13:30:02.535: I/Process(1376): Sending signal. PID: 1580 SIG: 3\r\n10-13 13:30:02.535: I/art(1580): Thread[2,tid=1583,WaitingInMainSignalCatcherLoop,Thread*=0x7f8d253e6f80,peer=0x76034080,\"Signal Catcher\"]: reacting to signal 3\r\n10-13 13:30:02.535: I/art(1580): Wrote stack traces to '/data/anr/traces.txt'\r\n10-13 13:30:02.535: I/Process(1376): Sending signal. PID: 1434 SIG: 3\r\n10-13 13:30:02.535: I/art(1434): Thread[2,tid=1440,WaitingInMainSignalCatcherLoop,Thread*=0x7f8d253e6f80,peer=0x76034080,\"Signal Catcher\"]: reacting to signal 3\r\n10-13 13:30:02.575: I/art(1434): Wrote stack traces to '/data/anr/traces.txt'\r\n10-13 13:30:02.645: I/art(1596): Wrote stack traces to '/data/anr/traces.txt'\r\n10-13 13:30:04.455: E/ActivityManager(1376): ANR in com.app.androidtesttwo (com.app.androidtesttwo/org.appcelerator.titanium.TiActivity)\r\n10-13 13:30:04.455: E/ActivityManager(1376): PID: 3089\r\n10-13 13:30:04.455: E/ActivityManager(1376): Reason: Input dispatching timed out (Waiting because the touched window has not finished processing the input events that were previously delivered to it.)\r\n10-13 13:30:04.455: E/ActivityManager(1376): Load: 0.12 / 0.28 / 0.23\r\n10-13 13:30:04.455: E/ActivityManager(1376): CPU usage from 44860ms to 0ms ago:\r\n10-13 13:30:04.455: E/ActivityManager(1376): 0.7% 966/adbd: 0% user + 0.7% kernel / faults: 428 minor\r\n10-13 13:30:04.455: E/ActivityManager(1376): 0.3% 2974/kworker/0:2: 0% user + 0.3% kernel\r\n10-13 13:30:04.455: E/ActivityManager(1376): 0% 3089/com.app.androidtesttwo: 0% user + 0% kernel / faults: 734 minor 29 major\r\n10-13 13:30:04.455: E/ActivityManager(1376): 0% 958/surfaceflinger: 0% user + 0% kernel / faults: 6 minor\r\n10-13 13:30:04.455: E/ActivityManager(1376): 0% 1376/system_server: 0% user + 0% kernel / faults: 66 minor\r\n10-13 13:30:04.455: E/ActivityManager(1376): 0% 1950/com.android.mms: 0% user + 0% kernel / faults: 30 minor\r\n10-13 13:30:04.455: E/ActivityManager(1376): +0% 3188/logcat: 0% user + 0% kernel\r\n10-13 13:30:04.455: E/ActivityManager(1376): 100% TOTAL: 10% user + 89% kernel\r\n10-13 13:30:04.455: E/ActivityManager(1376): CPU usage from 1680ms to 2190ms later:\r\n10-13 13:30:04.455: E/ActivityManager(1376): 0% TOTAL: 0% user + 0% kernel\r\n{code}\r\n3. Tried running kitchensink too & I see the same behaviour as default app.\r\n\r\nh5.Expected Result:\r\n1. The app should not stop responding & work successfully.", "attachment": [ { "id": "51938", "filename": "monkey.apk", "author": { "name": "lchoudhary", "key": "lchoudhary", "displayName": "Lokesh Choudhary", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2014-10-13T18:57:46.000+0000", "size": 834616, "mimeType": "application/vnd.android.package-archive" } ], "flagged": false, "summary": "Android: Default classic & alloy apps stops responding after launch on android 5.0 x86 64 bit emulator", "creator": { "name": "lchoudhary", "key": "lchoudhary", "displayName": "Lokesh Choudhary", "active": true, "timeZone": "America/Los_Angeles" }, "subtasks": [], "reporter": { "name": "lchoudhary", "key": "lchoudhary", "displayName": "Lokesh Choudhary", "active": true, "timeZone": "America/Los_Angeles" }, "environment": "Environment:\r\nAppc Studio : 3.4.0.201409261245\r\nTi SDK : 3.5.0.v20141008134113 , 3.4.0.GA\r\nMac OSX : 10.9.4\r\nAlloy : 1.5.1\r\nCLI - 3.4.0\r\nCode Processor: 1.1.1", "closedSprints": [ { "id": 230, "state": "closed", "name": "2014 Sprint 21 SDK", "startDate": "2014-10-13T22:00:57.270Z", "endDate": "2014-10-25T00:00:00.000Z", "completeDate": "2014-10-27T16:33:06.432Z", "originBoardId": 114 } ], "comment": { "comments": [ { "id": "329023", "author": { "name": "pwang", "key": "pwang", "displayName": "Ping Wang", "active": true, "timeZone": "America/Los_Angeles" }, "body": "Updated Android SDK to the latest 5.0 (API level 21). Created a new 64-bit emulator and selected API Level 21 as the target. Titanium projects run fine on this emulator. \r\nThe original issue may be due to the bugs in L preview. Resolved the ticket as Invalid.", "updateAuthor": { "name": "pwang", "key": "pwang", "displayName": "Ping Wang", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2014-10-22T17:56:07.000+0000", "updated": "2014-10-22T17:56:07.000+0000" }, { "id": "329562", "author": { "name": "lchoudhary", "key": "lchoudhary", "displayName": "Lokesh Choudhary", "active": true, "timeZone": "America/Los_Angeles" }, "body": "Verified that with the new android 5.0 64 bit emulator the default classic & alloy apps run fine without any errors.\r\n\r\nClosing.", "updateAuthor": { "name": "lchoudhary", "key": "lchoudhary", "displayName": "Lokesh Choudhary", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2014-10-27T18:16:46.000+0000", "updated": "2014-10-27T18:16:46.000+0000" } ], "maxResults": 2, "total": 2, "startAt": 0 } } }