com.ansca.corona.CoronaService ANR affects 20k users

Btw, this is different crash, we tried to deal with ANR in 3306.

Could you tell trend, like if you started to get more or less crashes and/or ANRs?

For me all ANRs are gone with 3306, so it definitely helped a lot.

Best regards!

Also, please , use pastebin for crash reports. They’re getting ugly formatted and hard to copy. 

Hi vlads,

like I mentioned in another thread, this seems to be helping on those ANR issues. However, it brings new problems with Stuck partial wake locks (background) regarding AudioMix.

Please see my response in the other thread:

https://forums.coronalabs.com/topic/72856-lots-of-anrs-on-android-packagestatechangedservice-androidintentactionscreen-off/?p=383107

Best regards!

I’m seeing the same thing. Possibly related: I checked my phone today, and one of my apps (which I used on Friday last week) is still draining battery in the background. It doesn’t show up in the task switcher, but I can get a PID from adb:

$ adb shell ps -A

u0_a170      26283   707 1974136  24308 0                   0 S se.appfamily.puzzle.super2.free

And logcat shows audio stuff going on in the background (to re-iterate, I’ve not opened the app for 3 days):

$ adb logcat | grep 26283

06-04 12:58:45.657 26283  8331 W AudioTrack: dead IAudioTrack, PCM, creating a new one from processAudioBuffer()

06-04 12:58:45.665 26283 26296 W AudioSystem: ioConfigChanged() closing unknown output 453

06-04 12:58:45.679 26283  8331 W AudioTrack: AUDIO_OUTPUT_FLAG_FAST denied, rates do not match 44100 Hz, require 48000 Hz

06-04 12:58:45.684 26283  8331 D AudioTrack: Client defaulted notificationFrames to 3592 for frameCount 10776

06-04 12:58:46.000 26283  8503 W AudioTrack: dead IAudioTrack, PCM, creating a new one from getPosition()

06-04 12:58:46.004 26283  8503 D AudioTrack: Client defaulted notificationFrames to 3675 for frameCount 11025

[member=‘Perflubron’],  3311 seems to fix that.

My testing seems to back this up.  I see no backgrounded Corona processes eating battery.

On a personal note, it seems recent daily builds seem to break other areas and that makes me sad.

Seems they are more rushed than tested properly.  As (paying) users of the Corona platform we shouldn’t be alerting you to bugs that could easily be found by basic automated testing.

Things like “Oh this recent daily build doesn’t work on Android 4” shouldn’t really be a thing with modern automated testing tools.

For us devs this ends up with 1 star reviews and angry customers :frowning:

Stability is critical!

SGS, I second that. Stability is key. Having said that, daily builds are afaiu not guaranteed to be suitable for production use.

In some situations, however, daily builds are necessary due to things like GDPR. And the problem is made worse for people who know nothing about these forum bug posts, and just pick the latest daily to ‘catch-up’ with all recent things. We as users have no way of knowing if a daily will be good or not. They might suddenly get all these issues introduced by an experimental fix, and have no idea what happened.

This leads me to suggest that there should be two types of builds:

  • Daily builds. Least stable, can contain experimental stuff.

  • Interim releases / tested daily builds. Created when events inbetween releases demand a daily build to be used until next release. Medium stability, no experimental stuff. Tested to a reasonable extent.

IMHO this doesn’t need to be a complicated setup with new download areas or such. Just a note in a daily builds text that this particular daily is more stable / tested.

A second suggestion is for Corona to use custom builds and work with specific pilot users when testing experimental fixes. It is inefficient that SGS, davebollinger, Bjoern, myself, etc all act as guinea pigs when Corona want to know if a certain bugfix works or not. So, before putting a fix in daily builds, put it in a custom build which your pilot users can use to update an app and verify if the fix worked or not. Once it is verified as working, deploy it to daily builds.

It might feel to the other users like the fixes take a bit longer to implement, but I believe they’d be happier if the fixes worked first time.

3311 appears to improve the situation, but wake locks still above threshold

Our ANRs are almost NIL thanks to the Corona team’s recent builds.

May I know which daily build version is everyone using now?

@Rob & @CoronaLabs, I’m happy to report that my new game Update with one of the most recent Corona builds has resulted in ZERO (0) ANRs after a week - about 1000 installs.This is fantastic news. THANK YOU! I will start a new thread about the 2 crashes that remain.