[Octave-bug-tracker] [bug #58814] Abort, core dump on exiting from graphics code

[John W. Eaton]

Follow-up Comment #5, bug #58814 (project octave):

Try looking at the full backtrace for all threads using


thread apply all bt


I suspect that the interpreter is in the process of exiting and cleaning up
the gh_manager object at the same time that the GUI thread is trying to use
graphics objects that belong to the gh_manager.

If so, then I believe this is a symptom of the problem that I was trying to
describe during our last developer meeting.  I think the solution is to either
do a better job of locking threads while using graphics objects or to make
graphics objects use copy-on-write semantics so that they can't be modified in
one thread while being used in another.

    _______________________________________________________

Reply to this item at:

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

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