-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[20.04] pop-os gnome-shell[2613]: == Stack trace for context 0x5557b1f8c900 == #28
Comments
Found exactly the same issue last week on 22.04, gnome-shell 42.3.1.
And here I found a similar error. |
@0x3b0 If you're on 22.04, then it's probably not the same issue. The OP's logs here don't include anything about garbage collection. A fix for a garbage collection issue (pop-os/shell#1572) was just merged yesterday (pop-os/shell#1573) and released yesterday afternoon. Can you confirm you installed the latest update to version feaf0e3 (you can check with |
@jacobgkau It happened on version 30bf682. Yesterday's commit probably fixed it. Thanks. |
I'm going to close this issue as stale since 20.04 is no longer being actively developed, and since similar issues have been fixed in the meantime. If anyone still has issues on the current version, you're welcome to open a new issue. |
I am having "Attempting to run a JS callback during garbage collection" and then the system blocks with "pop-os gnome-shell[2314]: == Stack trace for context 0x642356bb5170 ==". I have to force shutdown each time. I am on Pop!_OS 22.04 LTS. Can you reopen this Issue ? |
Hi there,
not sure if this is the right place to report it but with an upgrade from POP 19.10 to POP 20.04 I am experiencing frequent blocks of the system because an high CPU usage of
systemd-journald
andgnome-shell
, when if you runjournald -xe
you read a thousand of this:pop-os gnome-shell[2613]: == Stack trace for context 0x5557b1f8c900 ==
The only way to unfreeze POP is to enter in console mode run this:
sudo systemctl stop systemd-journald*
and thensudo killall gnome-shell
several times until POP comes back responsive.This is the full log:
The text was updated successfully, but these errors were encountered: