Am 22.01.2012 um 21:58 schrieb Jean-Marc Lasgouttes: > Le 22/01/12 02:09, Lars Gullik Bjønnes a écrit : >> My testing so far says the opposite. We are continually using more and >> more memory. Not especially fast, but it is there. > > A good tool to know where memory goes is the massif tool of valgrind.
I've tried to use Instruments Leak-Detector on Mac. 1. It doesn't find any suspicious leaks - the growing memory is not lost. 2. The growing memory is allocated in TextClass constructor - about 40k per autosave operation. 3. Call Stack: Total % Bytes Library Symbol Name ... 11.4 1.65 MB lyx::frontend::GuiView::autoSave() 11.4 1.64 MB lyx::Buffer::cloneBufferOnly() const 11.4 1.64 MB lyx::Buffer::Buffer(std::string const&, bool, lyx::Buffer const*) 11.4 1.64 MB lyx::Buffer::Impl::Impl(lyx::Buffer*, lyx::support::FileName const&, bool, lyx::Buffer const*) 11.4 1.64 MB lyx::BufferParams::BufferParams() 11.4 1.64 MB lyx::BufferParams::makeDocumentClass() 11.4 1.64 MB lyx::DocumentClassBundle::makeDocumentClass(lyx::LayoutFile const&, lyx::LayoutModuleList const&) 11.4 1.64 MB lyx::DocumentClassBundle::newClass(lyx::LayoutFile const&) 11.2 1.61 MB lyx::DocumentClass::DocumentClass(lyx::LayoutFile const&) 11.2 1.61 MB lyx::TextClass::TextClass(lyx::TextClass const&) 1 minute later Total % Bytes Library Symbol Name ... 11.7 1.69 MB lyx::DocumentClassBundle::newClass(lyx::LayoutFile const&) 11.4 1.65 MB lyx::TextClass::TextClass(lyx::TextClass const&) Stephan
