[Octave-bug-tracker] [bug #63714] uitable may show nan with data=zero

[Liang Tang]

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

                 Summary: uitable may show nan with data=zero
                 Project: GNU Octave
               Submitter: lt1234
               Submitted: Thu 26 Jan 2023 09:04:31 PM UTC
                Category: Octave Function
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Incorrect Result
                  Status: None
             Assigned to: None
         Originator Name: lt1234
        Originator Email: 
             Open/Closed: Open
                 Release: 7.1.0
         Discussion Lock: Any
        Operating System: Microsoft Windows
           Fixed Release: None
         Planned Release: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Thu 26 Jan 2023 09:04:31 PM UTC By: Liang Tang <lt1234>
I have a gui kept crashing when the tables and plots are being updated.  The
gui contain a number of uitable, uicontrol and one axes.  There is no mex. 
Everything to build the gui are in text form and exercising basically put
contents in, delete contents and replace with other contents. When crash
occurred, there are no true computation.  Only get/put/delete type of action. 


There is no consistency that I can detect for what causes the crash.  There
are only numeric and character variables in uitable.  My prior issue is with
logical variable.  There is no logical variable in this case.  
  
These  are what I have observed:    

(1) The same data contents can crash Octave but it may not crash Octave in a
different occasion.  
(2) The same uitable celledit callback function can be exercised in the
command window when the gui is up.  But I have never been able to reproduce
the crash in command window using the identical callback m file. However, it
is quite easy to crash with gui activation.  
(3) I tried by placing a number of save in the callback function.  The mat
files saved before the crash do not show any abnormality.  
(4) The crashes typically occurred when one of the three uitable is being
updated, not axes being updated.  So all the drawnow have zero impact on the
crash. 
(5) Placing pause into various locations of the callback reduces the
likelihood of crash, but it does not eliminate the crash.   
(6) It is lot easier/quicker to crash in 7.1.0 than 6.3.0.     

>From that I build an uitable only example.  Up to now, it did not introduce
crash but it has some unexpected numbers (nan) show up while they should all
be zero.  Please see the attached zip file.  There are two ofig that
illustrate what I observe here.  

Thanks,






    _______________________________________________________
File Attachments:


-------------------------------------------------------
Date: Thu 26 Jan 2023 09:04:31 PM UTC  Name: nan.zip  Size: 10KiB   By: lt1234

<http://savannah.gnu.org/bugs/download.php?file_id=54268>

    _______________________________________________________

Reply to this item at:

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

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