Gnome Freezing Shortly and becoming then sluggish after hitting activities

[Hanzel]

Thanks for the data so far, could you add the output of inxi -v7azy so users have a better Idea of the system you run and how it is configured.

The snippet you posted earlier is generated by gnome-shell that is good to know.

@Thomas_D

Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked

The issue looks like a problem with a extension to me, but the log in not clear enough to point to a specific one. One way to check what is causing the freeze/sluggishness is to disable extensions and try to recreate, that way, you can check if it is extension related.

Another way to check if extensions are the cause is to use the Projects/GnomeShell/LookingGlass - GNOME Wiki! to spy on what the extensions are doing and if there are errors reported.

Sharing large logfiles:

[HowTo] use public command-line pastebin services without installing anything!

Sometimes we might want to easily share terminal output. While this can be accomplished directly in the forums or manually through websites like pastebin, there also exist a number of open services that allow you to paste and share directly from the command line by using tools you already have installed. This is great for many situations, including troubleshooting from a non-graphical boot, or simply very large outputs. Here I will share a few examples and how to use them. Services and Exampl…

One more datapoint that is usefull:
Reboot & share the output of journalctl --boot --priority=3 (this should not be that large) will show errors in the current session. Since you mention having the same on Pop!_OS this might lead to a issue specific to your situation.