Arch Linux

Please read this before reporting a bug:

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#50589 - [gnome-online-accounts] goa-daemon takes huge amounts of memory

Attached to Project: Arch Linux
Opened by Johannes Rohr (jro) - Tuesday, 30 August 2016, 15:26 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 06 May 2017, 15:07 GMT
Task Type Bug Report
Category Packages: Extra
Status Assigned   Reopened
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 4
Private No


Description: goa-daemon takes huge amounts of memory, rendering system unresponsive. This is about a dell Latitude with 7.68 Gig of RAM and 8.00 Gigs swap partition. According to htop, goa-daemon consumes 31.3 % of the system memory. The system uses almost 3 gigs of the swap space. Running applications include the Gnome desktop, Evolution, Thunderbird, Owncloud-client, dropbox and Skype. The system feels so unresponsive because it is busy swapping all the time.

Additional info:
* package version(s) 3.20.30-2
* config and/or log files etc.

Steps to reproduce:

install GNOME
set up some online accounts (Google, ownCloud etc)
lauch evolution
see memory usage in htop or another tool
This task depends upon

Comment by Johannes Rohr (jro) - Sunday, 04 September 2016, 14:28 GMT
  • Field changed: Percent Complete (100% → 0%)
I again see goa-daemon using an absolutely insane amount of memory: 38.2 % or 2.9 GB.
Comment by Doug Newgard (Scimmia) - Saturday, 29 October 2016, 15:12 GMT
Still an issue?
Comment by Johannes Rohr (jro) - Saturday, 29 October 2016, 15:18 GMT
no, seems to be ok at the moment
Comment by Doug Newgard (Scimmia) - Saturday, 29 October 2016, 15:28 GMT
Great, I'll close this then. Sorry the ticket fell through the cracks, I somehow failed to reassign it when I reopened it :(
Comment by killmaster (killmaster) - Saturday, 06 May 2017, 15:07 GMT
Started happening again.
Comment by mattia (nTia89) - Sunday, 27 February 2022, 11:17 GMT
I cannot reproduce the issue. Is it still valid for you?