-
Notifications
You must be signed in to change notification settings - Fork 28.5k
Flutter android app crashes with (abort+160) (abort+180) (abort+116) (abort+166) ... #98271
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @medst, thanks for filing the issue. Please provide the output of Thank you |
Hi, I'm upvoting @medst issue because I have the exact same error reported in the Play Console.
The output of
I'm getting a lot of these stacktraces since version 2.10 of the SDK, with Android 9, 10, 11 and a large set of phones. |
The output of flutter doctor -v:
|
@flutter-symbolizer-bot engine#776efd2034 #98271 (comment) android release arm64 |
@jason-simmons Sorry, only public members of Flutter org can trigger my services. Check your privacy settings as described here. |
@flutter-symbolizer-bot engine#776efd2034 #98271 (comment) android release arm64 |
There were failures processing the requestWhen processing #98271 (comment) I found crash
but failed to symbolize it with the following notes:
but failed to symbolize it with the following notes:
but failed to symbolize it with the following notes:
but failed to symbolize it with the following notes:
but failed to symbolize it with the following notes:
See my documentation for more details. |
I tried symbolizing these stack traces using the The That implies that these crashes were due to memory allocation failures. |
Hi @medst, can we get a list of devices that are affected and their OS versions? |
I have the same issue
The list of some devices:
|
Labeling for further investigation. |
Per @jason-simmons last comment, the only lead we have so far is that this is an OOM situation. Closing this as no progress is be possible here without a reproducible or reduced test case. Feel free to reopen once either is available. |
this error is not happening on my device, so what part of my code can i share with you ? i think this issue has a relation with google mobile ads package. |
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
I can not reproduce the crash because it never happens on my device.
but we are getting crashes from play console logs
most devices getting this crash and almost every type of devices are receiving these crashes
The text was updated successfully, but these errors were encountered: