https://bugs.kde.org/show_bug.cgi?id=489315
Bug ID: 489315
Summary: With automatic crash reporting and tracing, something
crashing in a loop can freeze and OOM the system
Classification: Applications
Product: drkonqi
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: grave
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
When something crashes in a loop, multiple DrKonqi instances will be created,
one per crash. Each one will try to trace and report the crash, spinning up a
new instance of GDB. GDB can be heavy, especially when it's allowed to download
debug symbols.
When this happen, you end up with multiple GDB processes competing for CPU and
memory resources that are becoming more scarce. The system slows to a crawl and
you either run out of memory or the OOM killer starts killings things.
It's not ideal, and worsens the already bad situation of something crashing a
loop.
Some kind of throttling or repeated crash detection would be a good idea.
--
You are receiving this mail because:
You are watching all bug changes.
