Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-17841] Android: Default classic & alloy apps stops responding after launch on android 5.0 x86 64 bit emulator

GitHub Issuen/a
TypeBug
PriorityHigh
StatusClosed
ResolutionInvalid
Resolution Date2014-10-22T17:57:08.000+0000
Affected Version/sRelease 3.4.0, Release 3.4.1, Release 4.0.0
Fix Version/sn/a
ComponentsAndroid
Labelsqe-3.4.1
ReporterLokesh Choudhary
AssigneePing Wang
Created2014-10-13T18:11:31.000+0000
Updated2014-10-27T18:21:08.000+0000

Description

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.

2. Installed a native app (made by wilson) & it works without any issues. (native app: monkey.apk attached)

Description:

1. Build a classic or an alloy default app to android L x86 64bit emulator. 2. Let the app launch on the emulator.

Actual Result:

1. The app launches but clicking on the app gives "app has stopped responding". 2. We get the following logs in android monitor: 
10-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.
10-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.
10-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.)]
10-13 13:30:02.275: I/Process(1376): Sending signal. PID: 3089 SIG: 3
10-13 13:30:02.275: I/art(3089): Thread[2,tid=3095,WaitingInMainSignalCatcherLoop,Thread*=0xf77ffc90,peer=0x78d3f080,"Signal Catcher"]: reacting to signal 3
10-13 13:30:02.295: I/art(3089): Wrote stack traces to '/data/anr/traces.txt'
10-13 13:30:02.295: I/Process(1376): Sending signal. PID: 1376 SIG: 3
10-13 13:30:02.295: I/art(1376): Thread[2,tid=1382,WaitingInMainSignalCatcherLoop,Thread*=0x7f8d253e52f0,peer=0x76036080,"Signal Catcher"]: reacting to signal 3
10-13 13:30:02.525: I/Process(1376): Sending signal. PID: 1596 SIG: 3
10-13 13:30:02.525: I/art(1596): Thread[2,tid=1602,WaitingInMainSignalCatcherLoop,Thread*=0x7f8d253e6f80,peer=0x76034080,"Signal Catcher"]: reacting to signal 3
10-13 13:30:02.535: I/art(1376): Wrote stack traces to '/data/anr/traces.txt'
10-13 13:30:02.535: I/Process(1376): Sending signal. PID: 1580 SIG: 3
10-13 13:30:02.535: I/art(1580): Thread[2,tid=1583,WaitingInMainSignalCatcherLoop,Thread*=0x7f8d253e6f80,peer=0x76034080,"Signal Catcher"]: reacting to signal 3
10-13 13:30:02.535: I/art(1580): Wrote stack traces to '/data/anr/traces.txt'
10-13 13:30:02.535: I/Process(1376): Sending signal. PID: 1434 SIG: 3
10-13 13:30:02.535: I/art(1434): Thread[2,tid=1440,WaitingInMainSignalCatcherLoop,Thread*=0x7f8d253e6f80,peer=0x76034080,"Signal Catcher"]: reacting to signal 3
10-13 13:30:02.575: I/art(1434): Wrote stack traces to '/data/anr/traces.txt'
10-13 13:30:02.645: I/art(1596): Wrote stack traces to '/data/anr/traces.txt'
10-13 13:30:04.455: E/ActivityManager(1376): ANR in com.app.androidtesttwo (com.app.androidtesttwo/org.appcelerator.titanium.TiActivity)
10-13 13:30:04.455: E/ActivityManager(1376): PID: 3089
10-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.)
10-13 13:30:04.455: E/ActivityManager(1376): Load: 0.12 / 0.28 / 0.23
10-13 13:30:04.455: E/ActivityManager(1376): CPU usage from 44860ms to 0ms ago:
10-13 13:30:04.455: E/ActivityManager(1376):   0.7% 966/adbd: 0% user + 0.7% kernel / faults: 428 minor
10-13 13:30:04.455: E/ActivityManager(1376):   0.3% 2974/kworker/0:2: 0% user + 0.3% kernel
10-13 13:30:04.455: E/ActivityManager(1376):   0% 3089/com.app.androidtesttwo: 0% user + 0% kernel / faults: 734 minor 29 major
10-13 13:30:04.455: E/ActivityManager(1376):   0% 958/surfaceflinger: 0% user + 0% kernel / faults: 6 minor
10-13 13:30:04.455: E/ActivityManager(1376):   0% 1376/system_server: 0% user + 0% kernel / faults: 66 minor
10-13 13:30:04.455: E/ActivityManager(1376):   0% 1950/com.android.mms: 0% user + 0% kernel / faults: 30 minor
10-13 13:30:04.455: E/ActivityManager(1376):  +0% 3188/logcat: 0% user + 0% kernel
10-13 13:30:04.455: E/ActivityManager(1376): 100% TOTAL: 10% user + 89% kernel
10-13 13:30:04.455: E/ActivityManager(1376): CPU usage from 1680ms to 2190ms later:
10-13 13:30:04.455: E/ActivityManager(1376): 0% TOTAL: 0% user + 0% kernel
3. Tried running kitchensink too & I see the same behaviour as default app.

Expected Result:

1. The app should not stop responding & work successfully.

Attachments

FileDateSize
monkey.apk2014-10-13T18:57:46.000+0000834616

Comments

  1. Ping Wang 2014-10-22

    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. The original issue may be due to the bugs in L preview. Resolved the ticket as Invalid.
  2. Lokesh Choudhary 2014-10-27

    Verified that with the new android 5.0 64 bit emulator the default classic & alloy apps run fine without any errors. Closing.

JSON Source