[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java metho

From: Adrian
Subject: [Octave-bug-tracker] [bug #53733] Panic/segfault when calling Java method after forge:im[read|write]
Date: Sat, 28 Apr 2018 17:15:13 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0

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


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:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]