https://bugs.kde.org/show_bug.cgi?id=392133
Nikita Melnichenko <nikita+...@melnichenko.name> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |NEEDSINFO
Resolution|--- |WAITINGFORINFO
--- Comment #25 from Nikita Melnichenko <nikita+...@melnichenko.name> ---
>From the report, the peak allocations happen in Qt5 and KF5 libs. I don't see
any actual krusader code involved, just internal event handlers.
Most heap peak is coming from libKF5Solid, which is a hardware tracker. Wild
guess: if you have a faulty hardware that keeps disconnecting-reconnecting, it
frequently triggers those event in Solid, which connect Qt objects and doing
other stuff keeping track every such event. When you close Krusader, all the
memory from this "hardware log" is freed and we see no leaks.
It will be helpful if you get debug symbols for KF5 libs as well and rerun the
tool, then it may give us a clue on what kind of event it is.
--
You are receiving this mail because:
You are watching all bug changes.
