[Octave-bug-tracker] [bug #60620] [octave forge] (optim) 'expfit' function from optim-1.6.1 package terminates with segmentation fault

[Mike Miller]

Follow-up Comment #18, bug #60620 (project octave):

Unfortunately, I don't think there is a way to unload Java from a running
Octave instance once it's loaded.

There are numerous workarounds if you are not actually interested in any of
the Java functions provided by the io package (which is an indirect dependency
of the optim package).

One, you could fully uninstall the io package if you don't need it, and
install the optim and statistics packages with the '-nodeps' option. However,
I can't say for sure which particular functions may not work because of some
missing io package function.

Another option, if you don't use Java at all on your system, is to apt remove
all openjdk* packages. The Ubuntu repository version of Octave will still
install without them, they are pulled in only as a Recommends dependency.

And as far as fixing the underlying bug, I'm sorry that I don't know or
remember any further details about Java, I try to forget most things about
Java. I think there may have been some problem with the way Java allocates
stack space for dozens of background threads when the JVM starts up, and maybe
there was a bug in some version of Java, or maybe some configuration change
was made in later version of Java or Octave to limit that?

    _______________________________________________________

Reply to this item at:

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

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