https://bugs.kde.org/show_bug.cgi?id=526693
--- Comment #2 from [email protected] --- Important info: 1. Valgrind Limitations: I cannot capture a traditional Valgrind log by stopping the background service. If kded6 is stopped or frozen during the suspend handshake, it fails to release display, hardware or other drivers, resulting in a severe kernel deadlock that completely crashes the OS on suspend preventing the log capture. 2. Leak Trigger (Long vs. Short Sleep): The memory leak appears to be tied strictly to prolonged sleep periods. I tested a short 10-minute sleep cycle, and the leak did not trigger. However, after leaving the PC suspended for several hours, the leak immediately began upon waking. 3. KWallet Connection: I noticed a key behavioral difference after a long sleep cycle—the desktop prompts for the Wi-Fi/network password upon waking, which does not happen after a short sleep. The memory leak in kded6 and kwalletd6 starts the moment this password prompt interaction is forced, this prompt coming up appears to be connected in some way. I will attempt to attach a log next time the issue triggers following a long sleep period, likely later day tomorrow. -- You are receiving this mail because: You are watching all bug changes.
