-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Fix access violation when reporting fatal errors during startup #121602
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
Conversation
|
With this fix, we should see the following error message on unpatched Windows 10 machines: |
|
Tagging subscribers to this area: @mangod9 |
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.
Pull Request Overview
This PR fixes an access violation that occurs when ThreadStore::HoldingThreadStore() is called during early startup from HandleFatalError, before the thread store has been initialized.
Key changes:
- Added a null check for
s_pThreadStoreinHoldingThreadStore()to prevent dereferencing a null pointer during early startup error handling
|
/backport to release/10.0 |
|
Started backporting to |
|
/ba-g timeouts |
…g startup (#121605) Backport of #121602 to release/10.0 /cc @jkotas ## Customer Impact Allow customers to self-diagnose fail fasts encountered early during startup, such as running on unpatched Windows 10 machine that does not support CET correctly. This change fixes crash during printing of the fail fast error message early during startup. - [x] Customer reported - [ ] Found internally ## Regression - [ ] Yes - [x] No ## Testing Manual simulated test ## Risk Low Co-authored-by: Jan Kotas <[email protected]>
Fixes #121596