-
Notifications
You must be signed in to change notification settings - Fork 49
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
GToolkit crash on startup - glutin loads an unrelated libGLE.dll from PATH #973
Comments
Note this is the implementation of Another option would be to change glutin-sys to avoid optimistically loading libEGL (and only do it if asked to) |
This issue has been moved to feenkcom/libglutin#2 |
No. Please keep it here. |
I opened an issue in glutin itself rust-windowing/glutin#1292 |
Verified that using the fixed glutin version (syrel/glutin#1) in |
Great to hear! |
Would you be able to try again? We have changed quite a bit of things in the meantime. |
@NightRa: This issue is likely addressed now. Please let us know if you still encounter problems with starting GT. |
Scenario: Downloaded release, GToolkit.exe crashes on startup.
While debugging it, I noticed that there were unrelated library loads:
C:\Program Files\SciTools\bin\pc-win64\libEGL.dll
C:\Program Files\SciTools\bin\pc-win64\libGLESv2.dll
The flow which causes this load is:
glutin_create_headless_context (libGlutin) -> build_headless (glutin_sys) -> new_headless -> EGL lazy static -> LoadLibrary
In
new_headless
, if no windowed sharing was specified, it tries to loadlibEGL.dll
from the load path, which in my case was in PATH from another program (SciTools Understand for reading code), so it used it instead of the windows-based solution which is typically used in Pharo - and it led to a crash later on.From
new_headless
:The fallback flow of
new_headless
is the following:So a solution to avoid the use of EGL is to use
build_windowed -> new_windowed
instead ofbuild_headless
inlibGlutin
withwith_visible(false)
- and this would avoid the usage of libEGL.In the meantime, removing SciTools Understand from PATH is a workaround for the issue.
The text was updated successfully, but these errors were encountered: