0

I found that whenever I leave my laptop idle for a while (no suspend because of Caffeine)it gets stuck and I need to force reboot the system by the power button. I tried disabling all the startup applications, disabling and even uninstalling the extensions which appear on syslog, etc. I enabled a system monitor extension and I found whenever I leave the system idle, RAM usage is getting higher until everything gets stuck. So, before I lose control of everything I used system monitor and found that Gnome-shell is using 2.3GB RAM! I restarted the shell (alt-F2 then r) and the RAM usage reduced down to 237MB. using tail -f /var/log/syslog gives me errors like this:

gnome-shell[4646]: #0   5572a9982f20 i resource:///org/gnome/shell/ui/dateMenu.js

and using pmap pgrep gnome-shell | grep -v -i deleted > /tmp/gnome-pmap1.dump will give me errors like this related to the calendar:

2057:   /usr/libexec/gnome-shell-calendar-server

Using memstat (mentioned here I found that the problem is mostly made by chrome_crashpad_handler and when I kill this process everything is fine. but I dont know how to disable or totally remove it, and I dont know what it is at all!

Before-after picture is attached.

P.S. Ubuntu 22.10, Gnome 43.1, X11, on a Dell thinkpad Inspiron 7348: 4GB RAM, Core i5 CPU, Intel Graphics

before restarting shell

after

1 Answers1

0

After disabling everything suspicious, I still had the issue but before getting ram usage too much that I can't check anything, I used tail -f /var/log/syslog and faced too many errors like this:

Feb 26 20:46:46 thinkpad-lap gnome-shell[2087]: #0   55c0fea1a048 i   resource:///org/gnome/shell/ui/dateMenu.js:370 (34058da3b830 @ 55)

Feb 26 20:46:45 thinkpad-lap gnome-shell[2087]: Object .Gjs_ui_dateMenu_EventsSection (0x55c0f7150cd0), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.

Feb 26 20:46:46 thinkpad-lap gnome-shell[2087]: == Stack trace for context 0x55c0f38d1190 ==

there was a lot of errors and things like these, so I started to search one by one, and found this bug and solution

after backing up my clock setting:

dbus-launch dconf dump / > gnome-desktop.dconf

I did reset all clocks settings with:

dbus-launch dconf reset -f /org/gnome/clocks/

dbus-launch dconf reset -f /org/gnome/shell/world-clocks/

and it relieved me of an old disgusting problem.