Bug#961681: Bug #961681: octave 5.2.0 and java child processes

2020-07-13 Thread Sébastien Villemot
Control: tags -1 + upstream fixed-upstream Control: forwarded -1 https://savannah.gnu.org/bugs/?func=detailitem_id=58641 Dear Benjamin, Le vendredi 10 juillet 2020 à 19:15 +, Benjamin Moody a écrit : > This should now be fixed upstream: Thanks for taking care of investigating this bug and

Bug#961681: Bug #961681: octave 5.2.0 and java child processes

2020-07-10 Thread Benjamin Moody
This should now be fixed upstream: https://savannah.gnu.org/bugs/?func=detailitem_id=58641

Bug#961681: Bug #961681: octave 5.2.0 and java child processes

2020-06-19 Thread Benjamin Moody
> - Why does the stack overflow when the JVM is loaded from Octave, and > not when the JVM is launched "normally"? (What is that worker > thread doing that would cause it to use any appreciable amount of > stack space?) > > - Why, on bullseye, is it unable to create the worker thread in the

Bug#961681: Bug #961681: octave 5.2.0 and java child processes

2020-06-19 Thread Benjamin Moody
It seems that a possible workaround is to set the property "jdk.lang.processReaperUseDefaultStackSize" to "true". If that property is "true", then the worker thread uses the "default" stack size, whatever that is; if not, then the worker thread uses a stack size of 128 * 1024.

Bug#961681: Bug #961681: octave 5.2.0 and java child processes

2020-06-11 Thread Benjamin Moody
Control: found 961681 5.2.0-2 On bullseye, with octave 5.2.0-2 and openjdk-11-jre-headless 11.0.7+9-1, "b.start()" fails: $ octave -W -q -f octave:1> b = javaObject("java.lang.ProcessBuilder", {"/bin/true"}); OpenJDK 64-Bit Server VM warning: Archived non-system classes are disabled because the