Gnome Shell Crash about gnome-shell-extension-system-monitor HOT 5 OPEN

Hi @0b11001111,

Thanks for the feedback. As far as I know Fedora 36 includes Gnome Shell 42 which is the same version I've been using for a while without issues. I'm not saying this extension can't be the source of the crash, but it's very unlikely as there is no new feature being added or removed. (By the way an extension should not be able to crash the system in a better world.)

Do you see references to .js files in the crash report or the name [email protected]? If yes, you can copy-pate those lines here and I can take a look.
Otherwise you should try to reproduce the crash consistently in order to be able to debug it. But in that case I can't really help as I'm not a Gnome developer, so the best you can do is to submit a bug report with Gnome. If it turns out that the Fedora developers made customization to Gnome which makes it crash, then you might need to send a bug report to them too.

from gnome-shell-extension-system-monitor.

Thanks for the quick response. I filed the error report to Fedoras issue tracker but no reaction so far. In the attachment you'll find the log and a partial backtrace

• var_log_messages.txt
• backtrace.txt

from gnome-shell-extension-system-monitor.

It looks like something is consuming memory in the gnome-shell process without releasing unused memory. Maybe you can check this theory by opening the Gnome System Monitor app and filter for gnome-shell and watch the memory column for a minute or two. If you see it keeps growing, then this is the reason for the crash.

The backtrace.txt holds information about Gnome internals, so I don't have the knowledge to tell how it's connected to the extension.

There is a chance that a particular indicator does something wrong which causes this issue. If you are sure that this extension causes the problem you could do an experiment:

1. Open the Extensions app, find this one and click on settings.
2. There you can enable/disable indications individually.
3. Take half of them
4. If there is only one indicator left enabled, then you found the source of the issue.
5. Make them enabled only.
6. Wait until it's usually crash
7. If it crashed, take all currently enabled indicators, otherwise, take the other half. Continue with step 3.

from gnome-shell-extension-system-monitor.

Doing the binary search is actually pretty smart, assuming only one indicator is failing. I'll get back on this once I've tested it through

from gnome-shell-extension-system-monitor.

It seems to be the memory indicator!

EDIT: I double checked it and now I'm certain it's the memory indicator
EDIT: I observe the same issue with the CPU indicator, too

from gnome-shell-extension-system-monitor.