https://bugs.kde.org/show_bug.cgi?id=393929
--- Comment #36 from Nate Graham <n...@kde.org> --- With my "member of the KDE team" hat on: I acknowledge this bug but cannot reproduce it, and memory leak bugs in general are incredibly hard to debug, even in the best case scenario where the reporter has localized the issue to just a specific widget or triggering behavior. It requires specialized skill that I unfortunately do not have, which is why I don't generally do much with bug reports about memory leaks. -- You are receiving this mail because: You are watching all bug changes.
