Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
ANRs on Android #965
All our apps still have many ANRs (Input dispatching timed out & Broadcast of Intent types) on Android. The AIR team answer regarding this is that one should avoid any heavy calculations in the mouse_down, mouse click, key_down, etc. events and delay the calculations to avoid freezing the input.
From what I see, Starling already delays touch input handling to the next frame.. but we still get lots of ANRs. All our inputs are handled via Starling. Is there anything left to improve in Starling? Should one consider queuing the touch events in seperate setTimout calls instead of processing all of them in the next frame like currently?
Any other advice related to these dreaded ANRs?
Thanks for your help Daniel! :)
The thing is also that I get the impression not many devs actually take the time to dig into the ANR/Crashes/logs to figure out what it causing issues. I'm pretty sure this issue is wide spread among AIR apps but most people don't even know about it.
It's not a huge amount (less than 1% of users on a daily basis) but it generally seems to impact the same users (example: 1100 ANRs, concerning 700 users), which drives them crazy and earns us bad reviews.
Also, it's basically the only ANR remaining and the only cause of crashing in our apps at the moment.
I totally agree, this needs to be addressed!
Before I do that, though, is there a possibility to get some information about the devices where this occurs? Some model / vendor information? I know it's hard to get on Android, but maybe you've got something in place already, and I'm sure that would help Adobe fix this.
Got it, thanks! I already forwarded the information to Adobe.
Nevertheless: please create the same report at "tracker.adobe.com" and then post the link here. Adobe needs that for internal reasons, and any time we can save them is a win. Thanks in advance!