First run of this rig that was actually holding the instrument it claims.
Four pods under real full page heap - flags 0x3 in every cdb log, set by
elevated gflags, not the PEB trick that has stopped working - driven hard
enough to score 553..997, podium on.
Everything the diagnosis points at ran: four placed on the stand, the local
pod given its exterior (the podium's second MakeEntityRenderables pass, which
is the path the dumps finger), the full Application::Shutdown teardown, four
clean exits. No exception on any pod.
That is worth more than the earlier clean runs by some distance. Full page
heap traps a double free at the second free AND an overrun at the guard page,
in the culprit's own stack rather than in the victim's. Neither fired. So on
four pods over loopback with one teardown each, this bug does not happen.
It also settles the address-space question the rig kept running into: 2 works,
4 works, 6 dies. The population that actually crashed and the instrument that
would catch it cannot be had at the same time on one machine.
Left to try, in order of what is cheap: repetition, because a single sample of
an intermittent fault is nearly nothing; then three real machines, where the
podium and its teardown land at genuinely different moments per pod instead of
loopback's near-simultaneous nothing.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
CydandClaude Opus 5
74948fdd10