-
Notifications
You must be signed in to change notification settings - Fork 8.5k
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
Relax locking around the swapchain #5225
Conversation
The terminal lock is really only for the terminal; since the renderer is fully owned by the control, not the Terminal, and we'll only be receiving swap chain events after we register them during initialization, we don't need to lock before _or_ after firing off the coroutine. Fixes #5203.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yea I'm okay with this but pls make sure to add the GH# comment :)
} | ||
} | ||
|
||
// This event is only registered during terminal initialization, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
// This event is only registered during terminal initialization, | |
// See GH#5203 | |
// This event is only registered during terminal initialization, |
Because otherwise I'd forget why this is okay
This may not be entirely correct. |
I was wrong. It is not the cause of the crash in 5185. |
You mean #5203? |
@carlos-zamora no, I mean #5185. |
🎉 Handy links: |
Summary of the Pull Request
The terminal lock is really only for the terminal; since the renderer is
fully owned by the control, not the Terminal, and we'll only be
receiving swap chain events after we register them during
initialization, we don't need to lock before or after firing off the
coroutine.
PR Checklist
Validation Steps Performed
Manual validation.