[Libreoffice-bugs] [Bug 99623] Copy-paste freezes LibreOffice when CLCL is running

bugzilla-daemon at bugs.documentfoundation.org bugzilla-daemon at bugs.documentfoundation.org
Fri Jul 21 10:03:16 UTC 2017


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

Timur <gtimur at gmail.com> changed:

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

--- Comment #5 from Timur <gtimur at gmail.com> ---
This bug may stay open but I'm afraid it's of no use since Buovjaga didn't
reproduce and that os not widely used. 
So I set back to Needinfo for submitter to add some reproducible steps or new
info. 

If you don't get Crash Report, and sometimes there's no in Windows -  I guess
you'd mentioned it if it were - you may use procdump (part of free and useful
Sysinternaly Suite) during LO run in order to get a dump (soffice.bin.dmp).
How: 
- 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).

You may upload that crash dump or do it yourself:
- 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/20170721/408d5e89/attachment-0001.html>


More information about the Libreoffice-bugs mailing list