At some moment upowerd starts to use 100% of CPU (1 core) and consumes all memory until system reaches limit. I don't know neither exact cause, nor stacktrace of upowerd at the moment - system is unresponsive. I'm ready to provide any useful information to help with diagnostics. Version: 0.99.1
I experience this as well. This happens about once or twice per day on f20 and f21. "systemctl restart upower" helps, if I realize the problem early enough to get a shell open. Upower version is 0.99.1 on up-to-date f21 and f20, both with updates-testing enabled. "journalctl -xu upower" shows nothing noteworthy, but I probably couldn't tell for upower anyway. Let me know, if you need some logs or so.
*** Bug 1163747 has been marked as a duplicate of this bug. ***
*** Bug 1130776 has been marked as a duplicate of this bug. ***
This is almost certainly: https://bugs.freedesktop.org/show_bug.cgi?id=82659 Any chance we can get a new release and/or update with those patches? Having to manually kill an out-of-control upower on a regular basis isn't fun.
fwiw, I just hit this too on f21 beta. Definitely would look good to have this patched for release! Mark
As a workaround I used SystemD to limit the memory upower is allowed to use. Just add the following lines to /usr/lib/systemd/system/upower.service: MemoryAccounting=true MemoryLimit=256M I never hit this problem again since my last post, i.e. the last three weeks.
I think this might help: https://admin.fedoraproject.org/updates/upower-0.99.2-1.fc21 -- if it does, please give positive karma. Thanks.
I 0.99.2-1.fc21 but I still encounter the memory leak. Just restarted upowerd after it used around 500 megabytes of system RAM...
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.