Skip to content

memory leak in upowerd ? #1880

Open
wwwutz opened this issue Sep 14, 2020 · 2 comments
Open

memory leak in upowerd ? #1880

wwwutz opened this issue Sep 14, 2020 · 2 comments

Comments

@wwwutz
Copy link
Collaborator

wwwutz commented Sep 14, 2020

root:eldersoftheinternet:~/# grep VmPeak /proc/$(pgrep upowerd)/status
VmPeak:  3409372 kB

killed it to prevent others to debug it. Funny enough elders is the only workstation with that much upowerd mem usage.

I'd vote for removal, but anyway to prevent discussion just update sometime.

root:eldersoftheinternet:~/# bee query /usr/libexec/upowerd
upower-0.9.16-2.x86_64
  /usr/libexec/upowerd
root:eldersoftheinternet:~/# cat /proc/789/status 
Name:   upowerd
Umask:  0022
State:  S (sleeping)
Tgid:   789
Ngid:   0
Pid:    789
PPid:   1
TracerPid:      0
Uid:    0       0       0       0
Gid:    0       0       0       0
FDSize: 128
Groups:  
NStgid: 789
NSpid:  789
NSpgid: 789
NSsid:  789
VmPeak:  3409372 kB
VmSize:  3409356 kB
VmLck:         0 kB
VmPin:         0 kB
VmHWM:    235292 kB
VmRSS:     32540 kB
RssAnon:           28476 kB
RssFile:            4064 kB
RssShmem:              0 kB
VmData:  3153572 kB
VmStk:       132 kB
VmExe:       132 kB
VmLib:      9716 kB
VmPTE:      6292 kB
VmSwap:  3100324 kB
HugetlbPages:          0 kB
CoreDumping:    0
Threads:        3
SigQ:   1/127298
SigPnd: 0000000000000000
ShdPnd: 0000000000000000
SigBlk: 0000000000000000
SigIgn: 0000000000001000
SigCgt: 0000000180000002
CapInh: 0000000000000000
CapPrm: 0000003fffffffff
CapEff: 0000003fffffffff
CapBnd: 0000003fffffffff
CapAmb: 0000000000000000
NoNewPrivs:     0
Seccomp:        0
Speculation_Store_Bypass:       vulnerable
Cpus_allowed:   fff
Cpus_allowed_list:      0-11
Mems_allowed:   00000000,00000001
Mems_allowed_list:      0
voluntary_ctxt_switches:        1040657
nonvoluntary_ctxt_switches:     2126
@pmenzel
Copy link
Collaborator

pmenzel commented Sep 14, 2020

root:eldersoftheinternet:~/# grep VmPeak /proc/$(pgrep upowerd)/status
VmPeak:  3409372 kB

killed it to prevent others to debug it. Funny enough elders is the only workstation with that much upowerd mem usage.

It could be your wireless mouse, which makes the difference.

I'd vote for removal, but anyway to prevent discussion just update sometime.

$ sousage.pl upower

# '/usr/lib/libupower-glib.so.1' dependencies:
# -----------------------------------------------------------------------------------------------
  /usr/bin/gnome-power-manager                           gnome-power-manager-3.0.0-1.x86_64
  /usr/bin/gnome-power-statistics                        gnome-power-manager-3.0.0-1.x86_64
  /usr/bin/gnome-session                                 gnome-session-3.4.1-2.x86_64
  /usr/bin/gnome-session-properties                      gnome-session-3.4.1-2.x86_64
  /usr/bin/gnome-session-quit                            gnome-session-3.4.1-2.x86_64
  /usr/bin/upower                                        upower-0.9.16-2.x86_64
  /usr/bin/xfsettingsd                                   xfce4-settings-4.14.0-0.x86_64
  /usr/lib/control-center-1/panels/libpower.so           gnome-control-center-3.0.0.1-1.x86_64
  /usr/lib/gdm/gdm-simple-greeter                        gdm-3.4.1-14.x86_64
  /usr/lib/gnome-settings-daemon-3.0/libpower.so         gnome-settings-daemon-3.4.1-0.x86_64
  /usr/lib/gnome-settings-daemon-3.0/libxrandr.so        gnome-settings-daemon-3.4.1-0.x86_64
  /usr/lib/gnome-settings-daemon/gnome-settings-daemon   gnome-settings-daemon-3.4.1-0.x86_64
  /usr/lib/xfce4/panel/plugins/libweather.so             xfce4-weather-plugin-0.8.10-0.x86_64
  /usr/libexec/upowerd                                   upower-0.9.16-2.x86_64
# 14 hit(s)

@wwwutz
Copy link
Collaborator Author

wwwutz commented Sep 14, 2020

14 hits.. well... I didn't say it's easy 8-)))))

anyway, you're right, might be the mouse triggering the mem-leak. bad mouse - no donut. 8-)

Sign in to join this conversation on GitHub.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants