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
Flutter android app crash with libc.so(abort+164) #100104
Comments
@flutter-symbolizer-bot android arm64 release |
@Howard2595 Sorry, only public members of Flutter org can trigger my services. Check your privacy settings as described here. |
@Howard2595 I am going ahead and closing this as already fixed. After upgrading if you still get same error, write in comments and I'll reopen it. |
Hi @darshankawar, Thanks for your reply. Regarding this issue, I will try to upgrade the flutter version to 2.10.3, but I have a curious question:
What's the reason for this? Thanks again for your reply. |
@Howard2595 some android versions have bugs in libunwindstack which result in slightly incorrect addresses printed in stack traces. Try to offset all PC values by 0x1000 and symbolize again. |
@flutter-symbolizer-bot android arm64 release |
crash from #100104 (comment) symbolized using symbols for
crash from #100104 (comment) symbolized using symbols for
|
@Howard2595 the bot seems to symbolize it correctly into something meaningful. you can see the comment here which explains why manual symbolization might produce nonsense results. |
Hi @mraleph, Thanks for your reply. Thanks again for your reply. |
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 |
We are also facing this crash problem. A static lock variable called I think we can use c++ 11 double-checked-locking and remove this global lock: |
Labeling it for further investigation based on above report and symbolicated crash log. |
AFAIK, there is no exit in Flutter code. But if there is one in native components or a plugin, there is nothing Flutter can do to sidestep this. The double checked locking (which may still be the right thing to do) will not remove the need for the mutex. |
I can not reproduce the crash because it never happens on my device.
but we are getting crashes from play console logs.
This problem is the same as #98271.
Devices seem to be mostly Samsung devices:
Samsung Galaxy S21+ 5G
,Samsung Galaxy S21 5G
,Samsung Galaxy S21 Ultra 5G
, Android versions are all 12(SDK 31).Flutter version: 2.10.0
Engine version: 776efd2
Here are the stack traces:
I tried symbolizing these stack traces using the 776efd2 android_arm64_release engine binaries from the 2.10.0 branch, but I still can't parse these stack traces.
The output of flutter doctor -v:
The text was updated successfully, but these errors were encountered: