You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Exception message is sometimes not printed on Mac. In examples the default Python exception handler is overwritten with CEF Python's exception handler using this code:
sys.excepthook = cef.ExceptHook
This is required so that all CEF processes are shutdown on error. Otherwise in some cases zombie processes may be left running in background. Noticed this issue many years ago, but I don't remember which OS was that exactly. ExceptHook was to fix that, but whether using this handler is still required would need further testing using latest CEF. There have been many changes in upstream Chromium and maybe this ain't issue anymore?
Getting back to the core of the issue. It seems that calling cef.Shutdown() on Mac may prevent further execution of the Python code, because the code in ExceptHook looked like this:
Exception message is sometimes not printed on Mac. In examples the default Python exception handler is overwritten with CEF Python's exception handler using this code:
This is required so that all CEF processes are shutdown on error. Otherwise in some cases zombie processes may be left running in background. Noticed this issue many years ago, but I don't remember which OS was that exactly. ExceptHook was to fix that, but whether using this handler is still required would need further testing using latest CEF. There have been many changes in upstream Chromium and maybe this ain't issue anymore?
Getting back to the core of the issue. It seems that calling cef.Shutdown() on Mac may prevent further execution of the Python code, because the code in ExceptHook looked like this:
So the exception won't be printed if cef Shutdown procedure kills the process immediately which apparently occurs sometimes on Mac.
This issue was already fixed in master some time ago in commit 87123af . Creating this issue to track this bug.
The text was updated successfully, but these errors were encountered: