[drkonqi] [Bug 489315] With automatic crash reporting and tracing, something crashing in a loop can freeze and OOM the system
https://bugs.kde.org/show_bug.cgi?id=489315 Nate Graham changed: What|Removed |Added Version||6.6.0 Fixed/Implemented|| In|| -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 489315] With automatic crash reporting and tracing, something crashing in a loop can freeze and OOM the system
https://bugs.kde.org/show_bug.cgi?id=489315 Harald Sitter changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #16 from Harald Sitter --- This should be largely resolved. drkonqi only runs a single trace across different instances https://invent.kde.org/plasma/drkonqi/-/tree/3433c67f134c0f41cc000942d24dc2b169061a20/src/backtracegenerator.cpp#L76 each instance constrains their memory profile depending on available memory https://invent.kde.org/plasma/drkonqi/-/tree/3433c67f134c0f41cc000942d24dc2b169061a20/src/systemd/memoryfence.cpp#L147 terminates gdb if the memory pressure becomes too high https://invent.kde.org/plasma/drkonqi/-/tree/3433c67f134c0f41cc000942d24dc2b169061a20/src/systemd/memorypressure.cpp#L147 trace behavior inside gdb is also adapting to available memory to prevent OOM scenarios https://invent.kde.org/plasma/drkonqi/-/tree/3433c67f134c0f41cc000942d24dc2b169061a20/src/systemd/memoryfence.cpp#L127 -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 489315] With automatic crash reporting and tracing, something crashing in a loop can freeze and OOM the system
https://bugs.kde.org/show_bug.cgi?id=489315 Nate Graham changed: What|Removed |Added Severity|crash |grave -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 489315] With automatic crash reporting and tracing, something crashing in a loop can freeze and OOM the system
https://bugs.kde.org/show_bug.cgi?id=489315 --- Comment #15 from Roke Julian Lockhart Beedell <[email protected]> --- (In reply to Louis Moureaux from comment #14) Tentatively, I agree. The sole time I experienced this, I lost a render to it. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 489315] With automatic crash reporting and tracing, something crashing in a loop can freeze and OOM the system
https://bugs.kde.org/show_bug.cgi?id=489315 --- Comment #14 from Louis Moureaux --- Shouldn't the importance be higher than "crash"? This can freeze or even crash the whole system, not just a single app. There is definitely the risk of losing all unsaved work if one needs to force a reboot. I had this in the middle of a Zoom call, imagine if it had been a job interview... -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 489315] With automatic crash reporting and tracing, something crashing in a loop can freeze and OOM the system
https://bugs.kde.org/show_bug.cgi?id=489315 Nate Graham changed: What|Removed |Added CC||[email protected] --- Comment #13 from Nate Graham --- *** Bug 502446 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 489315] With automatic crash reporting and tracing, something crashing in a loop can freeze and OOM the system
https://bugs.kde.org/show_bug.cgi?id=489315 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 489315] With automatic crash reporting and tracing, something crashing in a loop can freeze and OOM the system
https://bugs.kde.org/show_bug.cgi?id=489315 --- Comment #12 from Louis Moureaux --- > I added MemoryMax=1GB in > /usr/lib/systemd/user/[email protected], and now gdb gets > killed by the OOM killer when it goes overboard. The correct syntax is "MemoryMax=1G", sorry. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 489315] With automatic crash reporting and tracing, something crashing in a loop can freeze and OOM the system
https://bugs.kde.org/show_bug.cgi?id=489315 Louis Moureaux changed: What|Removed |Added CC||[email protected] --- Comment #11 from Louis Moureaux --- DrKonqi keeps freezing my system each time Akonadi or Kontact crashes, which unfortunately happens quite often. A single gdb process uses over 8GB of RAM (with debug packages installed... how can this be?). I added MemoryMax=1GB in /usr/lib/systemd/user/[email protected], and now gdb gets killed by the OOM killer when it goes overboard. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 489315] With automatic crash reporting and tracing, something crashing in a loop can freeze and OOM the system
https://bugs.kde.org/show_bug.cgi?id=489315 Nate Graham changed: What|Removed |Added CC||[email protected] --- Comment #10 from Nate Graham --- *** Bug 495953 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 489315] With automatic crash reporting and tracing, something crashing in a loop can freeze and OOM the system
https://bugs.kde.org/show_bug.cgi?id=489315 --- Comment #9 from Harald Sitter --- Git commit c842292f5ac24babdd8c1e1fe4355b10181f8f2f by Harald Sitter. Committed on 06/11/2024 at 15:29. Pushed by sitter into branch 'master'. backtracegenerator: implement a serialization lock to prevent systems from drowning in gdb instances, we now establish a serialization lock in the form of a file lock. only a single debugger may be active at a time this only partially fixes the problem since a single debugger may still OOM the system. we still want a better solution, such as resource constraining via systemd, in the long run. M +78 -3src/backtracegenerator.cpp M +6-1src/backtracegenerator.h https://invent.kde.org/plasma/drkonqi/-/commit/c842292f5ac24babdd8c1e1fe4355b10181f8f2f -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 489315] With automatic crash reporting and tracing, something crashing in a loop can freeze and OOM the system
https://bugs.kde.org/show_bug.cgi?id=489315 Nate Graham changed: What|Removed |Added CC||[email protected] --- Comment #8 from Nate Graham --- *** Bug 495366 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 489315] With automatic crash reporting and tracing, something crashing in a loop can freeze and OOM the system
https://bugs.kde.org/show_bug.cgi?id=489315 Roke Julian Lockhart Beedell <[email protected]> changed: What|Removed |Added CC||4wy78uwh@rokejulianlockhart ||.addy.io -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 489315] With automatic crash reporting and tracing, something crashing in a loop can freeze and OOM the system
https://bugs.kde.org/show_bug.cgi?id=489315 --- Comment #7 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/drkonqi/-/merge_requests/268 -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 489315] With automatic crash reporting and tracing, something crashing in a loop can freeze and OOM the system
https://bugs.kde.org/show_bug.cgi?id=489315 Akseli Lahtinen changed: What|Removed |Added CC||[email protected] --- Comment #6 from Akseli Lahtinen --- I have same issue - If i use automatic crash reporting, gdb manages to somehow eat all my 16gb of RAM - If i use coredumpctl debug for same crash, it doesnt use nearly as much memory Unsure what is going on here, I managed to get it with plasmashell crash today. Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.80 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.9.12-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 6600 -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 489315] With automatic crash reporting and tracing, something crashing in a loop can freeze and OOM the system
https://bugs.kde.org/show_bug.cgi?id=489315 [email protected] changed: What|Removed |Added CC||[email protected] -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 489315] With automatic crash reporting and tracing, something crashing in a loop can freeze and OOM the system
https://bugs.kde.org/show_bug.cgi?id=489315 Nate Graham changed: What|Removed |Added CC||[email protected] --- Comment #5 from Nate Graham --- *** Bug 490527 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 489315] With automatic crash reporting and tracing, something crashing in a loop can freeze and OOM the system
https://bugs.kde.org/show_bug.cgi?id=489315 --- Comment #4 from Nate Graham --- 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.
[drkonqi] [Bug 489315] With automatic crash reporting and tracing, something crashing in a loop can freeze and OOM the system
https://bugs.kde.org/show_bug.cgi?id=489315 --- Comment #3 from Harald Sitter --- I wonder if this is really a bug in drkonqi... in practice even a single trace can OOM. OOM in of itself isn't a defect. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 489315] With automatic crash reporting and tracing, something crashing in a loop can freeze and OOM the system
https://bugs.kde.org/show_bug.cgi?id=489315 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=420443 --- Comment #2 from Nate Graham --- Sort of... this is about the performance impact more so than the ugly system tray full of sad face icons. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 489315] With automatic crash reporting and tracing, something crashing in a loop can freeze and OOM the system
https://bugs.kde.org/show_bug.cgi?id=489315 --- Comment #1 from Harald Sitter --- Kind of dupe of bug #420443? -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 489315] With automatic crash reporting and tracing, something crashing in a loop can freeze and OOM the system
https://bugs.kde.org/show_bug.cgi?id=489315 TraceyC changed: What|Removed |Added CC||[email protected] -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 489315] With automatic crash reporting and tracing, something crashing in a loop can freeze and OOM the system
https://bugs.kde.org/show_bug.cgi?id=489315 Bug Janitor Service changed: What|Removed |Added Severity|grave |crash -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 489315] With automatic crash reporting and tracing, something crashing in a loop can freeze and OOM the system
https://bugs.kde.org/show_bug.cgi?id=489315 Nate Graham changed: What|Removed |Added CC||[email protected] -- You are receiving this mail because: You are watching all bug changes.
