[Top][All Lists]

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

[Octave-bug-tracker] [bug #52666] Segfault when closing a figure inside

From: Rik
Subject: [Octave-bug-tracker] [bug #52666] Segfault when closing a figure inside a "deletefcn" callback
Date: Thu, 14 Dec 2017 17:52:51 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0

Follow-up Comment #3, bug #52666 (project octave):

I don't get a segfault, but Octave does hang and uses 100% of the CPU until

The deletefcn() is called prior to actually destroying the object so that the
callback can inspect any properties of the object it needs before allowing the
destruction to occur.

Calling close, or delete, on the parent figure will cause the graphics system
to recursively attempt to delete each child handle of the figure which will
eventually call delete() again on this handle.  It make be that, for me, the
object is locked because the deletefcn() is executing and thus the system


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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