|
| From: | Markus Mützel |
| Subject: | [Octave-bug-tracker] [bug #58641] Java crashes (OutOfMemoryError/StackOverflowError) when invoking a child process |
| Date: | Fri, 26 Jun 2020 03:14:41 -0400 (EDT) |
| User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.106 Safari/537.36 Edg/83.0.478.54 |
Follow-up Comment #11, bug #58641 (project octave):
If I understood correctly, setting that JVM options only takes any effect if
the JVM spawns new threads. If that option is not set on system with the buggy
glibc, the JVM (and with it Octave) will crash.
So I'm not sure, we need an option to change JVM start parameters to fix this
bug here. But I agree that such an option could be useful.
What about fixing this error (with the hard coded option on affected systems)
on stable?
We could add the interface that you are proposing on default afterwards.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?58641>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
| [Prev in Thread] | Current Thread | [Next in Thread] |