[Libreoffice-bugs] [Bug 108005] Writer hangs several seconds after saving

bugzilla-daemon at bugs.documentfoundation.org bugzilla-daemon at bugs.documentfoundation.org
Tue May 23 11:51:06 UTC 2017


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

Timur <gtimur at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEEDINFO
     Ever confirmed|0                           |1

--- Comment #1 from Timur <gtimur at gmail.com> ---
Thank you, but this can't be conformed like this, even that I'm seeing some
unresponsability myself. 
You should either attach minimal test case to reproduce a bug or test this
yourself. 

I'm suggesting that you:
- get http://tdf.io/siguiexe to easily get and run "parallel" LO in Windows
(extract without installation)
- run different extracted versions (here it would be fresh 5.3.3.2 and 5.4 beta
and master 5.5+) and architectures (32-bit or 64-bit) related to this bug in
order to test crash
- note crash report link for crash with LO 5.2 and higher, sth. like
crashreport.libreoffice.org/stats/crash_details/.... (not applicable here but a
general advice)

and, if possible, since it's not overly complicated, but gives some clues:
- use procdump (part of free and useful Sysinternaly Suite) during LO run in
order to get a dump (soffice.bin.dmp)
- run procdump manually after LO start (path-to\SYSINTERNALSSUITE\procdump.exe
soffice.bin -h path-to\soffice.bin.dmp) for reproducible bugs like this one, OR
via simple batch file like attachment 129814, that is used instead of LO icon
to start LO, for intermittent bugs (which seems to be the case here)

and even this - or just upload previous crash dump with LO "Master x86 39":
- analyze dump with WinDbg configured per
https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg (set
"Symbol File Path")
- attach here as an attachment result of "!analyze -v" command in WinDbg
(that's "backtrace") 
- if "!analyze -v" is empty, which comes after "ntdll!NtTerminateProcess"
error, go with "kb" that prints stack trace and "~* kp" to dump the whole
stack.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20170523/04116061/attachment.html>


More information about the Libreoffice-bugs mailing list