[Octave-bug-tracker] [bug #55064] Updating graphics object consumes memory

[anonymous]

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

                 Summary: Updating graphics object consumes memory
                 Project: GNU Octave
            Submitted by: None
            Submitted on: Tue 20 Nov 2018 03:53:23 PM UTC
                Category: Plotting
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Performance
                  Status: None
             Assigned to: None
         Originator Name: Robert F
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 4.4.1
        Operating System: GNU/Linux

    _______________________________________________________

Details:

I don't think this is the intended behavior of 'set(h,'xdata'...)' and I can't
figure out a way to update a plot, with identically sized 'data' arrays,
without octave searching for more memory with each update. 

Either using the 'set' or even 'delete(h); clear('h'), h=plot3();', when I
update the plot with a new set of data that is exactly the same dimensions,
new memory is reserved. This creates a huge problem where, in the simplified
script I have attached, octave's reserved memory goes from ~200MB to many GB's
very quickly. Is this the intended behavior of 'set' or is there a better way
that can be documented (or maybe I missed?) to update a plot? Regards, Robert.




    _______________________________________________________

Reply to this item at:

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

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