While using Writer 5.0.6.2, full profile with extensions, I got procdump. Writer didn't crash. Reason I'm using procdump is because I got crash on that file. I cannot reproduce but I get a crash rather frequently, mostly on paste, maybe related to tracked changes. Microsoft (R) Windows Debugger Version 6.3.9600.16384 X86 Comment: procdump.exe soffice.bin -h soffice.bin.dmp *** Hung window detected: 30784' User Mini Dump File: Only registers, stack and portions of memory are available ************* Symbol Path validation summary ************** Symbol search path is: CACHE*C:\symbols;SRV*http://dev-builds.libreoffice.org/daily/master/Win-x86@39/symbols;SRV*http://dev-downloads.libreoffice.org/symstore/symbols;SRV*http://msdl.microsoft.com/download/symbols Windows 7 Version 7601 (Service Pack 1) MP (8 procs) Free x86 compatible Product: WinNt, suite: SingleUserTS Debug session time: Tue May 17 14:19:47.000 2016 (UTC + 2:00) Process Uptime: 0 days 2:05:10.000 ................................................................ Loading unloaded module list . eax=00000000 ebx=139ba1b0 ecx=00000000 edx=00000000 esi=0e014810 edi=00000000 eip=7718000e esp=00e6efc0 ebp=00e6efd8 iopl=0 nv up ei pl zr na pe nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00200246 ntdll!ZwFlushBuffersFile+0x12: 7718000e 83c404 add esp,4 0:000> !analyze -v ******************************************************************************* * * * Exception Analysis * * * ******************************************************************************* *** ERROR: Symbol file could not be found. Defaulted to export symbols for soffice.bin - GetUrlPageData2 (WinHttp) failed: 12029. FAULTING_IP: +408b5cc71150000 00000000 ?? ??? EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff) ExceptionAddress: 00000000 ExceptionCode: 80000003 (Break instruction exception) ExceptionFlags: 00000000 NumberParameters: 0 CONTEXT: 00000000 -- (.cxr 0x0;r) eax=00000000 ebx=139ba1b0 ecx=00000000 edx=00000000 esi=0e014810 edi=00000000 eip=7718000e esp=00e6efc0 ebp=00e6efd8 iopl=0 nv up ei pl zr na pe nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00200246 ntdll!ZwFlushBuffersFile+0x12: 7718000e 83c404 add esp,4 FAULTING_THREAD: 00001b18 DEFAULT_BUCKET_ID: STATUS_BREAKPOINT PROCESS_NAME: soffice.bin ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached. EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid NTGLOBALFLAG: 0 APPLICATION_VERIFIER_FLAGS: 0 APP: soffice.bin ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre PRIMARY_PROBLEM_CLASS: STATUS_BREAKPOINT BUGCHECK_STR: APPLICATION_FAULT_STATUS_BREAKPOINT LAST_CONTROL_TRANSFER: from 7570df72 to 7718000e STACK_TEXT: 00e6efc0 7570df72 000005c4 00e6efd0 00000000 ntdll!ZwFlushBuffersFile+0x12 00e6efd8 74b4468d 000005c4 00e6f008 5dc0790e KERNELBASE!FlushFileBuffers+0x55 00e6efe4 5dc0790e 000005c4 2c75baa2 5dc01ed0 kernel32!FlushFileBuffersImplementation+0x62 00e6f008 5268b2fa 0e014810 2c75baff 00000000 sal3!osl_syncFile+0x5e 00e6f194 5268246e 04b8bbe8 5dc00510 05a8cd50 mergedlo!SfxMedium::Transfer_Impl+0xe2a 00e6f1bc 526d5320 2c75b9a7 01166760 139ba1b0 mergedlo!SfxMedium::Commit+0x6e 00e6f2cc 526cfbb1 139ba1b0 13797f38 2c75b85f mergedlo!SfxObjectShell::SaveTo_Impl+0x19b0 00e6f334 526d5a81 13797f38 2c75b807 13797f38 mergedlo!SfxObjectShell::DoSave_Impl+0x2e1 00e6f36c 5270a35a 13797f38 2c75b883 138158f0 mergedlo!SfxObjectShell::Save_Impl+0x211 00e6f3e8 526af125 06e24368 00e6f608 2c75be93 mergedlo!SfxBaseModel::storeSelf+0x6aa 00e6f5f8 526c893f 06e24358 05b39b50 07bf4da0 mergedlo!SfxStoringHelper::GUIStoreModel+0x465 00e6f988 526cae5e 139ba3c0 00e6f9e4 5258da4c mergedlo!SfxObjectShell::ExecFile_Impl+0x11af 00e6f994 5258da4c 01166760 139ba3c0 2c75b28f mergedlo!SfxStubSfxObjectShellExecFile_Impl+0xe 00e6f9e4 525903f9 01166760 0003d800 139ba3c0 mergedlo!SfxDispatcher::Call_Impl+0x24c 00e6fa24 5258ff7e 139ba3c0 00e6fa44 52727642 mergedlo!SfxDispatcher::PostMsgHandler+0xa9 00e6fa30 52727642 068ecee8 139ba3c0 0f9d82f0 mergedlo!SfxDispatcher::LinkStubPostMsgHandler+0xe 00e6fa44 534ac117 067ad428 139ba3c0 049e0b28 mergedlo!SfxHintPoster::LinkStubDoEvent_Impl+0x32 00e6fa58 534ac612 0f9d82f0 2c75b1d3 00000000 mergedlo!ImplHandleUserEvent+0x37 00e6fab8 53790b59 00aeaf58 04aeb0d8 00000016 mergedlo!ImplWindowFrameProc+0x3e2 00e6fad0 53793416 000601c0 0f9d82f0 00000482 mergedlo!ImplHandleUserEvent+0x29 00e6fb10 53793a00 000601c0 00000482 00000000 mergedlo!SalFrameWndProc+0x746 00e6fb5c 751f62fa 000601c0 00000482 00000000 mergedlo!SalFrameWndProcW+0x60 00e6fb88 751f6d3a 537939a0 000601c0 00000482 user32!InternalCallWinProc+0x23 00e6fc00 751f77c4 00000000 537939a0 000601c0 user32!UserCallWinProcCheckWow+0x109 00e6fc60 751f788a 537939a0 00000000 00e6fca4 user32!DispatchMessageWorker+0x3bc 00e6fc70 5375eae4 00e6fc88 01177168 00000001 user32!DispatchMessageW+0xf 00e6fca4 5375f34c 00000001 00000000 557dfbf0 mergedlo!ImplSalYield+0x64 00e6fcc8 536e535b 00000001 00000000 04aa9570 mergedlo!WinSalInstance::Yield+0xac 00e6fce0 527bb822 2c75b50f 557dfbf0 01114273 mergedlo!Application::Execute+0x5b 00e6fe64 536ebf19 2c75b5e7 00000000 01114273 mergedlo!desktop::Desktop::Main+0xd92 00e6fe8c 536ec2b9 002e6148 00e6ff08 527d6d09 mergedlo!ImplSVMain+0x49 00e6fe98 527d6d09 2c75b463 01114273 549bc090 mergedlo!SVMain+0x29 00e6ff08 0011101e 01114273 001112b2 00110000 mergedlo!soffice_main+0x79 WARNING: Stack unwind information not available. Following frames may be wrong. 00e6ff5c 74b4337a 7efde000 00e6ffa8 77199882 soffice+0x101e 00e6ff68 77199882 7efde000 7701be75 00000000 kernel32!BaseThreadInitThunk+0xe 00e6ffa8 77199855 00111183 7efde000 00000000 ntdll!__RtlUserThreadStart+0x70 00e6ffc0 00000000 00111183 7efde000 00000000 ntdll!_RtlUserThreadStart+0x1b STACK_COMMAND: ~0s; .ecxr ; kb FOLLOWUP_IP: sal3!osl_syncFile+5e [c:\cygwin64\home\buildslave\source\libo-core\sal\osl\w32\file.cxx @ 747] 5dc0790e 85c0 test eax,eax FAULTING_SOURCE_LINE: c:\cygwin64\home\buildslave\source\libo-core\sal\osl\w32\file.cxx FAULTING_SOURCE_FILE: c:\cygwin64\home\buildslave\source\libo-core\sal\osl\w32\file.cxx FAULTING_SOURCE_LINE_NUMBER: 747 FAULTING_SOURCE_CODE: No source found for 'c:\cygwin64\home\buildslave\source\libo-core\sal\osl\w32\file.cxx' SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: sal3!osl_syncFile+5e FOLLOWUP_NAME: MachineOwner MODULE_NAME: sal3 IMAGE_NAME: sal3.dll DEBUG_FLR_IMAGE_TIMESTAMP: 57209543 FAILURE_BUCKET_ID: STATUS_BREAKPOINT_80000003_sal3.dll!osl_syncFile BUCKET_ID: APPLICATION_FAULT_STATUS_BREAKPOINT_sal3!osl_syncFile+5e ANALYSIS_SOURCE: UM FAILURE_ID_HASH_STRING: um:status_breakpoint_80000003_sal3.dll!osl_syncfile FAILURE_ID_HASH: {96ce6e48-1ddb-de4c-68c3-1575deed0c0f} Followup: MachineOwner ---------
It would be nice if someone could confirm that this is useful.
the interesting thing is this: Hung window detected: presumably the main thread is blocked from processing Win32 messages. i'd guess that this was caused by Idle/Timer refactoring in VCL in 5.0. it is quite likely to be fixed in 5.1 already. please re-open if you can reproduce it in 5.1 or later.