[Libreoffice-bugs] [Bug 133770] SalUserEventList::isFrameAlive hang after crash
bugzilla-daemon at bugs.documentfoundation.org
bugzilla-daemon at bugs.documentfoundation.org
Mon Dec 7 13:03:11 UTC 2020
https://bugs.documentfoundation.org/show_bug.cgi?id=133770
--- Comment #27 from Jan-Marek Glogowski <glogow at fbihome.de> ---
I just checked desktop/win32/source/loader.cxx, the LO watchdog process. It
only does a loop of MsgWaitForMultipleObjects(1, &aProcessInfo.hProcess, ...)
and then calls GetExitCodeProcess. I guess the loop won't terminate, while the
process is running and then we check the exit code to handle some LO specific
exit codes for uncaught exceptions or a normal restart.
Interestingly we don't check the return value from GetExitCodeProcess, so won't
detect a case of STILL_ACTIVE. Maybe our watchdog is buggy?
Can you check the pid to verify, if it's really the old process or a new one
and it's actually a startup problem?
Not that I yet tried to reproduce this. Just some curiosity.
----------
(In reply to Telesto from comment #26)
...
> LibreOffice crashed storing recovery information now..
If a process has really crashed, you have no way to "storing recovery
information". These are just saved in some interval, while everything is still
ok. Maybe LO does some additional stuff for the "uncaught exception" case, but
in any case the process state will be compromised, so no way to store anything
useful (except for the process backtrace, if possible, but that's just a bonus
for developers).
P.S. I guess STR = Steps to Reproduce.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20201207/0a7794f3/attachment.htm>
More information about the Libreoffice-bugs
mailing list