Skip to content

fix: handle Windows startup access violations - #1092

Open
abhiprd2000 wants to merge 1 commit into
CodebuffAI:mainfrom
abhiprd2000:fix/windows-startup-access-violation
Open

fix: handle Windows startup access violations#1092
abhiprd2000 wants to merge 1 commit into
CodebuffAI:mainfrom
abhiprd2000:fix/windows-startup-access-violation

Conversation

@abhiprd2000

Copy link
Copy Markdown

Summary

Fixes #1091.

On Windows, a 0xC0000005 (STATUS_ACCESS_VIOLATION) crash from the optimized binary during the startup window can indicate a CPU compatibility problem. The launcher already falls back to the baseline binary for 0xC0000409, but did not handle 0xC0000005.

This change:

  • treats 0xC0000005 as a startup CPU-feature crash
  • keeps the existing startup-time guard so normal runtime access violations are unaffected
  • adds regression coverage for the new fallback case

Signed-off-by: Abhimanyu Prasad <abhiprd2000@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

freebuff.exe crashes immediately with access violation (0xC0000005) on Windows x64

1 participant