Fix memory address issues when queuing events during Windows OS window creation.#1382
Merged
caffeinepills merged 1 commit intopyglet:masterfrom Nov 4, 2025
Merged
Conversation
benmoran56
approved these changes
Oct 29, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
As discussed in #1374 some events cannot be deferred or queued for later due to memory locations only being guaranteed for the duration of the call.
This should fix the initial issue to prevent garbage from being passed into a structure.
This should probably be looked at in the future to just remove the queue and allow events to run as intended, and handle the cases where some resources aren't available (such as
window.set_currentbeing called before a context is created).