https://bugs.kde.org/show_bug.cgi?id=396651
--- Comment #1 from aditsu <adi...@yahoo.com> --- In the meantime I ran it again with --show-leak-kinds=all, the memory usage grew by about 1.3GB in 1.5 days; after closing it I got a 33MB log file that ends in: ==19355== 2,097,152 bytes in 1 blocks are still reachable in loss record 1,056 of 1,056 ==19355== at 0x4C2CF0F: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so) ==19355== by 0xAD42A9C: QArrayData::allocate(unsigned long, unsigned long, unsigned long, QFlags<QArrayData::AllocationOption>) (in /usr/lib64/libQt5Core.so.5.9.4) ==19355== by 0xAEEB676: ??? (in /usr/lib64/libQt5Core.so.5.9.4) ==19355== by 0xAEEB8DF: ??? (in /usr/lib64/libQt5Core.so.5.9.4) ==19355== by 0xAEE6265: QCoreApplication::postEvent(QObject*, QEvent*, int) (in /usr/lib64/libQt5Core.so.5.9.4) ==19355== by 0x1E6FEC30: ??? (in /usr/lib64/qt5/plugins/styles/breeze.so) ==19355== by 0x1E6FECC8: ??? (in /usr/lib64/qt5/plugins/styles/breeze.so) ==19355== by 0x1E6FA683: ??? (in /usr/lib64/qt5/plugins/styles/breeze.so) ==19355== by 0xAF0C838: QMetaObject::activate(QObject*, int, int, void**) (in /usr/lib64/libQt5Core.so.5.9.4) ==19355== by 0xAF0D1EE: QObject::destroyed(QObject*) (in /usr/lib64/libQt5Core.so.5.9.4) ==19355== by 0x9CB5C38: QWidget::~QWidget() (in /usr/lib64/libQt5Widgets.so.5.9.4) ==19355== by 0x9DFAAE8: QMenu::~QMenu() (in /usr/lib64/libQt5Widgets.so.5.9.4) ==19355== ==19355== LEAK SUMMARY: ==19355== definitely lost: 2,310 bytes in 44 blocks ==19355== indirectly lost: 53,983 bytes in 589 blocks ==19355== possibly lost: 12,321 bytes in 184 blocks ==19355== still reachable: 2,498,560 bytes in 4,263 blocks ==19355== of which reachable via heuristic: ==19355== newarray : 4,264 bytes in 1 blocks ==19355== suppressed: 0 bytes in 0 blocks ==19355== ==19355== For counts of detected and suppressed errors, rerun with: -v ==19355== ERROR SUMMARY: 177 errors from 177 contexts (suppressed: 0 from 0) -- You are receiving this mail because: You are watching all bug changes.
