[
https://issues.apache.org/jira/browse/CB-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493794#comment-13493794
]
Lindsey Simon commented on CB-1185:
-----------------------------------
I got some logs here, but I don't see anything immediately useful in my mind
from them.
Note - I got this by running our app for like 1.5 hrs in the background, going
in and out of network availability.
Logs were captured by CatLog.
If it's useful to know, we start a WAKE_LOCK when our app is running in the
background.
11-08 21:00:36.930 I/InputDispatcher( 643): Application is not responding:
Window{429eb608 com.twist.android/com.twist.android.TwistDroidActivity
paused=false}. 20010.5ms since event, 20009.9ms since wait started
11-08 21:00:36.930 I/InputDispatcher( 643): Current inboundQueue's length is
19, outboundQueue's length is 1
11-08 21:00:36.930 I/InputDispatcher( 643): outboundQueue 0: inProgress is 1,
type is 3 (429eb608 com.twist.android/com.twist.android.TwistDroidActivity
(server))
11-08 21:00:36.930 D/InputDispatcher( 643): [onANRLocked] initialize
cntPair(sender-receiver)
11-08 21:00:36.930 I/WindowManager( 643): Input event dispatching timed out
sending to XXX.XXXXX.XXXXXXX/XXX.XXXXX.XXXXXXX.XXXXXXXXXXXXXXXXXX
... more logs ...
then:
11-08 21:00:39.243 I/Process ( 643): Sending signal. PID: 21749 SIG: 3
11-08 21:00:39.243 I/dalvikvm(21749): threadid=3: reacting to signal 3
11-08 21:00:39.253 I/dalvikvm(21749): Wrote stack traces to
'/data/anr/traces.txt'
11-08 21:00:39.263 I/InputReader( 643): Touch event's action is 0x1
(deviceType=0) [pCnt=1, pending(waiting finished signal)=0, s=]
11-08 21:00:39.263 E/LocSvc_adapter( 643): I/<--- void globalEventCb(void*,
uint32_t, locClientEventIndUnionType, void*) line 88 QMI_LOC_EVENT_NMEA_IND_V02
11-08 21:00:39.263 E/LocSvc_eng( 643): D/void
loc_eng_deferred_action_thread(void*):1405] received msg_id =
LOC_ENG_MSG_REPORT_NMEA context = 0x1340bf0
11-08 21:00:39.263 E/LocSvc_eng( 643): I/<=== nmea_cb line 1581 0x17be5a8
11-08 21:00:39.263 E/LocSvc_adapter( 643): I/<--- void globalEventCb(void*,
uint32_t, locClientEventIndUnionType, void*) line 88 QMI_LOC_EVENT_NMEA_IND_V02
11-08 21:00:39.263 E/LocSvc_eng( 643): D/void
loc_eng_deferred_action_thread(void*):1405] received msg_id =
LOC_ENG_MSG_REPORT_NMEA context = 0x1340bf0
11-08 21:00:39.263 E/LocSvc_eng( 643): I/<=== nmea_cb line 1581 0x1cfbbf0
11-08 21:00:39.263 E/LocSvc_adapter( 643): I/<--- void globalEventCb(void*,
uint32_t, locClientEventIndUnionType, void*) line 88 QMI_LOC_EVENT_NMEA_IND_V02
11-08 21:00:39.263 E/LocSvc_eng( 643): D/void
loc_eng_deferred_action_thread(void*):1405] received msg_id =
LOC_ENG_MSG_REPORT_NMEA context = 0x1340bf0
11-08 21:00:39.263 E/LocSvc_eng( 643): I/<=== nmea_cb line 1581 0x16601f0
11-08 21:00:39.263 D/lights ( 643): write_int
/sys/class/leds/button-backlight/brightness = 255
11-08 21:00:39.263 E/android.os.Debug( 643): !@Dumpstate > dumpstate -k -t -z
-d -o /data/log/dumpstate_app_anr
11-08 21:00:39.263 D/lights ( 643): write_int
/sys/class/leds/button-backlight/brightness = 0
11-08 21:00:39.263 D/QMI_FW ( 643): QCCI: reader_thread: Received 80 bytes
from 309
11-08 21:00:39.263 D/QMI_FW ( 643): QCCI: QMI_CCI_RX: cntl_flag - 04, txn_id
- 0000, msg_id - 0026, msg_len - 0049
11-08 21:00:39.263 D/QMI_FW ( 643): QCCI: reader_thread: Received 75 bytes
from 309
11-08 21:00:39.263 D/QMI_FW ( 643): QCCI: QMI_CCI_RX: cntl_flag - 04, txn_id
- 0000, msg_id - 0026, msg_len - 0044
11-08 21:00:39.263 D/QMI_FW ( 643): QCCI: reader_thread: Received 69 bytes
from 309
11-08 21:00:39.263 D/QMI_FW ( 643): QCCI: QMI_CCI_RX: cntl_flag - 04, txn_id
- 0000, msg_id - 0026, msg_len - 003e
11-08 21:00:39.263 E/ActivityManager( 643): ANR in com.twist.android
(com.twist.android/.TwistDroidActivity)
11-08 21:00:39.263 E/ActivityManager( 643): Reason: keyDispatchingTimedOut
11-08 21:00:39.263 E/ActivityManager( 643): Load: 3.14 / 2.9 / 2.62
11-08 21:00:39.263 E/ActivityManager( 643): CPU usage from 11495ms to 0ms ago
with 99% awake:
11-08 21:00:39.263 E/ActivityManager( 643): 18%
21749/com.nolanlawson.logcat: 15% user + 2.3% kernel / faults: 473 minor
11-08 21:00:39.263 E/ActivityManager( 643): 3.9% 643/system_server: 2% user
+ 1.9% kernel / faults: 49 minor
11-08 21:00:39.263 E/ActivityManager( 643): 2.6% 332/surfaceflinger: 1.5%
user + 1% kernel
11-08 21:00:39.263 E/ActivityManager( 643): 1.7% 21792/logcat: 0.7% user +
0.9% kernel
11-08 21:00:39.263 E/ActivityManager( 643): 1.2% 1366/mpdecision: 0% user +
1.2% kernel
11-08 21:00:39.263 E/ActivityManager( 643): 1.2% 10756/logcat: 0.7% user +
0.4% kernel
11-08 21:00:39.263 E/ActivityManager( 643): 1.2% 18271/logcat: 0.5% user +
0.6% kernel
11-08 21:00:39.263 E/ActivityManager( 643): 1.2% 21768/logcat: 1% user +
0.1% kernel
11-08 21:00:39.263 E/ActivityManager( 643): 1.1% 11670/logcat: 0.4% user +
0.6% kernel
11-08 21:00:39.263 E/ActivityManager( 643): 0.8% 15175/logcat: 0.2% user +
0.6% kernel
11-08 21:00:39.263 E/ActivityManager( 643): 0.6% 946/com.android.phone: 0.3%
user + 0.2% kernel / faults: 8 minor
11-08 21:00:39.263 E/ActivityManager( 643): 0.6%
9718/com.google.android.apps.maps:GoogleLocationService: 0.4% user + 0.1% kernel
11-08 21:00:39.263 E/ActivityManager( 643): 0.4% 19053/kworker/0:1: 0% user
+ 0.4% kernel
11-08 21:00:39.263 E/ActivityManager( 643): 0% 454/rmt_storage: 0% user + 0%
kernel
11-08 21:00:39.263 E/ActivityManager( 643): 0.3% 779/com.android.systemui:
0.3% user + 0% kernel / faults: 4 minor
11-08 21:00:39.263 E/ActivityManager( 643): 0.2% 86/irq/299-mms_ts: 0% user
+ 0.2% kernel
11-08 21:00:39.263 E/ActivityManager( 643): 0.1% 448/sdcard: 0% user + 0%
kernel
11-08 21:00:39.263 E/ActivityManager( 643): 0.1% 16530/com.nytimes.android:
0% user + 0% kernel
11-08 21:00:39.263 E/ActivityManager( 643): 0% 96/mmcqd/0: 0% user + 0%
kernel
11-08 21:00:39.263 E/ActivityManager( 643): 0% 747/hdmid: 0% user + 0% kernel
11-08 21:00:39.263 E/ActivityManager( 643): 0% 888/com.google.process.gapps:
0% user + 0% kernel
11-08 21:00:39.263 E/ActivityManager( 643): 0% 18274/kworker/u:1: 0% user +
0% kernel
11-08 21:00:39.263 E/ActivityManager( 643): 0% 21154/kworker/u:2: 0% user +
0% kernel
11-08 21:00:39.263 E/ActivityManager( 643): 0% 21283/com.smlds: 0% user + 0%
kernel / faults: 20 minor
11-08 21:00:39.263 E/ActivityManager( 643): 0% 21565/kworker/u:3: 0% user +
0% kernel
11-08 21:00:39.263 E/ActivityManager( 643): 19% TOTAL: 12% user + 5.3% kernel
+ 1.6% iowait
11-08 21:00:39.263 E/ActivityManager( 643): CPU usage from 1741ms to 2273ms
later:
11-08 21:00:39.263 E/ActivityManager( 643): 5.6% 643/system_server: 0% user
+ 5.6% kernel / faults: 1 minor
11-08 21:00:39.263 E/ActivityManager( 643): 7.5% 712/InputDispatcher: 1.8%
user + 5.6% kernel
11-08 21:00:39.263 E/ActivityManager( 643): 0.8% 1366/mpdecision: 0% user +
0.8% kernel
11-08 21:00:39.263 E/ActivityManager( 643): 1.1%
21749/com.nolanlawson.logcat: 1.1% user + 0% kernel
11-08 21:00:39.263 E/ActivityManager( 643): 1.1% 21749/anlawson.logcat:
1.1% user + 0% kernel
11-08 21:00:39.263 E/ActivityManager( 643): 7.1% TOTAL: 2% user + 5.1% kernel
I have the mentioned /data/anr/traces.txt file, but I've never read one of
those before so I'm not sure what to make of it - but happy to send to someone
if it might be useful.
fwiw, I tried to replicate it a second time, and had the app running for longer
even, but it didn't cause the lockup - slippery little bug!
> When Application is placed in background and resumed, the UI is frozen
> ----------------------------------------------------------------------
>
> Key: CB-1185
> URL: https://issues.apache.org/jira/browse/CB-1185
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
> Affects Versions: 2.0.0
> Environment: Jelly Bean 4.1, ICS 4.0.x
> Reporter: Greg
> Assignee: Filip Maj
> Fix For: 2.3.0
>
> Attachments: 0001-Fix-issue-with-pause-resume-freezing-the-UI.patch,
> 0002-Uncomment.patch, cordova-2.0.0.jar
>
>
> When using PhoneGap 2.0.0 on ICS or JellyBean, the application freezes up
> after you set the app to the background or turn of the screen. After around
> 3-7 seconds, the application unfreezes and pretty much causes a panic and
> usually crashes. No error reports have been submitted.
> Here is how you re-produce the issue:
> 1. Download Untappd -
> V2.0.4(https://play.google.com/store/apps/details?id=com.untappdllc.app)
> 2. After logging in stay on the Friends tab
> 3. Turn the the screen off and wait about 3-7 minutes
> 4. Turn the screen back on, and the interface should be frozen.
> Another possible path to re-producing the issue:
> 1. Download Untappd -
> V2.0.4(https://play.google.com/store/apps/details?id=com.untappdllc.app)
> 2. After logging in stay on the Friends tab
> 3. Go back to the home screen then use other apps for about 3-7 minutes.
> 4. Go back into Untappd, and the interface should be frozen.
> When the app is frozen, native menu buttons will not nor any options in the
> UI.
> Would love to see if anyone can replicate this. I've tested this on Jelly
> Bean 4.1.x on a Samsung Galaxy Nexus, but users have been having this problem
> majority on ICS (4.0.x)
> Thanks,
> Greg
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
