ajwfrost
commented
8 months ago Hi
Looking at the backtrace, this is a crash happening during the garbage collection process. But the nature of that process is such that we can't tell what object is being cleaned up.. it's likely that the error happens where an object is being processed which still has a hanging reference open to an object which itself had been cleaned up previously...
It was quite some jump between versions there. Can I check whether anything else changed or is the runtime update the only change that was made?
Also just wondering whether you use any ANEs, and in particular whether you maintain any references to ActionScript objects from within the extension objects (within the C or Java code, if you are writing these yourselves)?
If you have any other crash logs it may be useful, sometimes we'd spot the object that's being corrupted if the crash is timing-related.
thanks
mohossama
Problem Description
Upgrading from Air SDK 33.1.1.575 to 50.2.4.1 caused our GooglePlay user-perceived crash rates to spike from <0.5% to ~8% and rising.
Which AIR SDK did you use? Air SDK 50.2.4.1. Building on windows.
Describe the affected environment: Android vs. iOS, all devices vs. just specific models. Android. No clear pattern of device models or Android versions being affected more than others. Both our 64-bit and 32-bit APKs seem to be similarly affected.
Can you reproduce it yourself, or did you get reports from other users? If so, how many users are affected (percentage)? We're unable to reproduce it locally.
What we have now is the backtrace from GooglePlay. They mostly look like this:
We cannot tell from the backtrace what possible behavior can be triggering this, so any hints to help reproduce it are welcome, if the backtrace tells you anything about that. We're also willing to help in other ways. e.g. if you can provide us (privately?) with debug symbols we can upload to GooglePlay to get clearer stack traces.