Firefox freezes on "/" hotkey repository search with self-hosted gitlab

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Summary

Using self-hosted gitlab, if I have more than one tab open with gitlab in firefox and use the "/" hotkey to search with ~4 characters, the entire tab freezes

Steps to reproduce

  1. Navigate to a repository on a self-hosted gitlab instance
  2. Hit "/" and type in "this is a test" without hitting enter. Note that the tab does not freeze/crash
  3. Keeping the first tab open, duplicate the tab so that it's also open to a repository on the self-hosted gitlab
  4. Hit "/" and try to type in "this is a test". By completing the word "this", the tab will have become unresponsive. Going back to the first tab, trying to search there will now also result in that tab freezing up.

Example Project

This is not reproducible on the main gitlab, I only am able to reproduce on my company's self-hosted gitlab (currently on gitlab v17.5.5). However, it looks like others have run into the same issue (could not find any issue already reported).

What is the current bug behavior?

With more than one open tab on self-hosted gitlab, searching a repository freezes gitlab tab

What is the expected correct behavior?

Search should not freeze

Relevant logs and/or screenshots

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info 

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)


(we will only investigate if the tests are passing)

Possible fixes

Patch release information for backports

If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.

Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.

High-severity bug remediation

To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.

Edited by 🤖 GitLab Bot 🤖