Skip to content

CI (Win32): register ProcDump as the postmortem debugger so crashes leave a dump - #247

Open
matthargett wants to merge 1 commit into
BabylonJS:mainfrom
rebeckerspecialties:ci-win32-procdump
Open

matthargett wants to merge 1 commit into
BabylonJS:mainfrom
rebeckerspecialties:ci-win32-procdump

Conversation

@matthargett

@matthargett matthargett commented Sep 16, 2026

Copy link
Copy Markdown

Problem

build-win32.yml enables WER LocalDumps for UnitTests.exe, but on the runner image no .dmp appeared for a plain access violation (an intermittent Hermes crash in the fork's Worker tests, exit 0xC0000005): the *-crash-dumps artifact only ever contained the exe and pdb, so the crash could not be diagnosed post mortem.

Change

A step downloads Sysinternals ProcDump and registers it as the just-in-time (AeDebug) debugger writing full dumps into the same Dumps folder the artifact step uploads. That path does not depend on WER's policy, needs no change to how the tests are launched, and leaves the process exit code untouched. The WER registration stays.

Workflow-only change. Fork twin: rebeckerspecialties#31.

…eave a dump

The WER LocalDumps registration produced no .dmp on the runner image for
a plain access violation, so the "crash dumps" artifact only ever held
the exe and pdb. ProcDump installed as the AeDebug handler writes a full
dump for any crashing process regardless of WER's policy; the existing
upload step picks it up from the same folder.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

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.

2 participants