Some analysis from Steven on the latest trp that I'm still digesting...
>> Is this an alignment problem?
> Not sure yet. The trap appears to be happening at
> https://github.com/psmedley/qt6-webengine-os2/blob/6.4.x/src/3rdparty/chromium/third_party/blink/renderer/platform/graphics/parkable_image_manager.cc#L33
> but not sure why yet...
FWIW, the caller is:
src\3rdparty\chromium\third_party\blink\renderer\platform\exported\platform.cc:251
base::trace_event::MemoryDumpManager::GetInstance()->RegisterDumpProvider(
&ParkableImageManager::Instance(), "ParkableImages",
base::ThreadTaskRunnerHandle::Get());
I think the generated code in the constructor is trying implement a "fast
memset" to clear the instance object. The PXOR clears the XMM0 and the
MOVAPS instructions zero 16-byte chunks of memory. This is going to be
faster than the rep movsd we typically see.
The problem here is that 0xfb31248 needs to be 16-byte aligned and it's
not.