Le 10/02/2017 à 17:58, Guillaume Munch a écrit :
There's more data, but I am not sure how to interpret the results that
massif-visualizer shows.
If you send the file or make it available, I can take a look.
Here it is. But if it is like callgrind, it might lack the symbols.
Interestingly, the massif output that you sent also points to
MathMacro::clone(). Besides the obvious getTextLayout leak that needs to
be plugged, would you have an idea on why it is specifically macros that
appear here (with an increasing memory use, like the other)? I do not
see other math objects doing that.
Note that there are other sources that point to MathAtom::MathAtom, as
the drop in percentage shows.
JMarc
->09.75% (18,139,776B) 0x8DA8B5:
lyx::MathMacro::MathMacro(lyx::MathMacro const&) (MathMacro.cpp:299)
| ->09.75% (18,139,776B) 0x8DB03F: lyx::MathMacro::clone() const
(MathMacro.cpp:394)
| ->09.75% (18,139,776B) 0x8AD26D:
lyx::MathAtom::MathAtom(lyx::MathAtom const&) (MathAtom.cpp:35)
| ->03.42% (6,356,216B) 0x86ADFE:
std::vector<lyx::MathAtom>::operator=(std::vector<lyx::MathAtom> const&)
(stl_construct.h:75)
| | ->01.16% (2,158,056B) 0x8EF837: lyx::(anonymous
namespace)::Parser::parse(lyx::MathData&, unsigned int,
lyx::Inset::mode_type) (vector:111)
| | | ->01.16% (2,158,056B) 0x8EFC99:
lyx::mathed_parse_cell(lyx::MathData&, lyx::docstring const&,
lyx::Parse::flags) (MathParser.cpp:2150)
| | | | ->01.16% (2,158,056B) 0x9079EB: lyx::asArray(lyx::docstring
const&, lyx::MathData&, lyx::Parse::flags) (MathSupport.cpp:985)
| | | | ->01.16% (2,158,056B) 0x8DBBE8:
lyx::MathMacro::updateRepresentation(lyx::Cursor*, lyx::MacroContext
const&, lyx::UpdateType, int) (MathMacro.cpp:699)
