Control: found -1 0.99.4-4
Control: tags -1 patch stretch upstream fixed-upstream
Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=100626
Control: affects -1 mate-power-manager gnome-power-manager
Hi,
This had been fixed in upower 0.99.5 upstream [1]. Therefore, the bug
Package: upower
Followup-For: Bug #689298
This seems to be fixed now. I'm also running a kernel without
CONFIG_TIMER_STATS and don't experience this problem.
Also the upstream changelog for version 0.9.19 states:
Do not continue to poll if /proc/timer_stats is not readable (Richard Hughes)
OK, I'm able to confirm the CPU waste on a kernel built without
CONFIG_TIMER_STATS=y run under qemu-kvm. I still haven't made upowerd
leak memory like I saw in the wild yet though.
To reproduce:
build and run a kernel without CONFIG_TIMER_STATS=y
run gnome-power-statistics
after some
Package: upower
Version: 0.9.17-1
Severity: important
I noticed upowerd using ~1.3 gigs of resident memory and burning most
of a cpu; strace proved to show that it was attempting to open
/proc/timer_stats over and over, failing, and logging an error about it
(which was redirected to /dev/null, so
4 matches
Mail list logo