[Octave-bug-tracker] [bug #49109] child process started by fork crashes or hangs with octave-gui

[Mike Miller]

Update of bug #49109 (project octave):

                  Status:               Confirmed => Wont Fix               
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #4:

I'm closing this bug as won't fix.

I've recently learned that it's a well known problem that "fork without exec"
does not work with large libraries and frameworks linked with a program,
including Python, Qt, probably Java. In fact, it's considered deprecated on
macOS now to 'fork' a process and not 'exec' a brand new executable image.

If the attached reproducer is changed to 'exec' a new program instead of
executing Octave code or calling 'exit', it works perfectly even in
octave-gui.

Calling 'fork' by itself for creating worker child processes should only be
used carefully in small programs that don't link with large frameworks.

References:

* http://www.evanjones.ca/fork-is-dangerous.html
* https://bugs.python.org/issue33725

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?49109>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/