[Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write]

[Adrian]

Follow-up Comment #48, bug #53733 (project octave):

So there is no crash but CPU hogging for the original code, right ? This is
one of the two behaviours I observe for octave outside gdb. Does it (the
original code, including graph.addNodes) also hog CPU when run under gdb ?

In your modified code you omit the method call

graph.addNodes(1:1000000);

which is the only problematic when running freely, and in gdb on systems where
one gets past the "javaaddpath('.')". Not sure therfore what your testing of
the imwrite timing is supposed to show: it's certainly not nice that imwrite
or zeros cause termination instead of some recoverable out of memory error,
but I have the impression it has nothing to do with the segfault that this
bug-report is about.


    _______________________________________________________

Reply to this item at:

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

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