https://bugs.kde.org/show_bug.cgi?id=526693
Bug ID: 526693
Summary: Memory leak in kded6 and kwalletd6 triggered by system
wake from sleep (tied to networkmanagement)
Classification: I don't know
Product: kde
Version First unspecified
Reported In:
Platform: Debian unstable
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
SUMMARY
A severe memory leak occurs in both `kded6` and `kwalletd6` immediately after
the system wakes up from sleep mode. The leak is heavily tied to the
`networkmanagement` module.
STEPS TO REPRODUCE (hopefully)
1. Use the system normally with Wi-Fi/networking connected.
2. Put the system into sleep mode (suspend).
3. Wake the system from sleep mode.
OBSERVED RESULT
Immediately upon waking, both `kded6` and `kwalletd6` begin rapidly consuming
memory:
- `kded6` leaks aggressively at a steady rate of roughly 1 MB/s at its highest,
can vary a lot, easily climbing up to 6 GB or higher if left unchecked (as far
as i observed).
- `kwalletd6` leaks at a slower, more sporadic/random rate, but has been
observed reaching around 2 GB, not sure if reaches higher.
MODULE DIAGNOSTICS:
- If I manually stop the `networkmanagement` module via System Settings (or
background services), the memory growth inside `kded6` immediately stops.
- Stopping the network management module does not stop the ongoing `kwalletd6`
leak; `kwalletd6` continues to hold/grow its memory until the process is
manually killed.
EXPECTED RESULT
Processes should handle network state changes post-resume without leaking
memory, and resources should be properly deallocated after fetching wireless
network credentials.
SOFTWARE/OS VERSIONS
Linux Distribution: Debian 14 / Unstable (sid)
KDE Plasma Version: 6.7.4
KDE Frameworks Version: 6.30.0
Qt Version: 6.11.2
Graphics Platform: X11
ADDITIONAL INFORMATION
Because the leak spans both the daemon framework (`kded6`) and the wallet
manager framework (`kwalletd6`) via the network applet interactions, it is
highly likely that a connection loop or unclosed query is repeating
indefinitely after a resume-from-sleep event. If left leaking for too long, it
has crashed the desktop with OOM before, though it took hours of use on a 16GB
system.
--
You are receiving this mail because:
You are watching all bug changes.
