|
| From: | Markus Mützel |
| Subject: | [Octave-bug-tracker] [bug #60620] octave-cli crashes when interacting with Java libraries |
| Date: | Tue, 18 May 2021 06:32:37 -0400 (EDT) |
| User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 Safari/537.36 Edg/90.0.818.62 |
Follow-up Comment #29, bug #60620 (project octave):
The bug that Mike referenced in comment #18 might be bug #58641.
I don't recall the details. But I think there was some issue with some Java
versions on some systems.
IIUC, the work-around that we implemented only applies if Octave starts its
own Java VM. We didn't change anything for that bug for the case where Octave
attaches to a Java VM that is already running.
I don't know much about Java and the JVM. Could it be that the CLI can connect
to an already running Java VM that the GUI cannot detect? Maybe that JVM was
started without the work-around.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?60620>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
| [Prev in Thread] | Current Thread | [Next in Thread] |