Bug 1599528
Summary: | gnome-software high memory consumption (constant) and CPU spikes (occasional) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | James Radtke <jradtke> |
Component: | gnome-software | Assignee: | Richard Hughes <rhughes> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 33 | CC: | ego.cordatus, gabriel, huniyat, klember, pablodav, rgd720, rhughes, trey, truls |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-01-23 19:53:05 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
James Radtke
2018-07-10 02:50:50 UTC
I have the same issue and I am also running Lenovo (T430). I notice the memory drain when I return from standby or sleep modes. It makes returning from these states slower than forcing a power down and restarting. It doesn't seem like this program should ever need more than 150MB when running in the background. That being the case, maybe an easier fix would be to monitor memory allocation every 5 minutes or so and when it gets to 150, auto-end the program and re-start it. This looks like a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1583300 This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. I have been checking these issues In this comment: https://gitlab.gnome.org/GNOME/gnome-software/issues/194#note_472798 Kalev Lember @klember says: "Part of the problem is that right now gnome-software never unloads its UI when closing the window. We have a plan to start doing that in the future and that should help with the memory usage." Today I see on my system gnome-software uses 377 MB, probably due to this current bug. Potentially related too: https://bugzilla.redhat.com/show_bug.cgi?id=1668808 https://bugzilla.redhat.com/show_bug.cgi?id=1583300 https://gitlab.gnome.org/GNOME/gnome-software/issues/486 https://gitlab.gnome.org/GNOME/gnome-software/issues/453 https://gitlab.gnome.org/GNOME/gnome-software/issues/269 https://gitlab.gnome.org/GNOME/gnome-software/issues/191 Maybe not all of them are related, but at least looks like the bug is recognized by Kalev, as a background program is running but not closing an UI! This has a bad impact in the overall performance of low-memory systems, also makes not sense to have all the time around 300 or 400Mb (less or more depending what it is doing) on a process that is only used to install software or updates. This is still valid in fedora 32, gnome-software uses around 500MB in background even when GUI is not in use. I think this is main reason why I can't recommend Fedora for every device, as Fedora is perfect for most of the use cases and is my main distro but for specific cases where I use to install linux on old wks, 500MB in use all the time is too much just to get updates in background once a day or a week. Its becoming a problem in Fedora32 (I dont have a lot of ram), gnome-system-monitor shows "/usr/bin/gnome-software --gapplication-service" eating up to 1GB of memory even when closed, and it stays up. I'm investigating what "--gapplication-service" is, and maybe if disabling that is a good idea or not. What I tried: When ending or killing gnome-software, and then reopening, it consumes only around 50Mb which is normal (even when installing apps, or doing some updates, apparently just stays around that consumption), but nothing like the 900mb it uses even if its not opened, after system boot.- Pseudo work-around: Killing gnome-software after boot so it doesn't start to eat up memory after some time. *It might be healthy to make sure its not doing important things before closing it* What I will try: Disabling it as a "service" if that is possible so it opens only when I open it and not in the background, I do all the updates daily and manually so Im not concerned about auto-updates. *Sorry for bad English* Looks like this was resolved now in latest releases. |