<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - SalUserEventList::isFrameAlive hang after crash" href="https://bugs.documentfoundation.org/show_bug.cgi?id=133770#c25">Comment # 25</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - SalUserEventList::isFrameAlive hang after crash" href="https://bugs.documentfoundation.org/show_bug.cgi?id=133770">bug 133770</a> from <a class="email" href="mailto:glogow@fbihome.de" title="Jan-Marek Glogowski <glogow@fbihome.de>"> Jan-Marek Glogowski</a> <pre>(In reply to Telesto from <a href="show_bug.cgi?id=133770#c24">comment #24</a>) > @Jan-Marek.. > The deadlock situation you're working on: Unlock scheduler in deinit for > ProcessEventsToIdle bring this bug (with duplicates) (and more distant bug > 135073 <a class="bz_bug_link bz_status_NEW " title="NEW - Document File Recovery freeze/hang after crash" href="show_bug.cgi?id=131681">bug 131681</a>) That Scheduler code Mike and I are working on is there for years: commit fd0fff67798fea87217e65bb1561aa0d0e741c51 Author: Jan-Marek Glogowski <<a href="mailto:glogow@fbihome.de">glogow@fbihome.de</a>> Date: Fri Jul 28 17:13:20 2017 +0200 Assert active Tasks on scheduler de-init This ProcessEventsToIdle() is just enabled for a debug build, as this is just some debug facility to verify the active static Tasks list. Normally - at the point of Scheduler::ImplDeInitScheduler - no more Tasks will be processed, but the list of pending Tasks can be quite long (which may be a problem in itself). > For me lingering soffice.bin after crash only occurs on second and following > crashes.. > > 1. open a bug doc able to crash LibO > 2. Let it crash -> file recovery dialog and such appears (everything OK) > 3. Make it crash again with same bug doc > 4. Now we see a lingering soffice.bin at 25% CPU. This whole bug report doesn't make sense. If LO really crashes, the process will be gone, so there is no way to "hang" in SalUserEventList::isFrameAlive. Maybe the LO process is not crashed but somehow deadlocked to begin with? No idea, how the watchdog is handling this.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>