https://bugs.kde.org/show_bug.cgi?id=503984
John Kizer <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WAITINGFORINFO Status|REPORTED |NEEDSINFO --- Comment #7 from John Kizer <[email protected]> --- Hi - I tried reproducing this in a Neon VM. After the Crash Report Sent screen showed up, drkonqi wasn't using a huge amount of CPU, but gdb was using a decent amount of CPU and had increasing memory usage - up until either it finally finished, or was stopped by the out-of-memory killer. Just to double-check, was it definitely the drkonqi process, and not gdb, that was using up those resources? And if you're able to try reproducing, I'm consistently able to reproduce this bug on an up-to-date system: https://bugs.kde.org/show_bug.cgi?id=498846 Thanks! -- You are receiving this mail because: You are watching all bug changes.
