It happens four to five time a day, when going back to gitlab to check for MR or repository, doing a “/” search and entering 3 characters max inevitably makes tab crash.
Firefox stays up, some button still respond but most of become unresponsive (other firefox window seems unaffected).
I tried to debug with about:processes without success.
On a mac m2 pro, self-hosted gitlab v17.5.5 (non-container), firefox 141.0.3.
I have been seeing the same issue now for a couple weeks as well. This has been across a few versions of firefox now.
Mac M3 Pro, onprem v17.5.5-ee, firefox 142.0 (extensions: uBlock Origin, Firefox Multi-Account Containers [gitlab tabs not containerized])
Notes:
It doesn’t always occur immediately after an upgrade/restart of firefox, but usually starts up pretty quickly
Issue has been reproduced in private browser as well
Repro and troubleshooting:
Firefox doesn’t completely do 1:1 with tabs to processes/threads, so when the crash does occur, the entire process gets borked, which takes any other tabs using the same process with it, including non-gitlab tabs
about:processes shows the process that’s messed up, it hits 100% CPU usage and you can see the affected tabs. I’ve tried killing that process which leaves some of the other affected tabs in limbo as well.
The only way I’ve resolved affected tabs, after killing the affected process, find each tab with the circular spinning logo, right click “duplicate tab” which loads the page in a new/different process then I can kill the original “hung” tab.
I would suggest opening an issue here: Issues · GitLab.org / GitLab · GitLab since Gitlab devs don’t read forum posts, so to get it fixed would require opening an issue for it.