-
Notifications
You must be signed in to change notification settings - Fork 932
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
Crashes on Windows 10 1809 10.0.17763.1 #1458
Labels
B - bug
Dang, that shouldn't have happened
DS - windows
F - duplicate
This issue or pull request already exists
Comments
chrisduerr
added a commit
to chrisduerr/winit
that referenced
this issue
Feb 13, 2020
In general, winit should never assert on anything unless it means that it is impossible to continue the execution of the program. There are several assertions in the Windows dark mode code where this is not the case. Based on surface level inspection, all existing assertions could be easily replaced with just simple conditional checks, allowing the execution of the program to proceed with sane default values. Fixes rust-windowing#1458.
Cc #1405. |
goddessfreya
added
DS - windows
F - duplicate
This issue or pull request already exists
B - bug
Dang, that shouldn't have happened
labels
Feb 13, 2020
chrisduerr
added a commit
to chrisduerr/winit
that referenced
this issue
Feb 17, 2020
In general, winit should never assert on anything unless it means that it is impossible to continue the execution of the program. There are several assertions in the Windows dark mode code where this is not the case. Based on surface level inspection, all existing assertions could be easily replaced with just simple conditional checks, allowing the execution of the program to proceed with sane default values. Fixes rust-windowing#1458.
chrisduerr
added a commit
to chrisduerr/winit
that referenced
this issue
Mar 7, 2020
In general, winit should never assert on anything unless it means that it is impossible to continue the execution of the program. There are several assertions in the Windows dark mode code where this is not the case. Based on surface level inspection, all existing assertions could be easily replaced with just simple conditional checks, allowing the execution of the program to proceed with sane default values. Fixes rust-windowing#1458.
Osspial
pushed a commit
that referenced
this issue
Mar 7, 2020
* Remove assertions from Windows dark mode code In general, winit should never assert on anything unless it means that it is impossible to continue the execution of the program. There are several assertions in the Windows dark mode code where this is not the case. Based on surface level inspection, all existing assertions could be easily replaced with just simple conditional checks, allowing the execution of the program to proceed with sane default values. Fixes #1458. * Add changelog entry * Format code * Pass dark mode by mutable reference * Format code * Return bool instead of mutable reference * Fix dark mode success reply Co-Authored-By: daxpedda <daxpedda@gmail.com> * Fix dark mode success reply * Replace magic integers with constants Co-authored-by: daxpedda <daxpedda@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
B - bug
Dang, that shouldn't have happened
DS - windows
F - duplicate
This issue or pull request already exists
This was reported upstream in alacritty/alacritty#3177.
It seems like on some Windows 10 systems, like Windows 10 Enterprise LTSC 1809, the new dark mode options are causing an assertion panic.
This assert is failing:
winit/src/platform_impl/windows/dark_mode.rs
Lines 135 to 138 in 83b60be
The text was updated successfully, but these errors were encountered: