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
If you execute a command that does a fork at Pharo level, and the process runs forever unless explicitly terminated (like tail) AND you don't terminate AND you quite the image, then the next time you start the image, the process will continue trying to do the waitForExit which does the queryExitStatus, which does the waitpid, which of course throws error because the process at the OS level does not exist anymore. Then, the StartupUIManager kills the VM if there is an error at startup.
If you execute a command that does a
fork
at Pharo level, and the process runs forever unless explicitly terminated (liketail
) AND you don't terminate AND you quite the image, then the next time you start the image, the process will continue trying to do thewaitForExit
which does thequeryExitStatus
, which does thewaitpid
, which of course throws error because the process at the OS level does not exist anymore. Then, the StartupUIManager kills the VM if there is an error at startup.An example of the process code is this:
And the VM crash looks as this (built a VM for debug and put a breakpoint in
_exit
):The text was updated successfully, but these errors were encountered: