Help with high ANR rate

2dguy

ilusha Just basically ignoring it for now. Not going to touch anything until we start adding the next phase.
@Shaun_Max v33.1.1.300.

Shaun_Max

2dguy v33.1.1.300.

thats too old ? how do you maintain such low ANR rate even now? is that an app that just displays "Hello World" ? 😆

bontegames My most popular game (around 2K downloads a day) has an ANR rate of 0.08% and a crash rate of 0.02%

intriguing!

2dguy

Shaun_Max lol.. 😛 but it doesn't use Starling, it uses a custom game engine and Genome2D for rendering.

ma

Yeah our rates are about that too, one of our biggest client apps has 0.16 ANR and 0.05 crash. But yeah we use an ane for all sounds and music, once we did that a few years ago that dropped our rates considerably.

Shaun_Max

ma But yeah we use an ane for all sounds and music, once we did that a few years ago that dropped our rates considerably.

so are you saying it could be ANEs ?

ilusha

ma What version of the AIR SDK is used for those apps?

Shaun_Max

2dguy what could be wrong with our build?
@ilusha Please let me also know the cause if you find any!

ma

Shaun_Max No, sound playback was our biggest contributor to ANRs and when we changed to using an ANE instead of the Sound class our ANRs dropped significantly.

Shaun_Max

ma How did you identify that ?
in our case this issue is the top scorer : -

Input dispatching timed out (2a798be air.com.company.appname/air.com.company.appname.AppEntry (server) is not responding. Waited 10001ms for MotionEvent)

I can also see this :

is crashalytics causing this issue?
Any help ?

ma

Doubt it. Best if you can get the full report and ask Harman on github about it.

Shaun_Max

@ilusha Have you already reported any issue to Harman?

ilusha

Shaun_Max Yes, you can find some answers from Harman here: https://github.com/airsdk/Adobe-Runtime-Support/issues/1319

Right now we found that parsing of our game data takes more than 5 seconds on some old devices. But user needs to touch a screen like a crazy to see an ANR. So I don't thing that it matters.

We use an obfuscated swf. So maybe it has some effect. I'll let you know if I find anything.

bontegames

ilusha The main optimizations I did was making sure absolutely nothing is executed when the game is deactivated, so no calculations and stopping all sound.
I just went over all my games and they are into that same range (I have games with lots of vector art on the one hand and on the other hand also games games with pixelart and lots of calculations). I noticed one game with a higher percentage, and I saw I forget to stop the sound for that one (and only zeroed the volume) when deactivated.

Shaun_Max

bontegames what about a simple loading animation ...

private function onStageDeactivate(e:flash.events.Event):void {
        deactivated = true;
        star.stop(true);

        if (myRoot != null && myRoot.current_state != null) {
            myRoot.current_state.pause(); // pauses all sounds
            myRoot.showBlackScreen(); // displays a black screen with circulating loading animation
        } 

        pausedTime = flash.utils.getTimer();
    }

Shaun_Max

ok! i have created a new issue :-

https://github.com/airsdk/Adobe-Runtime-Support/issues/1470

bontegames

Shaun_Max I'm not sure, but what I do is really stop everything: no screen updates, no calculations and stop all sounds/music.

kupo_games

By far my most common problem is the following crash:
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)
libCore.so (offset 0x1000)

I'm using AIR 33.1.1.533. No idea what causes it, but my game is very large and complicated!
For some reason my Android console is not showing me a Crash or ANR rate - maybe because my app is still in testing and not fully published yet. I could try a newer version of AIR and see if that helps - I was already getting this crash before adding ANEs.

urikaduri

We managed to get our ANR rate down from 2.5% to about 0.4% (skimming the bad bahavior threshold). What brought us down was:
Updating to the newest versions of AIR
Postponing as many tasks as possible from the app launch where most anr's happen for us
Removing rewarded videos from the product completely
Removing unused and little used ANE's

So there is hope 🙂 Constantly testing ideas for a long period of time was the only way we got it down.

Shaun_Max

urikaduri Postponing as many tasks as possible from the app launch where most anr's happen for us

How did you do that? I mean which all functions you moved from app launch event

urikaduri

Well it's an open discussion if this actually helped we used to decode more swf's as one of the first tasks on login and now we do it more gradually. The new firebase has ANR reporting so it might give us better clarity as to where the ANR's actually occur.

The main progress by far was done by updating AIR SDK and removing ANEs

« Previous Page