<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:gtimur@gmail.com" title="Timur <gtimur@gmail.com>"> <span class="fn">Timur</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - Writer hangs several seconds after saving"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=108005">bug 108005</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>UNCONFIRMED
</td>
<td>NEEDINFO
</td>
</tr>
<tr>
<td style="text-align:right;">Ever confirmed</td>
<td>
</td>
<td>1
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - Writer hangs several seconds after saving"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=108005#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - Writer hangs several seconds after saving"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=108005">bug 108005</a>
from <span class="vcard"><a class="email" href="mailto:gtimur@gmail.com" title="Timur <gtimur@gmail.com>"> <span class="fn">Timur</span></a>
</span></b>
<pre>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 <a href="http://tdf.io/siguiexe">http://tdf.io/siguiexe</a> 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 <span class=""><a href="http://bugs.documentfoundation.org/attachment.cgi?id=129814" name="attach_129814" title="Batch to start LO with procdump">attachment 129814</a> <a href="http://bugs.documentfoundation.org/attachment.cgi?id=129814&action=edit" title="Batch to start LO with procdump">[details]</a></span>, 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
<a href="https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg">https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg</a> (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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>