You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The memory allocated to the gnome shell process grows to 1-2 GB after a full days use with gsconnect extension enabled. The CPU also spikes and makes the system freeze for a few seconds. This doesn't happen when the gsconnect extension is disabled.
It's already reported on #1028 but none of the devs have managed to reproduce and we haven't been able to get it fixed. I'll definitely look closely on your findings on g.g.o as soon as I have time
Couldn't make much out of it. Could you also try to move your .cache/gsconnect directory to a safe backup spot and see if you could narrow down what is needed for reproducing the issue? In the g.g.o syscap there was an indication that the GSConnect daemon was forking a couple of processes before the hangup, but I don't think it included any information about what the other processes were. More information is needed, but unfortunately I don't have a clear idea what it could be exactly.
Describe the bug
The memory allocated to the gnome shell process grows to 1-2 GB after a full days use with gsconnect extension enabled. The CPU also spikes and makes the system freeze for a few seconds. This doesn't happen when the gsconnect extension is disabled.
Support Log
I'm not able to upload sysprof file here but it is available here https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4430.
System Details (please complete the following information):
The text was updated successfully, but these errors were encountered: