[Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem

[Rik]

Update of bug #55287 (project octave):

                  Status:         Patch Submitted => In Progress            

    _______________________________________________________

Follow-up Comment #19:

I ran the tst_leak.m script with one repetition and with 100 repetitions.  In
each case, the amount of memory now leaked is the same.  That's good, the leak
is no longer growing without bound.

There are two remaining leaks.  The first is


Direct leak of 4352 byte(s) in 17 object(s) allocated from:
    #0 0x7fada948fb50 in __interceptor_malloc
(/usr/lib/x86_64-linux-gnu/libasan.so.4+0xdeb50)
    #1 0x7fad9f40e8ed  (/usr/lib/x86_64-linux-gnu/libfontconfig.so.1+0x1d8ed)


I think we have had this one before in the past.  It may required getting the
debug versions of libfontconfig installed to see if there is any more
information to be gained.

The second is a series of 8 byte leaks which all have the same form of
starting with QApplicationPrivate::notify_helper.


Direct leak of 8 byte(s) in 1 object(s) allocated from:
    #0 0x7fada9491458 in operator new(unsigned long)
(/usr/lib/x86_64-linux-gnu/libasan.so.4+0xe0458)
    #1 0x7fada73d74f5 in
octave::type_info::register_type(std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > const&,
std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char>
> const&, octave_value const&, bool)
libinterp/octave-value/ov-typeinfo.cc:154
    #2 0x7fada7487a3a in octave_int8_scalar::register_type(octave::type_info&)
libinterp/octave-value/ov-int8.cc:75
    #3 0x7fada741ed01 in install_types(octave::type_info&)
libinterp/octave-value/ov.cc:2925
    #4 0x7fada73d616d in octave::type_info::type_info(int)
libinterp/octave-value/ov-typeinfo.cc:82
    #5 0x7fada7de1f89 in
octave::interpreter::interpreter(octave::application*)
libinterp/corefcn/interpreter.cc:384
    #6 0x7fada6713801 in octave::application::create_interpreter()
libinterp/octave.cc:314
    #7 0x7fada8d908b6 in octave::octave_interpreter::execute()
libgui/src/main-window.cc:115
    #8 0x7fada8f60e0c in
octave::octave_interpreter::qt_static_metacall(QObject*, QMetaObject::Call,
int, void**) libgui/src/moc-main-window.cc:89
    #9 0x7fada1350121 in QObject::event(QEvent*)
(/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x2ba121)
    #10 0x7fada209e82b in QApplicationPrivate::notify_helper(QObject*,
QEvent*) (/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x15482b)


This is a very small leak, but I'm concerned because it may indicate that we
don't really understand what is happening cross-thread between the Qt GUI and
the main interpreter thread.


    _______________________________________________________

Reply to this item at:

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

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