https://bugs.kde.org/show_bug.cgi?id=489315
--- Comment #4 from Nate Graham <n...@kde.org> --- It certainly is from a user's point of view. :) The reason I opened this on DrKonqi is because the issue gets triggered by automatic client-side gdb tracing. This wasn't a thing that would happen automatically until recently. The window where you opt into it warns about unbounded networks downloads, but doesn't mention anything about local performance degradation while tracing happens. At the minimum this should be mentioned IMO, and ideally we should investigate why the tracing process consumes so much memory and CPU resources. -- You are receiving this mail because: You are watching all bug changes.
