| Summary: | Memory consumption keeps increasing when a screen switched off by nvidia-settings | ||
|---|---|---|---|
| Product: | [Plasma] KScreen | Reporter: | wojnilowicz <lukasz.wojnilowicz> |
| Component: | common | Assignee: | kscreen-bugs-null <kscreen-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | kde, nate |
| Priority: | NOR | Keywords: | regression |
| Version: | 5.27.0 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=466362 | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
wojnilowicz
2023-02-18 12:00:16 UTC
It's not recommended to use NVIDIA tools to manage screens for many reasons, and this is one of them. :) I think it's fixable. Memory consumption stops increasing as soon as the laptop screen is turned on again in nvidia-settings (although what has been consumed already isn't returned :) ) Memory consumption resumes increasing as soon as the laptop screen is turned off. That means that I can switch increased memory consumption on and off. There are some screen settings that can be set through nvidia-settings and not through KDE settings. By saying "it's not recommended" do you mean it's not be meant to be fixed to work as before? KScreen watches for external changes, such as those done by nvidia-settings. Likely what's happening is that somehow the changes being done by nvidia-settings are triggering a condition in kscreen that never stops doing something. Ok, it seems so. Memory increases happen at a rate of 1 MB per read out by old KDE System Monitor. I'm not sure how to debug it. Can I help somehow to debug it further? If you disable the "KScreen 2" service in the System Settings "Background Services" page and reboot, does the issue stop happening? (remember to turn it back on after testing!) When: 1) laptop screen: disabled at startup, monitor screen: enabled at startup, kscreen2: enabled at startup No increases in memory consumption observed when enabling and disabling my screens in different configurations through nvidia-settings. I don't know on what my system depends to keep the setting to disable my laptop screen at startup but when it does so I'm happy. I want to add that at the login screen both screens are enabled and after login my laptop screen gets disabled by itself. It's ok for me. 2) laptop screen: enabled at startup, monitor screen: enabled at startup, kscreen2: disabled at startup No increases in memory consumption observed when enabling and disabling my screens in different configurations through nvidia-settings. 3) laptop screen: enabled at startup, monitor screen: enabled at startup, kscreen2: enabled at startup Increases in memory consumption observed when disabling my laptop screen through nvidia-settings (as reported initially). *** This bug has been marked as a duplicate of bug 466362 *** |