https://bugs.documentfoundation.org/show_bug.cgi?id=108384
Timur <gti...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #7 from Timur <gti...@gmail.com> ---
This bug may stay open but I'm afraid it's of no use since there's no Crash
Report and it's not reproducible, so it can't be confirmed like this.
I'll mark as a duplicate of Bug 108368 for now. If it reproduced with more
info, please set back to Unconfirmed.
Kevin, please consider a large number of bugs and help even more when there's a
case like this, intermittent bug:
* what: 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)
and upload previous crash dump with LO "Master x86 39" or even 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.
*** This bug has been marked as a duplicate of bug 108368 ***
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
