| Summary: | DrKonqi fills /tmp with core dumps until (almost?) no space is left | ||
|---|---|---|---|
| Product: | [Applications] drkonqi | Reporter: | Louis Moureaux <m_louis30> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED DOWNSTREAM | ||
| Severity: | normal | CC: | nate, sitter |
| Priority: | NOR | ||
| Version First Reported In: | 6.3.3 | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Louis Moureaux
2025-04-15 16:40:34 UTC
Cannot reproduce. When I close drkonqi the cores get cleaned up. Because of 489315 DrKonqi usually gets killed by the OOM killer. (actually it's gdb that gets killed) Well. With the hack you put in place for bug #489315 you are also killing drkonqi, obviously no cleanup is going to happen then. Thanks for the hint. I now have updated my "hack" to the following: MemoryMax=2G MemorySwapMax=0 ExecStopPost=/bin/sh -c '/bin/rm -rf %T/drkonqi*' Works like a breeze, except most reports don't get submitted because even a Dolphin crash appears to use more than 2G of RAM. I'm not willing to give more to a process that can start at any time without warning. There's a smart solution in the works for 6.4 |