-
-
Notifications
You must be signed in to change notification settings - Fork 682
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
windows: Crash at launching #836
Comments
Further details:
|
Just tested on a Virtualbox Windows 10 VM with the same error. The error does not come from the game loop function, I wrapped all errors returned with context to better trace them. This error comes directly from the ebiten RUN func. |
I think there is an issue in your audio device (that is used by both your host machine and VM). I am not sure.
The low-layer device is created and initialized lazily, and Run initializes the device. |
I tested in 3 different machines with the same result:
I am still trying to reproduce this with a minimal example. |
Oh that's interesting... Thank you for testing. |
So the audio device should not matter. I'm looking forward the minimal example to reproduce this issue. |
Hello again,
I also have created an example project to reproduce it. How can I send it to you @hajimehoshi? |
Hi, thank you for investigating!
As https://godoc.org/github.com/hajimehoshi/ebiten/audio#NewPlayer says:
I'm not sure why the lower device complains in such situation, but I think I can create a better error message.
I appreciate it! Could you mail to hajimehoshi@gmail.com, or share that on GitHub or something? |
Hi, It is also strange that on mac OS X and Linux this is not a problem. Thanks for looking into it. |
I think this was fixed by ebitengine/oto#73 |
This is a temporary fix for #836. After relasing Oto v0.3.3, update go.mod again and cherry-pick this onto 1.9 branch.
I let this issue open until releasing a new version of Oto and cherry-picking the fix onto 1.9 branch. |
Tested again in different Windows machines and it fixed in all of them! |
Borja Clemente reported:
Windows 10 (64bit, intel i7 processor)
The text was updated successfully, but these errors were encountered: