Skip to main content
K
KiNgEyK
Participating Frequently
October 10, 2012
Question

Android app for Adobe AIR 'Locks Up'

  • October 10, 2012
  • 5 replies
  • 7188 views

It appears as if the application I am developing on AIR for Android locks up intermittently. There is no crash on the ActionScript side at all. Looking at the output from logcat doesn't show anything either. It basically gets into a state where the game music (played through ActionScript/AIR) continues to play, but all buttons, events, timers, etc. fail to work. It almost seems like the framerate has gone to 0 (or close to it). I did not receive any USER_IDLE / USER_PRESENT / ACTIVATE / DEACTIVATE events from NativeApplication however. I've submitted a bug here.

I'm REALLY stumped on this one.. If anyone has experiences similar hangs/crashes with Adobe AIR for Android, I'd love to hear from you about how you fixed it.

    This topic has been closed for replies.

    5 replies

    p0L
    p0L
    Known Participant
    August 3, 2015

    Same problems here, loads of crashes with libhoudini.so

    A
    AlesSetinc1
    Participant
    March 22, 2015

    I'm getting the same behavior, more than 50 crashes per day. I'm using Adobe AIR 15...
    Massive problem as app just freezes during game...

    K
    KiNgEyKAuthor
    Participating Frequently
    October 11, 2012

    Not sure if this helps at all..

    I/ActivityManager(  608): No longer want com.android.gallery3d (pid 18891): hidden #16

    W/ActivityManager(  608): Activity pause timeout for ActivityRecord{4100ca98 air.com.blitzoo.SSMQA/.AppEntry}

    W/ActivityManager(  608): Activity stop timeout for ActivityRecord{4100ca98 air.com.blitzoo.SSMQA/.AppEntry}

    I/ActivityManager(  608): Activity reported stop, but no longer stopping: ActivityRecord{4100ca98 air.com.blitzoo.SSMQA/.AppEntry}

    W/ActivityManager(  608): Activity idle timeout for ActivityRecord{4100ca98 air.com.blitzoo.SSMQA/.AppEntry}

    E/ActivityManager(  608): ANR in air.com.blitzoo.SSMQA

    E/ActivityManager(  608): Reason: Broadcast of Intent { act=android.intent.action.SCREEN_OFF flg=0x50000010 }

    E/ActivityManager(  608): Load: 0.82 / 0.67 / 0.76

    E/ActivityManager(  608): CPU usage from 10293ms to 832ms ago:

    E/ActivityManager(  608):   5.4% 19100/kworker/u:3: 0% user + 5.4% kernel

    E/ActivityManager(  608):   5.2% 21186/air.com.blitzoo.SSMQA: 3.9% user + 1.3% kernel / faults: 1 minor

    E/ActivityManager(  608):   3.8% 250/mediaserver: 1% user + 2.7% kernel

    E/ActivityManager(  608):   2.7% 608/system_server: 1.3% user + 1.3% kernel / faults: 20 minor

    E/ActivityManager(  608):   1.9% 23366/dhd_dpc: 0% user + 1.9% kernel

    E/ActivityManager(  608):   1.5% 21196/kworker/u:4: 0% user + 1.5% kernel

    E/ActivityManager(  608):   1.3% 1387/mpdecision: 0% user + 1.3% kernel

    E/ActivityManager(  608):   0.5% 21180/kworker/0:1: 0% user + 0.5% kernel

    E/ActivityManager(  608):   0.2% 881/com.android.systemui: 0.2% user + 0% kernel / faults: 1 minor

    E/ActivityManager(  608):   0% 1019/com.android.nfc: 0% user + 0% kernel / faults: 7 minor

    E/ActivityManager(  608):   0.2% 16253/adbd: 0% user + 0.2% kernel / faults: 16 minor

    E/ActivityManager(  608):   0.2% 19519/com.doubleTwist.androidPlayer: 0.2% user + 0% kernel / faults: 31 minor

    E/ActivityManager(  608):   0.2% 23365/dhd_watchdog: 0% user + 0.2% kernel

    E/ActivityManager(  608):   0% 53/irq/675-esd_det: 0% user + 0% kernel

    E/ActivityManager(  608):   0.1% 98/mmcqd/0: 0% user + 0.1% kernel

    E/ActivityManager(  608):   0% 246/rild: 0% user + 0% kernel / faults: 2 minor

    E/ActivityManager(  608):   0.1% 247/surfaceflinger: 0% user + 0.1% kernel / faults: 2 minor

    E/ActivityManager(  608):   0% 992/com.android.inputmethod.latin: 0% user + 0% kernel / faults: 5 minor

    E/ActivityManager(  608):   0% 1145/com.google.process.gapps: 0% user + 0% kernel

    E/ActivityManager(  608):   0% 3427/com.latedroid.juicedefender: 0% user + 0% kernel / faults: 3 minor

    E/ActivityManager(  608):   0% 20810/com.google.android.apps.maps:GoogleLocationService: 0% user + 0% kernel / faults: 8 minor

    E/ActivityManager(  608):   0.1% 21195/kworker/u:1: 0% user + 0.1% kernel

    E/ActivityManager(  608):  +0% 21731/flush-0:16: 0% user + 0% kernel

    E/ActivityManager(  608):  +0% 21732/flush-179:96: 0% user + 0% kernel

    E/ActivityManager(  608): 17% TOTAL: 4.6% user + 12% kernel + 0% softirq

    E/ActivityManager(  608): CPU usage from 1819ms to 2348ms later with 99% awake:

    E/ActivityManager(  608):   13% 608/system_server: 3.7% user + 9.4% kernel / faults: 94 minor

    E/ActivityManager(  608):     3.7% 615/Compiler: 0% user + 3.7% kernel

    E/ActivityManager(  608):     3.7% 660/ActivityManager: 0% user + 3.7% kernel

    E/ActivityManager(  608):     1.8% 617/FinalizerDaemon: 1.8% user + 0% kernel

    E/ActivityManager(  608):   5.4% 19519/com.doubleTwist.androidPlayer: 5.4% user + 0% kernel / faults: 32 minor

    E/ActivityManager(  608):     4.1% 14888/8-16-166: 4.1% user + 0% kernel

    E/ActivityManager(  608):   2.2% 250/mediaserver: 2.2% user + 0% kernel

    E/ActivityManager(  608):     1.1% 603/FastMixer: 0% user + 1.1% kernel

    E/ActivityManager(  608):     1.1% 674/AudioOut_2: 1.1% user + 0% kernel

    E/ActivityManager(  608):   2.8% 21186/air.com.blitzoo.SSMQA: 1.4% user + 1.4% kernel

    E/ActivityManager(  608):     2.8% 21223/FP_AudioCallbac: 2.8% user + 0% kernel

    E/ActivityManager(  608):     1.4% 21222/AudioTrack: 0% user + 1.4% kernel

    E/ActivityManager(  608):   1.2% 881/com.android.systemui: 0% user + 1.2% kernel

    E/ActivityManager(  608):     1.2% 881/ndroid.systemui: 1.2% user + 0% kernel

    E/ActivityManager(  608):   1.8% 1387/mpdecision: 0% user + 1.8% kernel

    E/ActivityManager(  608):     1.8% 1395/mpdecision: 0% user + 1.8% kernel

    E/ActivityManager(  608):   1.4% 21180/kworker/0:1: 0% user + 1.4% kernel

    E/ActivityManager(  608):   1.8% 23366/dhd_dpc: 0% user + 1.8% kernel

    E/ActivityManager(  608): 17% TOTAL: 8.3% user + 9.3% kernel

    A
    Arthur_Flower
    Participant
    October 17, 2012

    I am having the same issue with an Andoid app. This is critical and it's driving me crazy because the app crashes also when in idle. I have tested this on a large range of device with Honeycomb and Ics. The bug is related to AIR runtime 3.4. The only way I had to avoid the crash uninstall air 3.4 and install the 3.1 runtime on the tablet/phone.

    Please fellow coders show some solidarity and vote for my bug:

    https://bugbase.adobe.com/index.cfm?event=bug&id=3348496

    Thanks

    Message was edited by: Arthur_Flower

    chris.campbell
    Community Manager
    chris.campbellCommunity Manager
    Community Manager
    October 18, 2012

    I've asked our team to take a look at this bug (3348496).  I'd like to recommend anyone else encountering this issue to take a minute and leave a comment/vote in the bug report.

    K
    KiNgEyKAuthor
    Participating Frequently
    October 11, 2012

    The last 3 times I checked out the 'main' thread during a hang, I noticed that  the thread was in the middle of the handleMessage / callTimeoutFunction of the com.adobe.air.customHandler class. Not sure if that helps at all..

    K
    KiNgEyKAuthor
    Participating Frequently
    October 11, 2012

    So in order to find out a little more information about what is happening I took at look at the threads. The 'main' thread upon which AIR runs does indeed seem to be 'stuck' as the utime and stime reported by DDMS no longer count up, and remain the same once the application stops responding. The AudioTrack thread continues to operate normally, with utime and stime counting up while the audio plays fine in the background.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices