Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
x/mobile/example/audio: build on windows system,run CRASH #12514
Is someone get the same error when running the example of "Audio" ?
I am not sure is this the issues from gomobile,or other reason?
However, on Windows, do I need to do something similarly?
I am using the newest gomobile package and keep to update everyday.
First of all, about the "al: cannot load libopenal.so".
So sorry for my development environment.
Now , the crash is still exist. It seems that is due to a error "Fatal signal 11".
Thank you sincerely.
Could you file a different bug with the steps to produce this case, please? It is a fatal case and must be fixed.
Could you share details about your test device -- brand, model, Android version and similar? The audio package is currently tested only on ARM devices. As far as I can see, you have an x86 device with ARM emulation.
o(∩_∩)o Hi, rakyll. Thank you for your reply.
My test device
Mmm, yes, they are both the x86 architecture.
Lost the "libopenal.so" file
The reproduce step is simple:
I feel sorry that the network limit us to access the "*.Google.com".We have to modify the HOSTS file frequently or use vpn to access it .
I file a different bug with the quick reproduce steps,click the link here please: #12550
Thank you sincerely :)
run other apps on my test device
I did not known which android game or app is used OpenAL. So these few days, I try to search and test different apks.
This debug apk crash due to other problem, but in the message of logcat, I could see that it seems can run OpenAL well.
The last two message of the log above,
new result build with newest gomobile
I update newest gomobile yesterday. Now, audio example will NOT CRASH! But also have NO any SOUND.
The audio_20150905.apk will crash,messages of logcat is already writed down above the comment ;
Is it in arm device, the audio example is still everything ok with newest gomobile ?
Thank you sincerely :)
I was not able to test it with an x86 Android device yet, so still cannot reproduce and give you more details. The non-deterministically of the crash looks like there are other possible problems you have spotted.
The OpenAL loading strategy we use (https://github.com/golang/mobile/blob/master/exp/audio/al/al_android.go#L25), is looking under
The log above lists
(Note: OpenAL loading strategy we use is immature and not well tested across different devices, we should rather invoke System.loadLibrary through JNI or replicate its behavior.)
Hi , @rakyll :)
As the result of
Then I use a root explorer to check
Mmm... I unzip the 'audio_20150905.apk' and found the 'libopenal.so' file in it, but after be installed it 's not in lib directory. It is the key case crash?
Thanks for the details.
It is the crash case. The audio might be buggy for looking under
I don't have much context why there is no sound in the arm-emulating device yet though.
just for your reference/information:
So basically, the original loading strategy you mentioned in the comment above [https://github.com//issues/12514#issuecomment-140202336] might well be correct, as long as you can make sure that libaudio.so and libopenal.so end up in the same directory in the apk (and then, consequently, on the device). I think the code commit mentioned above does just that, so might close this issue as well. On the contrary, using System.loadLibrary might lead to other issues, like having to make sure that nativeLibraryPath/Directory contains the correct values or mistakenly loading an incompatible library version from another place, isn't it?