[Octave-bug-tracker] [bug #58641] Java crashes (OutOfMemoryError/StackOverflowError) when invoking a child process

[Markus Mützel]

Update of bug #58641 (project octave):

                  Status:             In Progress => Need Info              
                 Release:                   5.2.0 => 6.0.90                 

    _______________________________________________________

Follow-up Comment #12:

I'm not sure what changed. But I'm no longer able to reproduce the original
error.

With the attached patch, the workaround is used if the test from comment #7
fails (i.e. for all glibc versions for now).
With it, Octave should no longer crash or block for the initial test.

We already use $OCTAVE_JAVA_DIR/java.opts to pass user arguments to the JVM
(with a fallback to OCTAVE_FCNFILEDIR/java/java.opts if $OCTAVE_JAVA_DIR isn't
set).

Can someone who can still reproduce the crash please test if the attached
patch solves the issue? (Run bootstrap, configure and make with the usual
parameters)
If it does, does it crash again after executing the following and restarting
Octave:

system('echo -Djdk.lang.processReaperUseDefaultStackSize=false >
$OCTAVE_JAVA_DIR/java.opts')



The patch also activates debug messages for Java. A final patch should not do
that.

    _______________________________________________________

Reply to this item at:

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

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