[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
The full log is the best I can offer unless I figure out how to
reproduce this (it hasn't even re-occurred randomly). If you skip the
first 50 lines and ignore the libinput errors, it's entirely errors
produced during or immediately after a freeze.
gnome-shell-extension-prefs shows the following
Please:
1. Attach only the portion of the log relating to the command in comment
#2 - while the freeze is occurring. You will need to start the command,
wait till the freeze happens, and then send us the most recent messages
only.
2. Provide 'top' output from a fresh session immediately after a f
>From top, just now (gnome-shell has not been freezing during this
session):
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
In logs I have going back 6 months the errors "Attempting to run a JS
callback during garbage collection." and "The offending callback was
..." only appear on one other date.
There is a similar message "Attempting to call back into JSAPI during
the sweeping phase of GC." that appears more frequent
** Attachment added: "GnomeShellNormalLog.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876946/+attachment/5367201/+files/GnomeShellNormalLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Please also run 'top' or 'ps auxw' and tell us how much memory the
gnome-shell processes are using.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876946
Title:
gnome-shell freezing with "Attempting
That log message is actually pretty common and probably not related to
any freezes. To confirm this please open a Terminal window and start
monitoring the log:
journalctl -f
Now please check to see if the messages correlate closely with the
freezes. And tell us if any of them appear when the fr