-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Memory Leak after monitor power saving #1087
Comments
Do you have the latest version installed? Perhaps from Chaotic AUR? |
@mmstick could I replicate this issue even with auto-cpufreq installed? |
@mmstick Thanks for the reply. I'm using the cosmic packages in the standard vanilla arch repos which I assume are currently based off of the tagged alpha 4 release. For clarification this issue happens when you use the "cosmic settings > power and battery > turn off the screen after" setting . I believe that there is a minimum amount of time you have to wait until the memory leak gets triggered because if you let the screens go to sleep using this feature and then immediately wake them up it doesn't trigger the leak. I don't know what the time frame to trigger it is though, but it's likely to be somewhere between a few minutes to an hour after you let the power management trigger. |
memory leak issue is no longer happening as of alpha 5 |
System Specs:
Arch Linux
Cosmic alpha 4
Kernel: 6.12.4-arch1-1
GPU: AMD RX 7900 XT
CPU: i7-12700K
RAM: 32GB
Testing out the monitor power saving features of COSMIC. I have two external displays are connected using display port. When the displays are shut down for power saving, I don't lock the desktop. When I come back after an hour, I notice that all the apps that were open prior to monitor shutdown have all been closed and the session has been locked. After logging back in if I open an app it will proceed to memory leak until it fills all memory prompting a reboot to solve. The expected behavior would be to have all apps still open when I come back and power on the monitors.
The text was updated successfully, but these errors were encountered: