simple-tab-groups VS profiler

The older release is still available on that page, but presumably with different features. Development looks very active here: https://github.com/Drive4ik/simple-tab-groups/tree/master/plugins/stg-plugin-group-notes

Please use this page to report issues with Simple Tab Groups.

You can use this page to ask questions or submit your feedback about Simple Tab Groups.

Please open this page and click on New issue to contact the people who created Simple Tab Groups.

Are there reasons that the "Simple Tab Groups" extension isn't suitable for you? It seems to be well-maintained, cleverly uses Firefox's "hide tabs" API to keep a single window behind-the-scenes, and has integration with lots of other features like Firefox's containers. I think it's an indirect descendent of the old Tab Groups extension when it was spun out of Firefox.

https://github.com/drive4ik/simple-tab-groups

Just use Simple Tab Groups honestly

I assume that the speed is partly a consequence of not integrating with the context menu items of other extensions and of Firefox. See for example the discussions at and around https://github.com/Drive4ik/simple-tab-groups/issues/749#issuecomment-783171538

tab grouping extensions that do not misuse Firefox containers were developed, however in the absence of a tab groups API, conflicts are inevitable

Probably your best bet is to use the Firefox Profiler once it starts hogging the CPU to try to see what it's doing. I'd be happy to take a look at the result although I don't have a lot of experience at diagnosing performance problems; hopefully the profile will make it obvious what's going on.

I tried using the https://profiler.firefox.com/ and running with:

You can try to reproduce while taking a profile using the Firefox profiler, then share it in the #perf:mozilla.org room on Mozilla's Matrix instance.

Run a profiling session for ~30 sec when you notice something is running slower than you expect, see https://profiler.firefox.com/. Share results here if you want help interpreting them.

Next time, send a SIGABRT to the main process (kill -6 $(pidof firefox)) and use the resulting backtrace (you will find a link to the crash report in about:crashes) to file a bug. A performance profile could be useful, but you'll need to know first what to capture. This seems like a graphics issue, so try the Graphics preset. Share a link to your report.

https://profiler.firefox.com will be useful if you can capture and share it to developers.

If you can reproduce it in safe mode and a clean profile, capture a performance profile using the clean profile while trying to load a problematic webpage, don't remove any information from it, and share it here (although it's typically not easy for users to analyse them), or file a bug with it attached.

Next time, capture a performance profile using the Graphics preset, and kill the browser by entering kill -6 $(pidof firefox) in a shell. This will create a bug report (unless debian disables the crash reporter) that would indicate where Firefox is stuck at. You might need to use an official build to get useful results.