[Libreoffice-bugs] [Bug 133770] SalUserEventList::isFrameAlive hang after crash

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=133770

--- Comment #28 from Telesto <telesto at surfxs.nl> ---
Created attachment 167918
  --> https://bugs.documentfoundation.org/attachment.cgi?id=167918&action=edit
Screenshot Document Recovery

(In reply to Jan-Marek Glogowski from comment #27)
> 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.

A) See screenshot What I mean with Document Recovery Windows with "graceful"
crash. Instead of abruptly terminating.. 

Off-topic Note: Still not seeing the whole point of that dialog (but really of
off topic)
* it manages to crash again while saving the recovery info in number of cases..
mostly if the crash is caused by rendering/layout flaw. Kind of hard to keep
showcases if this.. people tend to fix the layout flaws (so you never reach the
crash of the recovery dialog; so kind of masked). Also speculating this causing
lovely recovery issues... 

* it turns up in 40% of the cases or so (again depending on crasher). The other
60% it simply skips it: the lovely abrupt termination.. 

--
B) It's the old process not exiting.. (did check pid specifically, but I memory
usage 600 mb to different from new started process..

C) The screenshot is based on bug 138718 (which also illustrated the 'deadlock'
or whatever is happening). Or I'm I the only one encountering this on my
Windows 8.1 system? FWIW: as said the first time crash working properly..
failure when doing same thing again (so only the second and following runs).
After reboot everything is back to normal, until the second crash. It isn't my
user profile.. nor limited to specific LibO version.. 7.0 branch and up, I
think (but maybe even 6.4?)

-- 
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/16f99b36/attachment.htm>