-
Notifications
You must be signed in to change notification settings - Fork 19
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
librusty_vangers failing inside wgpu:command.rs #190
Comments
Does vange-rs work for you if you set GL in the config (as "backend: GL")? |
Road works fine on GL backend. |
I think there is some UB in my build, will look into it tomorrow |
Nope valgrind shows that there is no errors |
and it works in browser :) |
Could you reproduce this via https://github.com/lpenguin/rv_ffi ? |
I can reproduce it in rv_ffi. It fails from the commit 2341f55 (Water: first implementation). I pushed a small fix to it, so you may need a pull. |
Yep same here
|
looks like some memory stomping is taking place:
i.e. just printing the state leads to a core dump. This is unusual. |
Hm, it could be something from the C++ side also, I'll check it |
no, it's just my debugger being buggy. The logic bug is in wgpu-hal/gles. Fix is coming! |
Fixes in 671a10a, which carries gfx-rs/wgpu#2427 |
I compiled render-ng branch natively, but when I try to run it constantly fails with error:
Here:
GPU:
[2022-01-26T08:22:28Z INFO wgpu_hal::gles::adapter] Vendor: Intel
[2022-01-26T08:22:28Z INFO wgpu_hal::gles::adapter] Renderer: Mesa Intel(R) HD Graphics 620 (KBL GT2)
[2022-01-26T08:22:28Z INFO wgpu_hal::gles::adapter] Version: OpenGL ES 3.2 Mesa 21.2.
Full log
full-log.txt
The text was updated successfully, but these errors were encountered: