[Octave-bug-tracker] [bug #61005] clear does not always clear

[sylvain bougnoux]

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

                 Summary: clear does not always clear
                 Project: GNU Octave
            Submitted by: sbougnoux
            Submitted on: mar. 03 août 2021 14:10:06 UTC
                Category: None
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
                 Release: 6.3.0
         Discussion Lock: Any
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

It does not always happen but I remarked the following (maybe it is related to
strange feed-backs about memory some others have posted?). 

I create a gui (in a frame) and store its handle 'h' (as in the example).
Then sometimes I create a field (like 'h.foo=1')
Then I clear (I've tried 'clear; clear h; close all')
Then the variable 'h' does not exist anymore, fine.
Up to this, everything is correct.
Then I relaunch my script & recreate 'h' the same way but without adding field
'foo'.
Then up to my surprise, sometimes 'foo' still belongs to 'h', like 'h.foo'
does exist!!!
Then I cannot get rid of 'h.foo' through the various clear mentioned above,
I've to restart Octave.

Unfortunately it does not always happen, maybe only when the mapping of memory
happens similarly (up to what it means?).

I send you this to help pinpoint a real issue. Hope this helps.




    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message posté via Savannah
  https://savannah.gnu.org/