https://bugs.kde.org/show_bug.cgi?id=522615
zosima <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from zosima <[email protected]> --- Reproduced, with a much faster leak rate, evidence tying it to the kwalletd6 -> ksecretd loop in bug 522307, and confirmation that downgrading pam_kwallet6 (per that bug's bisect) eliminates the problem. SOFTWARE VERSIONS OS: Fedora 44 (KDE spin), kernel 7.0.14-201.fc44.x86_64 Plasma: 6.7.1 (Wayland) kf6-kwallet / kwalletd6: 6.27.0-1.fc44 pam-kwallet (pam_kwallet6): 6.7.1-1.fc44 Secret Service backend: ksecretd OBSERVED - kwalletd6 D-Bus-activated at 10:43:07 after a fresh boot + login (journalctl confirms zero suspend/resume events in the boot). OOM kill at 11:38:01 — so ~55 GB anon RSS in under 55 minutes, roughly 1 GB/min versus the ~28 MB/min in the original report. It exhausted 64 GB RAM plus most of an 8 GB swap. - Kernel OOM record: Out of memory: Killed process 26948 (kwalletd6) total-vm:64172028kB, anon-rss:55416916kB, file-rss:5544kB, shmem-rss:0kB, UID:1000 pgtables:124492kB oom_score_adj:200 - systemd accounting for the unit: dbus-:[email protected]: Consumed 14min 11.211s CPU time over 54min 55.588s wall clock time, 53G memory peak, 7.7G memory swap peak. - Same post-restart warnings as the original report: received unexpected result type ao from Completed signal instead of expected o g_task_return_error: assertion 'error != NULL' failed GTask secret_service_real_prompt_async (...) finalized without ever returning - Additional failure face: ~50 minutes after the OOM respawn, the replacement kwalletd6 instance silently deadlocked — 0% CPU but no reply to any D-Bus call (even org.kde.KWallet.wallets timed out after 25 s), so every client (kwalletmanager, kded6 NM secret agent) failed with timeouts. Killing it and letting D-Bus respawn recovered. So the Secret Service client path in kwalletd6 can leak-loop OR deadlock depending on state. - Link to bug 522307: for the entire window that kwalletd6 was growing, ksecretd (--pam-login) was spinning at ~32% CPU; the moment kwalletd6 was killed, ksecretd went fully idle. That report's dbus-monitor capture shows kwalletd6 calling ReadAlias("default") on ksecretd in a tight loop, and its reporter bisected the trigger to pam_kwallet6 6.7.1 — the version installed here. CONFIRMED MITIGATION Downgrading pam-kwallet to 6.6.4-1.fc44 (Fedora carries no 6.7.0) eliminates the issue: after reboot, ksecretd consumes zero CPU (previously ~32% from the first minute of the session) and kwalletd6 RSS stays flat at ~60 MB. This independently confirms the pam_kwallet6 6.7.1 bisect from bug 522307 on a second distribution. Suggest cross-linking the two reports — 522307 (CPU loop) and this one (memory growth) look like two symptoms of the same defect. -- You are receiving this mail because: You are watching all bug changes.
