https://bugs.kde.org/show_bug.cgi?id=522615
--- Comment #24 from Xinyu Tu <[email protected]> --- Some observations from local debugging: I've been tracking this memory growth locally and wanted to share a few observations regarding how these components interact during this state: 1: kwalletd6 behavior: It acts as a passive, event-driven daemon handling incoming D-Bus requests. The rapid memory growth (~14 MB/s RSS in my environment) appears to be a downstream effect driven by an unusually high volume of incoming traffic—specifically continuous CreateItem and GetProperties requests for org.freedesktop.Secret.Item.Attributes. 2: Client-side request frequency: Monitoring D-Bus traffic indicates that plasma-nm (inside kded6) enters a high-frequency retry/polling loop under specific conditions (such as syncing a specific Wi-Fi credential UUID like {...};802-11-wireless-security). 3: Cascade effect: When this loop triggers at ~10ms intervals, session and proxy objects are instantiated faster than the standard lifecycle cleanup can process them, leading to high CPU load in kded6 and steady RSS growth in kwalletd6. -- You are receiving this mail because: You are watching all bug changes.
