regular hard lockups in display

[bfallik]

Hi,

Several days ago I installed this extension and it resulted in frequent hard lockups of my display. The kernel was still responsive and I could SSH into the machine to restart gnome-shell, but the frequent freezes made the system unusable for my regular use so I had to remove it.

I opened a downstream ticket in Fedora. Initially I suspected this was a regression from a recent OS package update but someone suggested I try disabling any new Gnome extensions. Once I removed System Monitor the lockup went away.

The only notable lines from the log were:

Jan 21 10:05:29 widow gnome-shell[1953]: == Stack trace for context 0x559f7c642320 ==
Jan 21 10:05:29 widow gnome-shell[1953]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.

The ticket contains more details that might be of interest.

Let me know if I can provide more details to help with debugging. I found System Monitor very useful for the few days I was using it and would love to re-enable it without the lockups.

Thx, brian

[elvetemedve]

Hi @bfallik,

Thanks for the feedback.

Regarding the quoted warning from the log, I'm not sure if it's caused by this extension as I don't see a single instance of that on my machine (at least under Gnome 43.2).

It would help a lot if you could narrow down which usage indicator caused this issue. If you open up the settings of the extension, you can turn off them separately. Other users reported problems with the swap indicator, so I would start with that.

[elvetemedve]

Hi @bfallik

I've made an improvement on that. The UI lag seems to be gone after the fix. Would you mind testing it? Replace the contents of ~/.local/share/gnome-shell/extensions/System_Monitor@bghome.gmail.com with the attached zip file: System_Monitor@bghome.gmail.com-pre-release.zip

[bfallik]

Hi @elvetemedve

Sure, I'm tryout out the new build now. When I was last testing this extension the lockups happened quickly, within a few days, so I should know soon enough if this resolves the issue.

Is there a way to know for certain that I'm using the extension from the zipfile? I've copied the files from the zip into ~/.local/... already but wasn't sure if there was a way to see exactly what Gnome Shell thinks it's running.

Best, brian

[elvetemedve]

Hi,

Great, thank you. Just make sure you log out and log in again after extracting the new version. Or if you are on an Xorg session you can reload the Shell by pressing Alt+F2 then type r and press enter. That's it.

[bfallik]

hi @elvetemedve , been using SystemMonitor for 5 days now without lockup so it seems to me that bug has been addressed in the dev build you shared above. Previously my system would lock 2-3 times per day.

Assuming you release a new version with these fixes, do I need to do anything to switch back to the normal release stream? Right now I'm using the manually installed build from the zip archive. Will Gnome just upgrade me when there's a newer upstream?

Thx, brian

[elvetemedve]

Hi @bfallik,

That's great news. Thank you for your help. I will publish it as a new release soon.

No action needed, you can keep the dev version. Gnome will notify you about the new release, so you can do the upgrade as usual, but it will be functionally identical to the dev version.