-
Notifications
You must be signed in to change notification settings - Fork 406
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
crash on macOS 10.14.2 (18C54) at debug_assert!(backend.is_current()); #1721
Comments
The deprecation seems unrelated, seems it's related to glutin's In the meantime you can compile with --release, the debug assertion will compile away and it seems to work perfectly well. Can it be a race condition on the time the context becomes current and when the assertion is performed? Can you give us a bit a guidance here @mitchmindtree? |
Seems that the root cause of this is now fixed in Glutin 0.20.0 (Changelog, so once Glium upgrades that dependency this should be ok. |
The upstream library glutin have finished this. Please update glium to 0.24.0 I will close this issues. Please see: |
The old work-around had a serious performance issue because every draw call triggered a redundant call to `Context::make_current`.
/glium-0.23.0/src/context/mod.rs:647:17
I use edition = "2018" and glium = "0.23.0"
It seems that
unsafe { backend.make_current() };
not effect.full stacks:
source code is:
The text was updated successfully, but these errors were encountered: