I have also seen it in previous versions, perhaps in all 5 releases. And possibly in other components, say calc and draw. The problem is that libreOffice seem to work flawlessly, including successfully opening files. At some point, perhaps after running a few days flawlessly, when trying to open a document that is not in its recent documents list, it freezes. To be more precise, it shows the window where one can browse the file system and select a file to open. And after the selection, as if it has started to load the file, it freezes. At the freeze point, the file selection window partially erased, as in the picture at http://i.imgur.com/6NmygMW.jpg. The task manager will then show 2 libreoffice non responding processes. The way I overcome this problem is to end both tasks. The non responding program, end or cancel window is then shown for each of the tasks. Choosing end task will eventually kill them. Then libreoffice can be started again, and the whole thing will repeat after a few days of running flawlessly, when trying to open some, possibly other, file, that is not a recent document.
It happened again some time ago. This time, while trying to open a calc (ods) file. If that matter, there was one writer (odt) file opened, and I tried to File -> Open, navigate to the desired file, double clicking it, and had a similar window to the image in my previous report. It froze while partially erased.
Who it hang like that, I can't see the lock file for the document created. I assu,e the lock file is created in the same directory the file is in. I hope this information will help narrowing where the problem is.
In the previous comment, Who it hang ... -> When it hang ...
Do you mean "after running continuously for a few days"? Ie. not shutting down the computer of LibreOffice. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the information.
Hi ronvarburg, Thank you for reporting the crasher. Can you provide me with more info about which version you are running. Simply copy and paste the version information found in Help > About LibreOffice. Also can you let me know which version of Windows you are running. If you are able to reproduce the crash consistently, it would be good if you can provide a debug report for us using the steps found in the below, webpage. https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg
I mean after LibreOffice runs for a few days, not shutting down neither the computer of LibreOffice, nor LibreOffice. I manage to run XP SP3 for weeks, perhahs more, without shutting it down. And the shutdown are intended, not a crash of XP. And LibreOffice runs for days flawlessly. Most of the time LibreOffice sits idle and _minimized. From time to time I maximize it, edit a file, or 3, for a few minutes, and _minimizes it again. My edits of each file are usually short, and the files themselves are short too. I would say that 65% of the files I edit within a few days are at the recent files list. From time to time I have to use open, and browse the file system.
I had 5.1.1. Unfortunately, I also have http://portableapps.com/ installed, which I prefer. I used it for for a long time. I update the http://portableapps.com/ version when it has new ones. The problem began with some portableapps version. Following the suggestion at http://portableapps.com/node/53825, I installed upstream == yours 5.1.1. After some time, when the problem occurs 2 or 3 times, I removed your version, and returned to the portableapps.com one. I returned to Version: 5.1.0.3 Build ID: 5e3e00a007d9b3b6efb6797a8b8e57b51ab1f737 CPU Threads: 1; OS Version: Windows 5.1; UI Render: default; Locale: en-US (en_US). I had it before installing yours version. When I run your version, it was installed in parallel, and I had not use it. Note that portableapps apps are meant to be install on a portable device like a USB disk on key, so it doesn't keep information in the registry, or similar intrusive methods. strangely, before installing your version, I had Build ID: 5e3e00a007d9b3b6efb6797a8b8e57b51ab1f737 hangs in the same manner that is described in the report. Though I think I am again running it more time then I expected the freeze to occur, it still hasn't hang.
Few hours ago I reported I am a bit surprised it still didn't happen. Now it did. And after the hang clicking the close window, red X at the right corner of the window to choose the file produced the end program, not responding, End now or Cancel, window.
A non related issue is that after I killed it and started LinreOffice again, it suggested to recover the file that was opened before the freeze. I refused , and it suggested to keep the version it had, or something to that effect. The point is that it suggested to keep the file at D:\Documents. Which is only part of the directory name. The directory name is Documents and Settings. I think you should have enclose Documents and Settings within quotation marks: "Documents and Settings". It could be that it works under the cover. What I saw about the directory name seem to me wrong.
Hi ronvarburg, It is hard for us to assist you when you arent providing an real clues on why or when it is happening. If we cant accurately reproduce the problem then unfortunately it wont get fixed.
Can you tell if Yousuf (Jay) Philips suggestion from 2016-03-02 20:03:20 UTC (Comment 5) to produce a debug report using the steps found in https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg is likely to work with portableapps.com Version: 5.1.0.3 Build ID: 5e3e00a007d9b3b6efb6797a8b8e57b51ab1f737? Unfortunately, I totally forgot I should try to provide the debug info when I had the problem few hours ago. I was hasty doing the work I had to do. I just skimmed https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg. Looks like I have to do some installation, including .net. I think I will start winDbg just before I am trying to open a file, and stop it if the opening succeeds. Will that work? Your instructions mention starting both winDbg and LibreOffice concurrently. I also hope I will remember to run WinDbug whenever opening a file. Does stopping winDbg straight forward, or would you like to write some instructions on doing that?
Sure, you can start debugging just before trying to reproduce the problem. You stop by just closing Windbg. It should work fine with the portableapps version.
You suggest to set winDbg to CACHE*C:\symbols;SRV*http://... Here, C:\ is mostly empty. D:\ is the main disk. Should I change to CACHE*D:\symbols;SRV*http://... I hope this is not a too dumb question.
(In reply to ronvarburg from comment #13) > You suggest to set winDbg to > CACHE*C:\symbols;SRV*http://... > Here, C:\ is mostly empty. D:\ is the main disk. Should I change to > CACHE*D:\symbols;SRV*http://... > I hope this is not a too dumb question. Which ever drive you want to put it on, thats fine. C: is mentioned as that is normally the drive that Windows is installed on.
1. I think you should have mentioned that WinDng will ask to save something to the workspace after attaching to it. Does accepting the suggestion OK? 2. Although you mentioned that WinDbg might be used when LibreOffice hang, you didn't supply full instructions for that case. Here is what happened: I was about to open a document by browsing the file system. I clicked open, navigated to the directory the file to be opened was in, and then started WinDbg. I saw only a single soffice.bin process. Attached it to WinDbg, and clicked to open the file. The last few lines I got in the WinDbg window so far were: (b60.b10): Break instruction exception - code 80000003 (first chance) eax=7ffd9000 ebx=00000001 ecx=00000002 edx=00000003 esi=00000004 edi=00000005 eip=7c90120e esp=0724ffcc ebp=0724fff4 iopl=0 nv up ei pl zr na pe nc cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246 ntdll!DbgBreakPoint: 7c90120e cc int 3 0:012> g (b60.fd8): C++ EH exception - code e06d7363 (first chance) (b60.fd8): C++ EH exception - code e06d7363 (first chance) (b60.fd8): C++ EH exception - code e06d7363 (first chance) (b60.fd8): C++ EH exception - code e06d7363 (first chance) Nothing was changed for about 15 minutes. WinDbg stated *BUSY* Debugger is running. I couldn't see in your instructions what should I do, so I selected Debug -> Break. If I got it correctly, WinDbg only the following new lines added, (b60.4d0): Break instruction exception - code 80000003 (first chance) eax=7ffd9000 ebx=00000001 ecx=00000002 edx=00000003 esi=00000004 edi=00000005 eip=7c90120e esp=0724ffcc ebp=0724fff4 iopl=0 nv up ei pl zr na pe nc cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246 ntdll!DbgBreakPoint: 7c90120e cc int 3 Now LibreOffice Window was hidden by WinDbg and the browser windows, and I couldn't switch to it. So I again let it Debug -> Go. Other then a single 0:010> g line, I saw nothing new in WinDbg window. At that point I decided to kill LibreOffice. In the task manager there was a single, Not Responding, LibreOffice application. In the Processes list of the task manager, I saw one soffice.bin. I choose to END Process it. Was I to choose End Process Tree? As a consequence, WinDbg got the following lines added: eax=00000000 ebx=0000006b ecx=7ffd7000 edx=19d99c48 esi=01de8218 edi=00000144 eip=7c90e514 esp=16e1fd08 ebp=16e1fd40 iopl=0 nv up ei pl zr na pe nc cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246 ntdll!KiFastSystemCallRet: 7c90e514 c3 ret And the LibreOffice application was gone. Doesn't seem sensible to analyze, but what do I know? 0:011> !analyze -v Last event: b60.fd8: Exit process 0:b60, code 1 debugger time: Tue Mar 8 15:51:26.662 2016 (UTC + 0:00)
(In reply to ronvarburg from comment #15) > 1. I think you should have mentioned that WinDng will ask to save something > to the workspace after attaching to it. Does accepting the suggestion OK? > 2. Although you mentioned that WinDbg might be used when LibreOffice hang, > you didn't supply full instructions for that case. Parts mentioning workspace saving in the wiki article: Now press OK and choose File ▸ Save workspace to permanently set the symbols search path. As LibreOffice is still locked by WinDbg, you need to close WinDbg by pressing Alt+F4 or clicking File ▸ Exit. If a dialog appears asking to "Save information for workspace?", choose No. This will close both WinDbg and LibreOffice. Yep, I am not sure about hangs. You could try forcefully closing the soffice.bin from the Task manager (ctrl-alt-del). Perhaps that would allow Windbg to get a trace.
Replying to Comment #16: I was getting one more save suggestion besides those that are mentioned in the wiki. Referring to your reply, it was between these two: Now press OK and choose File ▸ Save workspace to permanently set the symbols search path. Here I got another one save something. As LibreOffice is still locked by WinDbg, you need to close WinDbg by pressing Alt+F4 or clicking File ▸ Exit. If a dialog appears asking to "Save information for workspace?", choose No. This will close both WinDbg and LibreOffice. I tried now and I didn't get it. Next time I'll try forcefully closing the soffice.bin from the Task manager (ctrl-alt-del), without the Debug->Break I used this time.
https://support.microsoft.com/en-us/kb/241215 discusses the Userdump.exe tool. The page explicitly mentions dump file of a hang process. Can you comment? I didn't install it, don't know if it supports old cpus, not sure if XP SP3 is supported, and so on. In general I would like detailed instructions, like what you have for <a href="https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg">WinDbg</a>. Will analyzing a forcefully closed soffice.bin from the Task manager (ctrl-alt-del) by WinDbg, likely to give meaningful results?
(In reply to ronvarburg from comment #18) > https://support.microsoft.com/en-us/kb/241215 discusses the Userdump.exe > tool. The page explicitly mentions dump file of a hang process. > Can you comment? > I didn't install it, don't know if it supports old cpus, not sure if XP SP3 > is supported, and so on. In general I would like detailed instructions, like > what you have for <a > href="https://wiki.documentfoundation.org/ > How_to_get_a_backtrace_with_WinDbg">WinDbg</a>. > > Will analyzing a forcefully closed soffice.bin from the Task manager > (ctrl-alt-del) by WinDbg, likely to give meaningful results? I finally got the word from devs that forceful closing a hanging LibreOffice on Windows will not help in getting a trace. Such a procedure only works on OS X it seems. I have no experience with Userdump.exe Do you have a plan to move away from WinXP in the near future?
(In reply to Buovjaga from comment #19) I don't plan to move away from XP in the near future. Doesn't MS have a newer, similar, tool for their recent versions? Perhaps just a newer version of the same tool? Does LibreOffice suggest a solution for debugging hang processes on newer MS versions? I thought about it a bit. From the LibreOffice users point of view, such a tool might have some privacy issues.
(In reply to ronvarburg from comment #20) > (In reply to Buovjaga from comment #19) > I don't plan to move away from XP in the near future. > Doesn't MS have a newer, similar, tool for their recent versions? Perhaps > just a newer version of the same tool? Does LibreOffice suggest a solution > for debugging hang processes on newer MS versions? > I thought about it a bit. From the LibreOffice users point of view, such a > tool might have some privacy issues. I guess https://www.visualstudio.com/
(In reply to Buovjaga from comment #21) The way I understand https://msdn.microsoft.com/en-us/library/d5zhxt22%28VS.80%29.aspx, using VisualStudio for debugging the hang is not trivial, and requires a VisualStudio license. That page also mentions UserDump. and there is an alternatively. AD+. If I ubderstood the page correctly, a dump produced by UserDump can be analyzed by VisualStudio. I wonder if that is correct for any VisualStudio, or only one that is installed on the machine where the dump was produced. If developers will be able to analyze a dump produced here, can you provide instructions for installing and using UserDump, or AD+. like those you supply for WinDbg?
(In reply to ronvarburg from comment #22) > (In reply to Buovjaga from comment #21) > The way I understand > https://msdn.microsoft.com/en-us/library/d5zhxt22%28VS.80%29.aspx, using > VisualStudio for debugging the hang is not trivial, and requires a > VisualStudio license. That page also mentions UserDump. and there is an > alternatively. AD+. > If I ubderstood the page correctly, a dump produced by UserDump can be > analyzed by VisualStudio. I wonder if that is correct for any VisualStudio, > or only one that is installed on the machine where the dump was produced. > If developers will be able to analyze a dump produced here, can you provide > instructions for installing and using UserDump, or AD+. like those you > supply for WinDbg? Visual Studio community edition is free. I am not qualified to provide the instructions.
(In reply to Buovjaga from comment #23) Although Visual Studio community edition is free, I am not sure it is capable of analyzing the dump. Can you ask the developers: 1. Will they be able to analyze a dump created by UserDump or AD+ on a user machine? 2. Can someone qualified provide the instructions?
I just took a look at the WinDbg help (from the Help menu). You could try !analyze -hang instead of -v.
(In reply to Buovjaga from comment #25) > I just took a look at the WinDbg help (from the Help menu). You could try > !analyze -hang instead of -v. It seems this is better: !analyze -v -hang
In reply to Buovjaga from comment #21: I am confused. Didn't you wrote on comment #18 that forceful closing a hanging LibreOffice on Windows will not help in getting a trace ? Looking back at my comment #15, Are you saying that I should try Debug->Break, and then !analyze -v -hang ? Perhaps you meant to skip the Debug->Go step, and jump right ahead to !analyze -v -hang ?
Fixing myself on comment #27: My previous comment is a replay to Buovjaga from comment #26.
(In reply to ronvarburg from comment #27) > In reply to Buovjaga from comment #21: > I am confused. Didn't you wrote on comment #18 that > > forceful closing a hanging LibreOffice on Windows will not help in getting a > trace > > ? > > Looking back at my comment #15, Are you saying that I should try > Debug->Break, and then !analyze -v -hang ? Perhaps you meant to skip the > Debug->Go step, and jump right ahead to !analyze -v -hang ? Yep, sorry, this is all new to me. Start debug normally, then debug - break when it hangs. Then !analyze -v -hang
In reply to Buovjaga from comment #29: I have the following WinDbg problem. I removed WinDbg, and related packages, from the PC. And installed them again. I can see in the control panel that * Microsoft .Net Framework 4 Client Profile * Microsoft .Net Framework 4 Extended * Microsoft Windows SDK for Windows 7 (7.1) are installed. But I can not see a shortcut to WinDbg. Trying check/repair Microsoft Windows SDK for Windows 7 (7.1) doesn't help. 6:20:47 PM Wednesday, March 16, 2016: [SDKSetup:Info] Config_Products_DetermineProductState_Begin: Product: Windows Debugging Tools 6:20:47 PM Wednesday, March 16, 2016: [SDKSetup:Info] Config_Products_DetermineProductState: Product: Windows Debugging Tools; Installed: Unknown; 6:20:47 PM Wednesday, March 16, 2016: [SDKSetup:Info] Windows Installer reported no registered source locations for the WinSDKDebuggingToolsproduct. 6:20:47 PM Wednesday, March 16, 2016: [SDKSetup:Info] Config_Products_DetermineProductState_End: Product: Windows Debugging Tools 6:20:47 PM Wednesday, March 16, 2016: [SDKSetup:Info] Config_Products_Install: Windows SDK Setup (skipping)
Please ignore my, ronvarburg, comment #30. I checked the wrong box when installing the SDK. Took me a while to spot it. I now have WinDbg as expected.
I upgraded LibreOffive in the mean while. Currently with Version: 5.1.1.3 Build ID: 89f508ef3ecebd2cfb8e1def0f0ba9a803b88a6d CPU Threads: 1; OS Version: Windows 5.1; UI Render: default; Locale: en-US (en_US) Problem is still here. Another note is that I was trying to minimize LibreOffice, or asked it to appear over the browser, and other windows I used in the mean while. It didn't show itself, as it was hang. ******************************************************************************* * * * Exception Analysis * * * ******************************************************************************* *** ERROR: Symbol file could not be found. Defaulted to export symbols for D:\downloadedPrograms\portableapps\libreoffice\App\libreoffice\program\soffice.bin - GetPageUrlData failed, server returned HTTP status 404 URL requested: http://watson.microsoft.com/StageOne/soffice_bin/5_1_1_3/ntdll_dll/5_1_2600_6055/0000120e.htm?Retriage=1 FAULTING_IP: ntdll!DbgBreakPoint+0 7c90120e cc int 3 EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff) ExceptionAddress: 7c90120e (ntdll!DbgBreakPoint) ExceptionCode: 80000003 (Break instruction exception) ExceptionFlags: 00000000 NumberParameters: 3 Parameter[0]: 00000000 Parameter[1]: 00000002 Parameter[2]: 00000003 FAULTING_THREAD: 0000000c BUGCHECK_STR: HANG PROCESS_NAME: soffice.bin ERROR_CODE: (NTSTATUS) 0xcfffffff - <Unable to get error code text> EXCEPTION_CODE: (NTSTATUS) 0xcfffffff - <Unable to get error code text> EXCEPTION_PARAMETER1: 00000000 EXCEPTION_PARAMETER2: 00000002 EXCEPTION_PARAMETER3: 00000003 MOD_LIST: <ANALYSIS/> NTGLOBALFLAG: 0 APPLICATION_VERIFIER_FLAGS: 0 DERIVED_WAIT_CHAIN: Dl Eid Cid WaitType -- --- ------- -------------------------- 13 ac.fe8 Speculated (Triage) --> 0 ac.f3c Critical Section --> 12 ac.ae4 SendMessage WAIT_CHAIN_COMMAND: ~13s;k;;~0s;k;;~12s;k;; BLOCKING_THREAD: 00000ae4 DEFAULT_BUCKET_ID: APPLICATION_HANG_BlockedIn_SendMessage PRIMARY_PROBLEM_CLASS: APPLICATION_HANG_BlockedIn_SendMessage PRIMARY_PROBLEM_CLASS_DATA: HWND: 0xdaec18 LAST_CONTROL_TRANSFER: from 7e4194be to 7c90e514 STACK_TEXT: 15e4fd04 7e4194be 7e42c174 00350384 00000144 ntdll!KiFastSystemCallRet 15e4fd40 7e4292e3 00daec18 00000144 00000000 USER32!NtUserMessageCall+0xc 15e4fd60 0c57c91c 00350384 00000144 00000000 USER32!SendMessageW+0x7f 15e4fd80 0c566e2c 00350384 15e4fe7c 15e4fdc0 fps!ListboxDeleteItems+0x1c [c:\cygwin64\home\buildslave\source\libo-core\fpicker\source\win32\misc\winimplhelper.cxx @ 234] 15e4fdb0 0c564b0e 086a18d8 0000006b 00000000 fps!CExecuteFilePickerState::setValue+0xac [c:\cygwin64\home\buildslave\source\libo-core\fpicker\source\win32\filepicker\filepickerstate.cxx @ 405] 15e4fde4 10c60290 0c4741d0 0000006b 00000004 fps!CFilePicker::setValue+0x4e [c:\cygwin64\home\buildslave\source\libo-core\fpicker\source\win32\filepicker\filepicker.cxx @ 455] 15e4fec0 10c5be1d e4362b51 0c7d67b4 000b0008 mergedlo!sfx2::FileDialogHelper_Impl::updateVersions+0x2e0 [c:\cygwin64\home\buildslave\source\libo-core\sfx2\source\dialog\filedlghelper.cxx @ 642] 15e4fee0 0c5652e4 0c7d67b4 04785100 6176e161 mergedlo!sfx2::FileDialogHelper_Impl::fileSelectionChanged+0x4d [c:\cygwin64\home\buildslave\source\libo-core\sfx2\source\dialog\filedlghelper.cxx @ 161] 15e4ff08 0c557bf4 047850f8 0c7d67b4 6176e109 fps!CFilePickerParamEventNotification::notifyEventListener+0x74 [c:\cygwin64\home\buildslave\source\libo-core\fpicker\source\win32\filepicker\filepickereventnotification.cxx @ 73] 15e4ff60 0c555e46 0c4741dc 0c58c874 15e4ffa8 fps!CAsyncEventNotifier::run+0x164 [c:\cygwin64\home\buildslave\source\libo-core\fpicker\source\win32\filepicker\asynceventnotifier.cxx @ 277] 15e4ff70 0102c01d 0c4741dc e76108e3 07a3b810 fps!CAsyncEventNotifier::ThreadProc+0x16 [c:\cygwin64\home\buildslave\source\libo-core\fpicker\source\win32\filepicker\asynceventnotifier.cxx @ 306] 15e4ffa8 0102c001 00000001 15e4ffec 7c80b729 MSVCR120!_callthreadstartex+0x1b [f:\dd\vctools\crt\crtw32\startup\threadex.c @ 376] 15e4ffb4 7c80b729 085cbe40 07a3b810 00000001 MSVCR120!_threadstartex+0x7c [f:\dd\vctools\crt\crtw32\startup\threadex.c @ 354] 15e4ffec 00000000 0102bfb4 085cbe40 00000000 kernel32!BaseThreadStart+0x37 FOLLOWUP_IP: fps!ListboxDeleteItems+1c [c:\cygwin64\home\buildslave\source\libo-core\fpicker\source\win32\misc\winimplhelper.cxx @ 234] 0c57c91c 83f8ff cmp eax,0FFFFFFFFh SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: fps!ListboxDeleteItems+1c FOLLOWUP_NAME: MachineOwner MODULE_NAME: fps IMAGE_NAME: fps.dll DEBUG_FLR_IMAGE_TIMESTAMP: 56d5cb8b STACK_COMMAND: ~12s ; kb BUCKET_ID: HANG_fps!ListboxDeleteItems+1c FAILURE_BUCKET_ID: APPLICATION_HANG_BlockedIn_SendMessage_cfffffff_fps.dll!ListboxDeleteItems WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/soffice_bin/5_1_1_3/56d5cb71/ntdll_dll/5_1_2600_6055/4d00f27d/cfffffff/0000120e.htm?Retriage=1 Followup: MachineOwner ---------
Another one, looks to me like the one from comment #32: 0:010> !analyze -v -hang ******************************************************************************* * * * Exception Analysis * * * ******************************************************************************* *** ERROR: Symbol file could not be found. Defaulted to export symbols for D:\downloadedPrograms\portableapps\libreoffice\App\libreoffice\program\soffice.bin - GetPageUrlData failed, server returned HTTP status 404 URL requested: http://watson.microsoft.com/StageOne/soffice_bin/5_1_1_3/ntdll_dll/5_1_2600_6055/0000120e.htm?Retriage=1 FAULTING_IP: ntdll!DbgBreakPoint+0 7c90120e cc int 3 EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff) ExceptionAddress: 7c90120e (ntdll!DbgBreakPoint) ExceptionCode: 80000003 (Break instruction exception) ExceptionFlags: 00000000 NumberParameters: 3 Parameter[0]: 00000000 Parameter[1]: 00000002 Parameter[2]: 00000003 FAULTING_THREAD: 0000000c BUGCHECK_STR: HANG PROCESS_NAME: soffice.bin ERROR_CODE: (NTSTATUS) 0xcfffffff - <Unable to get error code text> EXCEPTION_CODE: (NTSTATUS) 0xcfffffff - <Unable to get error code text> EXCEPTION_PARAMETER1: 00000000 EXCEPTION_PARAMETER2: 00000002 EXCEPTION_PARAMETER3: 00000003 MOD_LIST: <ANALYSIS/> NTGLOBALFLAG: 0 APPLICATION_VERIFIER_FLAGS: 0 DERIVED_WAIT_CHAIN: Dl Eid Cid WaitType -- --- ------- -------------------------- 10 b74.de8 Speculated (Triage) --> 0 b74.1e4 Critical Section --> 12 b74.dcc SendMessage WAIT_CHAIN_COMMAND: ~10s;k;;~0s;k;;~12s;k;; BLOCKING_THREAD: 00000dcc DEFAULT_BUCKET_ID: APPLICATION_HANG_BlockedIn_SendMessage PRIMARY_PROBLEM_CLASS: APPLICATION_HANG_BlockedIn_SendMessage PRIMARY_PROBLEM_CLASS_DATA: HWND: 0xdfc868 LAST_CONTROL_TRANSFER: from 7e4194be to 7c90e514 STACK_TEXT: 14b2fd04 7e4194be 7e42c174 007e035c 00000144 ntdll!KiFastSystemCallRet 14b2fd40 7e4292e3 00dfc868 00000144 00000000 USER32!NtUserMessageCall+0xc 14b2fd60 06f6c91c 007e035c 00000144 00000000 USER32!SendMessageW+0x7f 14b2fd80 06f56e2c 007e035c 14b2fe7c 14b2fdc0 fps!ListboxDeleteItems+0x1c [c:\cygwin64\home\buildslave\source\libo-core\fpicker\source\win32\misc\winimplhelper.cxx @ 234] 14b2fdb0 06f54b0e 04a43018 0000006b 00000000 fps!CExecuteFilePickerState::setValue+0xac [c:\cygwin64\home\buildslave\source\libo-core\fpicker\source\win32\filepicker\filepickerstate.cxx @ 405] 14b2fde4 10c60290 0730cc50 0000006b 00000004 fps!CFilePicker::setValue+0x4e [c:\cygwin64\home\buildslave\source\libo-core\fpicker\source\win32\filepicker\filepicker.cxx @ 455] 14b2fec0 10c5be1d 80ae95b3 08f0f01c 000afd98 mergedlo!sfx2::FileDialogHelper_Impl::updateVersions+0x2e0 [c:\cygwin64\home\buildslave\source\libo-core\sfx2\source\dialog\filedlghelper.cxx @ 642] 14b2fee0 06f552e4 08f0f01c 04b93f18 fc7b2d17 mergedlo!sfx2::FileDialogHelper_Impl::fileSelectionChanged+0x4d [c:\cygwin64\home\buildslave\source\libo-core\sfx2\source\dialog\filedlghelper.cxx @ 161] 14b2ff08 06f47bf4 04b93f10 08f0f01c fc7b2d7f fps!CFilePickerParamEventNotification::notifyEventListener+0x74 [c:\cygwin64\home\buildslave\source\libo-core\fpicker\source\win32\filepicker\filepickereventnotification.cxx @ 73] 14b2ff60 06f45e46 0730cc5c 06f7c874 14b2ffa8 fps!CAsyncEventNotifier::run+0x164 [c:\cygwin64\home\buildslave\source\libo-core\fpicker\source\win32\filepicker\asynceventnotifier.cxx @ 277] 14b2ff70 0102c01d 0730cc5c 80f26e64 ffffffff fps!CAsyncEventNotifier::ThreadProc+0x16 [c:\cygwin64\home\buildslave\source\libo-core\fpicker\source\win32\filepicker\asynceventnotifier.cxx @ 306] 14b2ffa8 0102c001 00e3f3fc 14b2ffec 7c80b729 MSVCR120!_callthreadstartex+0x1b [f:\dd\vctools\crt\crtw32\startup\threadex.c @ 376] 14b2ffb4 7c80b729 04ba4a60 ffffffff 00e3f3fc MSVCR120!_threadstartex+0x7c [f:\dd\vctools\crt\crtw32\startup\threadex.c @ 354] 14b2ffec 00000000 0102bfb4 04ba4a60 00000000 kernel32!BaseThreadStart+0x37 FOLLOWUP_IP: fps!ListboxDeleteItems+1c [c:\cygwin64\home\buildslave\source\libo-core\fpicker\source\win32\misc\winimplhelper.cxx @ 234] 06f6c91c 83f8ff cmp eax,0FFFFFFFFh SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: fps!ListboxDeleteItems+1c FOLLOWUP_NAME: MachineOwner MODULE_NAME: fps IMAGE_NAME: fps.dll DEBUG_FLR_IMAGE_TIMESTAMP: 56d5cb8b STACK_COMMAND: ~12s ; kb BUCKET_ID: HANG_fps!ListboxDeleteItems+1c FAILURE_BUCKET_ID: APPLICATION_HANG_BlockedIn_SendMessage_cfffffff_fps.dll!ListboxDeleteItems WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/soffice_bin/5_1_1_3/56d5cb71/ntdll_dll/5_1_2600_6055/4d00f27d/cfffffff/0000120e.htm?Retriage=1 Followup: MachineOwner ---------
Thanks. In the future, though, please attach the backtraces as text files and don't paste them in a comment.
Should I attach future backtraces to this bug when I am not observing some change in the behavior? Perhaps I should attach a backtrace whenever I upgrade to a newer version, even though I am not observing some change in the behavior?
(In reply to ronvarburg from comment #35) > Should I attach future backtraces to this bug when I am not observing some > change in the behavior? Perhaps I should attach a backtrace whenever I > upgrade to a newer version, even though I am not observing some change in > the behavior? One backtrace per same crash is enough, so no need to continue attaching to this report.
I wonder: I have a document that includes this animated GIF, and Writer hangs often while displaying the document: http://forums.x-plane.org/uploads/monthly_2016_07/GPS24golden.gif.5d39c488452fdbfe7ac47db70df3cbc8.gif Is this the same bug?
(In reply to Ulrich Windl from comment #37) > I wonder: I have a document that includes this animated GIF, and Writer > hangs often while displaying the document: > http://forums.x-plane.org/uploads/monthly_2016_07/GPS24golden.gif. > 5d39c488452fdbfe7ac47db70df3cbc8.gif > Is this the same bug? I created a separate report about the gif animation: bug 104582
Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20180502
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20180530