Memory Leaks
Mark Kretschmann <[email protected]>
| Newsgroups | gmane.comp.kde.devel.koffice |
|---|---|
| Message-ID | <[email protected]> |
Hey all, I did a Valgrind run today with KWord, with --leak-check=full, and the following came out of it: http://mark.kollide.net/ko/kword-valgrind2.txt Most of the leaks don't seem to be very critical, as far as I can see. But this one might be worth looking into: ==6523== 2,508 (224 direct, 2,284 indirect) bytes in 14 blocks are definitely lost in loss record 2,056 of 2,115 ==6523== at 0x4C28973: operator new(unsigned long) (vg_replace_malloc.c:261) ==6523== by 0x4F2EEEC: KoTextEditor::Private::documentCommandAdded() (KoTextEditor.cpp:128) ==6523== by 0x4F34CF4: KoTextEditor::qt_metacall(QMetaObject::Call, int, void**) (KoTextEditor.moc:317) ==6523== by 0x834CB26: QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (qobject.cpp:3280) ==6523== by 0x69863F0: QTextDocumentPrivate::endEditBlock() (qtextdocument_p.cpp:1183) -- Mark Kretschmann Amarok Developer, Software Engineer at KO GmbH Fellow of the Free Software Foundation Europe http://amarok.kde.org - http://fsfe.org - http://kogmbh.com