[Octave-bug-tracker] [bug #47368] test of svds.m fails on Windows (Octave 4.0.1-rc3)

[Hartmut]

Follow-up Comment #7, bug #47368 (project octave):

@ Avinoam:
I have had a look at bug report #43505, and this looks very odd, indeed. Seems
that some Octave function calls are messed up, once Java stuff has been used
before. Rik thought this might be due to memory leaks in Octave.

Should we open a new bug report dedicated to this issue? The facts so far are
(at least):
* bug #43505 : After using java, the image saved by imwrite has all elements
lower by one value. 
* this bug (#47386): svds.m gives different results when java has been used
before (but I haven't tried to reproduce this yet).

If this points to memory leaks, it should be worth fixing. (My deepest hope
would even be to eventually find the root cause of image-i/o crashing Octave
on Windows during shutdown, bug #41699, still present in 4.0.1-rc3)

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?47368>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/