|
From: | Dmitri A. Sergatskov |
Subject: | [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem |
Date: | Tue, 8 Jan 2019 17:01:33 -0500 (EST) |
User-agent: | Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:64.0) Gecko/20100101 Firefox/64.0 |
Follow-up Comment #30, bug #55287 (project octave): And then more fun if you stop the cycle clf and restart it (w/o restarting the octave): <<<....>>> 35 288028 780 36 288028 0 37 288732 704 38 289512 780 39 290292 780 40 291072 780 41 291856 784 42 292636 780 43 293416 780 44 294200 784 ^C octave:5> clf octave:6> i=0 i = 0 octave:7> memold=memory().MemUsedOctave; octave:8> do > i=i+1; > data=rand(100000,1); > #clf #uncomment to avoid leak > plot(data); > drawnow > mem=memory().MemUsedOctave; > mc=mem-memold; > disp([i mem mc]) > memold=mem; > until i>100000 1 292948 -2032 2 292948 0 3 292948 0 4 292948 0 5 292948 0 6 292948 0 7 292948 0 8 292948 0 9 292948 0 10 292948 0 11 292948 0 12 292948 0 13 292948 0 14 292948 0 15 292948 0 16 292948 0 17 292948 0 18 292948 0 19 292948 0 20 292948 0 21 292948 0 22 292948 0 23 292948 0 24 292948 0 Dmitri. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?55287> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |