-
-
Notifications
You must be signed in to change notification settings - Fork 686
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
internal/graphicsdriver/opengl/gl: crash on Galaxy A02s #3052
Comments
With Ebitengine 856b339:
|
https://android.googlesource.com/platform/bionic/+/refs/heads/main/libc/include/dlfcn.h My guess is that /CC @TotallyGamerJet |
Even with C's RTLD definitions, another crash happened.
I'll try to replace all the dlopen part with C version later. |
In v2.7, PureGo is not used for this part https://github.com/hajimehoshi/ebiten/blob/2.7/internal/graphicsdriver/opengl/gl/procaddr_linbsd.go |
A quick solution is to just revert the change in procaddr_linbsd. I wonder if this is a sign that arguments are not being passed correctly in arm64. Perhaps trying purego.SyscallN instead of RegisterFunc. It’s unclear from the last error if this is a call to an OpenGL function or to Dlopen |
I've confirmed that the fix worked on Test Lab. |
I've almost reverted the Android part, but not non-Android Linux part. So, there might still be an issue on Linux, but I don't know what machines an issue. On Linux, the constants |
https://community.infiniteflight.com/t/i-cannot-download-if-because-its-not-compatible/710435/4
|
This is basically a revert for 297efea. This updates PureGo for the Android issue. Updates #3052 Updates ebitengine/purego#262
Ebitengine Version
v2.8.0-alpha.2
Operating System
Go Version (
go version
)go version go1.22.4 darwin/arm64
What steps will reproduce the problem?
Run an Android application with Ebitengine on Galaxy A02s
What is the expected result?
No crash
What happens instead?
Crash on launching
Anything else you feel useful to add?
I've confirmed this on Firebase Test Lab with our Ebitengine application.
The text was updated successfully, but these errors were encountered: