<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 - Copy-paste freezes LibreOffice when CLCL is running"
   href="https://bugs.documentfoundation.org/show_bug.cgi?id=99623">bug 99623</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 - Copy-paste freezes LibreOffice when CLCL is running"
   href="https://bugs.documentfoundation.org/show_bug.cgi?id=99623#c5">Comment # 5</a>
              on <a class="bz_bug_link 
          bz_status_NEEDINFO "
   title="NEEDINFO - Copy-paste freezes LibreOffice when CLCL is running"
   href="https://bugs.documentfoundation.org/show_bug.cgi?id=99623">bug 99623</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>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 <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).

You may upload that crash dump or do it yourself:
- 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>