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

[anonymous]

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

Is there a way to unload Java ?
...
Actually, I need only 'expfit', so I can just use the .m file. But OTOH I
might need other packages - like 'signal', so can it be that Java will still
be pulled in ?
...
Many thanks for confirming the bug.

[comment #15 comment #15:]
> I can reproduce this in a Ubuntu 18.04 virtual machine with the stock
installed Octave 4.2.2 and the optim package installed from Forge.
> 
> The segmentation fault appears to arise only when the Java runtime is loaded
into Octave.
> 
> This works just fine:
> 
> 
> addpath ~/octave/optim-1.6.1
> expfit (512, 0, 1, rand (1, 1024))
> 
> 
> But this is enough to reproduce the segmentation fault:
> 
> 
> addpath ~/octave/optim-1.6.1
> version -java
> expfit (512, 0, 1, rand (1, 1024))
> 
> 
> IIRC there have been problems reported before about memory problems when
Java has been loaded.

    _______________________________________________________

Reply to this item at:

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

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