Hi,
Sometimes when I open a folder DOpus will crash when generating thumbnails, and I'm not really sure what is causing it because it seems sporadic - that is, re-opening the same folder again may not lead to a crash.
I have a few dump files. Here's some output from one of them:
CONTEXT: (.ecxr)
rax=00007fff66661620 rbx=00007fff67ccf010 rcx=0000014b48590070
rdx=00000000000009db rsi=00000000000009db rdi=0000000000000000
rip=00007fff666ea8a8 rsp=00000042201fc440 rbp=00007fff67ccf000
r8=00000042201fc4b0 r9=0000014b4c1256a0 r10=0000000000000030
r11=00000042201fc440 r12=00000000fffffffd r13=0000000000000000
r14=00000042201fc4b0 r15=0000000082141014
iopl=0 nv up ei pl zr na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010246
XCShMain_x64!GetThumbnail+0x891a8:
00007fff`666ea8a8 ff5018 call qword ptr [rax+18h] ds:00007fff`66661638=41e800000058b9c3
Resetting default scope
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007fff666ea8a8 (XCShMain_x64!GetThumbnail+0x00000000000891a8)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
PROCESS_NAME: dopus.exe
READ_ADDRESS: ffffffffffffffff
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
This is what the stack looks like:
XCShMain_x64!GetThumbnail+0x891a8
XCShMain_x64!GetThumbnail+0x65f42
XCShMain_x64!GetThumbnail+0x66962
XCShMain_x64!GetThumbnail+0x869f0
XCShMain_x64!GetThumbnail+0x86595
XCShMain_x64!GetThumbnail+0x7fd2f
XCShMain_x64!GetThumbnail+0x7df30
XCShMain_x64!GetThumbnail+0x7c167
XCShMain_x64!GetThumbnail+0x41ad67
XCShMain_x64!GetThumbnail+0x416472
XCShMain_x64!GetThumbnail+0x41ac41
XCShMain_x64!GetThumbnail+0x1723
XCShMain_x64+0x71a6c1
XCShMain_x64+0x719fdf
XCShMain_x64+0x7357ea
windows_storage!InitializeFileHandlerWithStream+0x18e
windows_storage!CFileSysItemString::HandlerCreateInstance+0x1fb
windows_storage!CFileSysItemString::_PropertyHandlerCreateInstance+0xbf
windows_storage!CFileSysItemString::LoadHandler+0x298
windows_storage!CFSFolder::LoadHandler+0xd5
windows_storage!CFSPropertyStoreFactory::_GetFileStore+0x18a
windows_storage!CFSPropertyStoreFactory::_GetMultiplexPropertyStore+0x1ce
windows_storage!CFSPropertyStoreFactory::_GetPropertyStore+0xc6
windows_storage!CFSPropertyStoreFactory::GetPropertyStore+0x22
windows_storage!CShellItem::_GetPropertyStoreWorker+0xed
windows_storage!CShellItem::GetPropertyStore+0xcf
DropboxExt64_49_0!DllUnregisterServer+0x51a9
shell32!SHGetPropertyStoreFromParsingName+0x65
dopus!DummyExeFunction2ToAvoidSymbolConfusion+0x62b98
dopus!DummyExeFunction2ToAvoidSymbolConfusion+0x5e1ac
dopuslib!IsWow64+0x34
dopuslib!DummyDllFunctionToAvoidSymbolConfusion+0xbc20c
kernel32!BaseThreadInitThunk+0x10
ntdll!RtlUserThreadStart+0x2b
YMBOL_NAME: XCShMain_x64!GetThumbnail+891a8
MODULE_NAME: XCShMain_x64
IMAGE_NAME: XCShMain.x64.dll
STACK_COMMAND: ~35s ; .ecxr ; kb
FAILURE_BUCKET_ID: INVALID_POINTER_READ_c0000005_XCShMain.x64.dll!GetThumbnail
OS_VERSION: 10.0.22000.1
I originally thought this might be related to the PDF thumbnail handler, but now I'm not so sure.