[Octave-bug-tracker] [bug #61994] Crash on GUI exiting with octave_base_value objects still open.

[John W. Eaton]

Follow-up Comment #20, bug #61994 (project octave):

I know it is tedious to try to get stack traces in cases like this, but it
would be more useful to have the output of "thread apply all where" to see
which threads still exist and what they are doing at the point of the crash. 
If we can get that info it would be great, but the output you have in comment
#19 already seems to confirm what I was thinking.

At this point, it appears that the GUI thread is executing the function that
was queued to clear the workspace model/viewer and the crash is happening when
it deletes the octave_value objects stored there.  My assumption was that it
wouldn't matter whether the last reference to an octave_value object was
deleted in the interpreter or GUI thread.  Either that assumption is wrong or
something else is happening to cause the "m_rep" pointer for this object to be
invalid at the point when the destructor is called in the GUI thread.

It would also be useful to confirm that the "m_rep" here pointed to the
audioplayer class object (I would assume so if that is the only thing that was
displayed in the workspace viewer prior to the crash).  It would also be
useful to know whether this kind of crash can happen with other types of class
objects of if it is something unique to the audioplayer object.

    _______________________________________________________

Reply to this item at:

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

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