[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem
From: |
Pantxo Diribarne |
Subject: |
[Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem |
Date: |
Mon, 7 Jan 2019 16:16:35 -0500 (EST) |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:64.0) Gecko/20100101 Firefox/64.0 |
Follow-up Comment #20, bug #55287 (project octave):
About fontconfig, I observe something strange: in ft-text-renderer.cc, if I
change HAVE_FONTCONFIG to HAVE_XXXXXXX (so that Octave doesn't use fontconfig
at all), I observe the same direct leak.
Now about the 8 byte leaks that are observed when registering octave types,
they also happen using --no-gui-libs:
Direct leak of 8 byte(s) in 1 object(s) allocated from:
#0 0x7fddd3f36458 in operator new(unsigned long)
(/usr/lib/x86_64-linux-gnu/libasan.so.4+0xe0458)
#1 0x7fddd2748525 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)
../octavestable/libinterp/octave-value/ov-typeinfo.cc:154
#2 0x7fddd27db9e4 in
octave_int32_matrix::register_type(octave::type_info&)
../octavestable/libinterp/octave-value/ov-int32.cc:68
#3 0x7fddd27918c5 in install_types(octave::type_info&)
../octavestable/libinterp/octave-value/ov.cc:2939
#4 0x7fddd274719d in octave::type_info::type_info(int)
../octavestable/libinterp/octave-value/ov-typeinfo.cc:82
#5 0x7fddd315c097 in
octave::interpreter::interpreter(octave::application*)
../octavestable/libinterp/corefcn/interpreter.cc:384
#6 0x7fddd1a5c0b1 in octave::application::create_interpreter()
../octavestable/libinterp/octave.cc:314
#7 0x7fddd1a5ca26 in octave::cli_application::execute()
../octavestable/libinterp/octave.cc:389
#8 0x562a8a333571 in main ../octavestable/src/main-cli.cc:92
#9 0x7fddced33b96 in __libc_start_main
(/lib/x86_64-linux-gnu/libc.so.6+0x21b96)
So this is clearly no threading issue but rather a problem in Octave's
interpreter initialization.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?55287>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Pantxo Diribarne, 2019/01/06
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Dmitri A. Sergatskov, 2019/01/06
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Pantxo Diribarne, 2019/01/06
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Dmitri A. Sergatskov, 2019/01/06
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Pantxo Diribarne, 2019/01/06
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Rik, 2019/01/06
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Pantxo Diribarne, 2019/01/07
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Rik, 2019/01/07
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem,
Pantxo Diribarne <=
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Rik, 2019/01/07
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Pantxo Diribarne, 2019/01/07
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Rik, 2019/01/07
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Rik, 2019/01/07
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Lars Kindermann, 2019/01/08
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Rik, 2019/01/08
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Rik, 2019/01/08
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Lars Kindermann, 2019/01/08
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Doug Stewart, 2019/01/08
- [Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem, Dmitri A. Sergatskov, 2019/01/08