-
-
Notifications
You must be signed in to change notification settings - Fork 234
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
'compile_shader' crash on Windows/MSYS2 #1032
Comments
Same problem here I believe - though Im using the visual studio build
Here is an example project which has the problem: Failing on an nvidia gtx (980) on windows |
Also using MSVC, using the tutorial code I seem to gotten different errors when running multiple times without rebuilding.
Windows 10 64-bit, GTX 670M, Driver version 361.91 |
Yes sometimes (maybe 1 out of 5 times) it actually Does start :S (without rebuild). But most of the time it doesn't. I tried with both stable rust 1.8 and nightly 2.0 with the exact same results, so maybe this is caused by the MSVC integration somehow.. |
The one thing I don't understand is why developers of Piston ignore this thread. They (or he) are the ones who know best how their engine works. |
@lem0nify Been busy. We have encountered a compiler bug concerning corrupted memory before, see gfx-rs/gfx#574. It could be something that only affects MSVC. The process used to find it might be of help rust-lang/rust#22536. The opengl_graphics backend has an "image_test" example, https://github.com/PistonDevelopers/opengl_graphics/blob/master/examples/image_test.rs, which might be a starting point for reducing the test case. If there is a compiler bug, but not something wrong with the GLSL compiler inside the driver, then a such reduced example would be of great help for the Rust team. |
@bvssvni So what should I do? |
@lem0nify Try remove code from your fork of opengl_graphics and the "image_test" example until you have the minimum amount of code required that trigger the bug. |
@bvssvni Sorry I can't remove parts from your code correctly because I don't fully understand rust, piston, opengl, glsl and only start to learn them. So I can only notice that this error is glsl log putted in buffer by gl::GetShaderInfoLog (shader_utils.rs, line 150) but it happens only with textured/150_core.glslv shader (back_end.rs, line 137). Can you please try to investigate the reason? |
@lem0nify PistonDevelopers/opengl_graphics#236 fixed a possible dangling pointer. Do you still get the error? |
@bvssvni No I don't get it since your prevous reference. Thank you. |
I'm trying to make any piston application work on msys.
I installed freetype and mingw64 gcc tools on msys2 using pacman, then built rust and cargo from sources, as said in your getting-started tutorial. Everything went fine.
Then I've built spinning-square example with
cargo build
. This finished without any errors (just some warnings about#[allow(raw_pointer_derive)]
) but when I try to run it, I see (always different) runtime errors about 'compile_shader' fuction. There are some examples of them:Any changes in OpenGL version in code don't affect result. Other piston applications (e.g. rust-2048) don't work the same way.
I find it strange that I always see different errors without even recompile.
On my linux laptop everything works fine and I have such problems only on Windows/MSYS2. I have also tryed to compile and run simple OpenGL application written in C here but it works fine too.
I use Windows 8.1 64bit, my video card is GeForce GTX 770 and the last driver (361.75) is installed.
Sorry for my bad english.
So what could be the problem and how to fix it? Hope for your help.
The text was updated successfully, but these errors were encountered: