|
From: | Dmitri A. Sergatskov |
Subject: | [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem |
Date: | Thu, 27 Dec 2018 15:32:58 -0500 (EST) |
User-agent: | Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:64.0) Gecko/20100101 Firefox/64.0 |
Follow-up Comment #9, bug #55287 (project octave): I compiled octave with leak sanitizer flags. Running the loop with LSAN_OPTIONS=leak_check_at_exit=0 gives no errors. Running without this flag produces lots of errors and at the top I see something like that (after 100 cycles): ==20132==ERROR: LeakSanitizer: detected memory leaks Direct leak of 26500000 byte(s) in 331250 object(s) allocated from: #0 0x7f64fa95579f in __interceptor_malloc (/lib64/liblsan.so.0+0xf79f) #1 0x7f64f7f59d37 (/lib64/libfreetype.so.6+0x15d37) Number of bytes seems to increase linearly with number of cycles: #i bytes objects 1 43200 540 2 310480 3881 3 577680 7221 10 2448400 30605 30 7793200 97415 100 26500000 331250 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] |