<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#c26">Comment # 26</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:telesto@surfxs.nl" title="Telesto <telesto@surfxs.nl>"> Telesto</a> <pre>(In reply to Jan-Marek Glogowski from <a href="show_bug.cgi?id=133770#c25">comment #25</a>) > 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. First of, I misconceived where working on. Clearly a different topic. Me thinking I know something about the topic, while not knowing anything at all :P Mea culpa ---About topic here The issue is more me lacking the adequate terminology/vocabulary. Take a STR which normally would crash/terminate LibreOffice. Directly without 'grace' or with intermediary dialog show up, LibreOffice crashed storing recovery information now.. Pressing OK should finally kill/terminate soffice.bin process. However In my case the 'termination' doesn't kick in. It works for the first round using known crasher, but second 'crash' gets stuck). So you get LibreOffice crashed storing recovery information dialog. You process OK. LibreOffice is gone from screen, Except the process still lingering in task manager (soffice.bin). Launching LibreOffice again, while soffice.bin still active in the background causes a bootloop. Splash screen, splash screen etc. until the older soffice.bin process lingering in the task manager is terminated manually. Looking inside the lingering process with VerySleepy shows process SalUserEventList::isFrameAlive looping/running (25% CPU usage). Not that they tool is reliable for proper/clean stacks. But looks like for searching for a 'frame' which killed Which I somehow connect with <a class="bz_bug_link bz_status_VERIFIED bz_closed" title="VERIFIED FIXED - LibreOffice exits/crashes when minimizing start center after closing a document (SKIA)" href="show_bug.cgi?id=138022">https://bugs.documentfoundation.org/show_bug.cgi?id=138022</a> (as it start somewhere with Skia implementation). But that's a n00b assessment not to be taken seriously :P Or a deadlock issue or something like that. But as stated at the beginning.. I think I know something but probably know squad.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>