https://bugs.documentfoundation.org/show_bug.cgi?id=172071

--- Comment #12 from Nicklas Johnson <[email protected]> ---
FWIW here's the exception data from the Windows event viewer for two out of
three crashes:

Faulting application name: soffice.bin, version: 26.2.2.2, time stamp:
0x69c03618
Faulting module name: MFPlay.DLL, version: 10.0.26100.8115, time stamp:
0x1e7c97b2
Exception code: 0xc0000005
Fault offset: 0x000000000002dcf1
Faulting process id: 0x25AC
Faulting application start time: 0x1DCE3BFC18EE7A4
Faulting application path: C:\Program Files\LibreOffice\program\soffice.bin
Faulting module path: C:\WINDOWS\SYSTEM32\MFPlay.DLL
Report Id: d8d64170-082c-40f4-bf9a-ca65660bb5d2
Faulting package full name: 
Faulting package-relative application ID: 

The other crash produced this output instead:

Faulting application name: soffice.bin, version: 26.2.2.2, time stamp:
0x69c03618
Faulting module name: mergedlo.dll, version: 26.2.2.2, time stamp: 0x69c035f0
Exception code: 0xc0000005
Fault offset: 0x0000000000bb2243
Faulting process id: 0x55E8
Faulting application start time: 0x1DCE3B2EFF83DEC
Faulting application path: C:\Program Files\LibreOffice\program\soffice.bin
Faulting module path: C:\Program Files\LibreOffice\program\mergedlo.dll
Report Id: bcf5cff0-6275-4b67-9c58-963bd890a97b
Faulting package full name: 
Faulting package-relative application ID: 

The memory faulting within MFPlay.DLL seems like it would suggest some issue
interacting with Media Foundation Playback on Windows in particular.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to