Increase early window creation timeout to 30 seconds #243
+1
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is needed as of Intel Arc driver update 32.0.101.6559 as there is a regression causing OpenGL context initialization to take a very long time.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A regression was introduced in Intel Arc driver update 32.0.101.6559 which is causing OpenGL context initialization to take an extremely long time (~12 seconds) when starting Minecraft. This problem affects Vanilla as well, but only NeoForge has a window creation timeout, which results in the game being prematurely terminated.
As a short-term solution, this patch increases the timeout to 30 seconds, which is a long enough period for the driver to take care of what it needs to.
Note that the underlying problem here needs to be reported to Intel, as context creation shouldn't take this long. But seeing as they've rolled out this WHQL driver update, it is the unfortunate situation that we have to deal with it.