|
From: | Mike Miller |
Subject: | [Octave-bug-tracker] [bug #37877] unable to initialize java VM more than once per Octave session |
Date: | Fri, 07 Dec 2012 01:42:44 +0000 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.95 Safari/537.11 |
URL: <http://savannah.gnu.org/bugs/?37877> Summary: unable to initialize java VM more than once per Octave session Project: GNU Octave Submitted by: mtmiller Submitted on: Thu 06 Dec 2012 08:42:43 PM EST Category: Libraries Severity: 3 - Normal Priority: 5 - Normal Item Group: None Status: None Assigned to: None Originator Name: Originator Email: Open/Closed: Open Discussion Lock: Any Release: dev Operating System: GNU/Linux _______________________________________________________ Details: I have no idea what the correct or expected behavior is in this situation, but since these are user-callable functions they should not be allowed to put Octave in this state. Calling java_init and java_exit more than once apparently put the Java infrastructure into a confused state: octave:1> java_init; octave:2> java_exit; octave:3> java_init; error: unable to start Java VM in /usr/lib/jvm/default-java/jre/lib/amd64/server/libjvm.so octave:3> java_exit; octave:4> java_init; At this point the interpreter hangs and I have to Ctrl-C to kill it. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?37877> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |