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

[John Donoghue]

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

                 Summary: Crash on GUI exiting with octave_base_value objects
still open.
                 Project: GNU Octave
            Submitted by: lostbard
            Submitted on: Sat 05 Feb 2022 02:00:08 PM UTC
                Category: Interpreter
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Segfault, Bus Error, etc.
                  Status: None
             Assigned to: None
         Originator Name: JohnD
        Originator Email: 
             Open/Closed: Open
                 Release: 7.0.90
         Discussion Lock: Any
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

Its been reported before but the last bug was 'fixed' as it appeared to have
stopped happending. (Bug #57945)


Run octave in gui mode: octave --gui


Create a audio player object

a = audioplayer([1:100], 44000)


Close octave by clicking on the close gadget on the octave title bar.

Octave closes, but crashes during the shutdown.

A quick run with debug - stops for me at:


Thread 1 "octave-gui" received signal SIGSEGV, Segmentation fault.
0x00007ff5bb278c22 in octave_value::~octave_value (this=0x7ff5549832d0,
__in_chrg=<optimized out>) at ../libinterp/octave-value/ov.h:387


I can make it happen in both linux and windows using same method.

I can cause the same error with external octave packages as well by creating
an object and not clearing it before closing by the close button.





    _______________________________________________________

Reply to this item at:

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

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