PostQuitMessage is a message, not a return. The fallback CreateDevice
posted one and then carried straight on into the Clear below it, so a
machine that could not give us the mode we asked for dereferenced a
device that was never created and died on an access violation instead of
saying what had happened. The quit message it had just posted would not
be read until someone pumped the queue, which by then nobody would.
Both attempts are now judged once, and the line names the size that was
REFUSED. That is the question this failure raises rather than an
incidental detail: the back buffer is the requested size windowed as
well as full-screen since the render target went back to being the size
that was asked for, so a request the adapter will not meet is the first
thing to look at.
DPLRenderer: no D3D device for a 2560x1440 windowed back buffer
(hr=0x8876086c) - giving up
mDevice was also never in the initialiser list, so until CreateDevice
wrote it the member held whatever was on the stack - and the
mPrimaryIndex bail-out above has always returned through that into the
destructor's SAFE_RELEASE. It is nulled before either exit can be taken.
Found while reading the constructor for an unrelated crash, which turned
out to be on another thread. This one is latent - no report of it yet -
but it is the difference between a tester sending a dump and a tester
sending a line that says what to fix.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
CydandClaude Opus 5
3482de5147