-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
x/mobile: apps crash with malloc deadlock on Android #10469
Comments
Not reporting stacktrace is worrisome - hopefully we figure out why there is no log and fix the problem before the freeze if possible. Can you provide a sample app and file a separate issue for it? You can assign the bug to me. Thanks! |
go get -d github.com/rakyll/gomobilebugs/b10469 for a sample app to reproduce. |
I got the crash logs Tested Nexus5/lollipop and Nexus7/kitkit and they exhibit different types Nexus5 I/ActivityManager( 744): START u0 {act=android.intent.action.MAIN Nexus 7/kitkat I/ActivityManager( 6833): Start proc org.golang.todo.main for activity I/DEBUG (13729): Build fingerprint: 2015-04-15 16:18 GMT-04:00 Burcu Dogan [email protected]:
__ |
and apk built with gomobile. 2015-04-16 16:16 GMT-04:00 Hyang-Ah Hana Kim [email protected]:
__ |
I have reinited gomobile and am able to see a similar crash log as soon as app launches. go version devel +7f983f2 Fri Apr 17 04:31:48 2015 +0000 darwin/amd64 Nexus 9, kernel version: 3.10.40, android version: 5.0.2. |
Failed to append the log last night, doing it now.
|
The basic example crashes with the log below.
|
I guess the malloc deadlock is a red herring. The preceding log message may be the more interesting one. F/libc (12348): Fatal signal 11 (SIGSEGV), code 2, fault addr 0x7af3c000 in tid 12365 (Thread-1452) Now we are going through many changes in the main and the mobile repositories, let's continue debugging after the dust settles. |
FWIW, I'm unable to reproduce the crashes on
Running gomobile tip (4e56a5f1a) and Go tip (3115952) |
Still reproducible on Nexus 9 - Android 5.0.2 and Nexus 9 - Android 5.1.1. |
Is this still reproducible? If it is, the cause seems like a core Go problem and according to https://groups.google.com/forum/#!topic/golang-dev/fcIhmOnwhK8 the 1.5 beta is close and I would prefer the (possible) fix for this issue not get rejected because of stricter CL standards. I'd happily do the debugging myself, but I don't have access to a Nexus 9. |
@rakyll can you check if it's still reproducible on your Nexus 9? |
I don't have an Android device with me currently, will give it a try this evening. |
I can't reproduce this bug, closing. |
We've also seen this happen on ARM with Go 1.5.1, the issue seems unrelated to gomobile. Should we open a new issue about this? |
@fjl yes please, and any way to reproduce it would be appreciated. |
Opened #13143. |
My application crashes without a stack trace after device rotation if it doesn't register for orientation changes in the AndroidManifest.xml. It is only reproducible if the current activity's orientation is set to a value such as
android:screenOrientation="landscape"
in my case.Update: Each Android apk that is built with gomobile crashes. It outputs a log with malloc deadlock. See #10469 (comment).
The text was updated successfully, but these errors were encountered: