[Octave-bug-tracker] [bug #55052] Memory consumption of figure command going up significantly from 4.2 to 4.4

[John W. Eaton]

Follow-up Comment #8, bug #55052 (project octave):

With the latest sources (stable or default) the qt graphics toolkit is loaded
dynamically.  So that means you should see a big jump for the first figure as
Octave loads the QtOpenGL and dependent libraries.  When __init_qt__ is
executed it calls mlock, so Octave won't unload the .oct file and libraries. 
Even after I tried munlock and calling __shutdown_qt__ and clear all, I was
unable to get Octave to unload the __init_qt__.oct file.

Apart from the memory allocated to the shared library, I also see the usage go
up with figure creation.  I'm looking at the value of RSS reported by ps:


 69140  ## before qt graphics is loaded
139156  ## after figure (1)
152580  ## after figure (2)
165880  ## after figure (3)
163992  ## after close (3)
161624  ## after close (2)
157900  ## after close (1)


So it is increasing by about 13MB for each new figure and only decreasing by
about 2MB, though closing the last figure seems to release more.

Here is what I see with fltk:


 67296  ## before fltk graphics is loaded
100560  ## after figure (1)
101008  ## after figure (2)
101272  ## after figure (3)
101536  ## after close (3)
102692  ## after close (2)
102692  ## after close (1)


It's no surprise that fltk is smaller than qt, but I don't understand what's
going on with this case because the size appears to increase when closing
figures?!?



    _______________________________________________________

Reply to this item at:

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

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