Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#36214 - [accountsservice] Leaking almost a gigabyte of memory
Attached to Project:
Arch Linux
Opened by Simonas (nagi) - Sunday, 21 July 2013, 10:47 GMT
Last edited by Jan de Groot (JGC) - Monday, 26 August 2013, 10:00 GMT
Opened by Simonas (nagi) - Sunday, 21 July 2013, 10:47 GMT
Last edited by Jan de Groot (JGC) - Monday, 26 August 2013, 10:00 GMT
|
DetailsDescription:
Accountsservice, at some point, starts leaking memory quite a lot. Currently it is using 847MB of memory after being `up 2 days, 4:26`. Additional info: * package version(s): 0.6.34-1 Steps to reproduce: No idea. I can, however, try to provide any information needed given you provide me the steps how to obtain it. I can tell what does seem to trigger the leak: * Opening/Closing a (gnome-)terminal (leaks a whooping 20MB of memory with every single terminal) * Changing from tty1 to any other tty (tty5 for example). |
This task depends upon
Closed by Jan de Groot (JGC)
Monday, 26 August 2013, 10:00 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in 0.6.34-2 by adding various memleak fixes from upstream.
Monday, 26 August 2013, 10:00 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in 0.6.34-2 by adding various memleak fixes from upstream.
Comment by Dave Reisner (falconindy) -
Sunday, 21 July 2013, 16:04 GMT
847M virtual or resident?
Comment by Simonas (nagi) -
Sunday, 21 July 2013, 18:54 GMT
Resident of course.
Comment by Jan de Groot (JGC) -
Tuesday, 23 July 2013, 10:20 GMT
I can confirm it's leaking memory. Upstream has a memleak fix in git, but that alone doesn't fix this.
Comment by Jan Alexander Steffens (heftig) -
Sunday, 11 August 2013, 18:58 GMT
Can't reproduce this myself.