https://bugs.kde.org/show_bug.cgi?id=439496
--- Comment #1 from David <david.cortes.riv...@gmail.com> --- And BTW, valgrind shows a memory leak too: ==16644== definitely lost: 19,401 bytes in 980 blocks ==16644== indirectly lost: 11,013 bytes in 348 blocks ==16644== possibly lost: 1,773,992 bytes in 4,482 blocks ==16644== still reachable: 75,351,792 bytes in 978,899 blocks ==16644== of which reachable via heuristic: ==16644== length64 : 115,288 bytes in 309 blocks ==16644== newarray : 1,028,064 bytes in 782 blocks ==16644== multipleinheritance: 83,040 bytes in 652 blocks ==16644== suppressed: 28 bytes in 2 blocks ==16644== Rerun with --leak-check=full to see details of leaked memory ==16644== ==16644== Use --track-origins=yes to see where uninitialised values come from ==16644== For lists of detected and suppressed errors, rerun with: -s ==16644== ERROR SUMMARY: 16 errors from 11 contexts (suppressed: 0 from 0) ^C [1]+ Exit 255 valgrind plasma-discover -- You are receiving this mail because: You are watching all bug changes.
