Issue Summary

When using Chrome 125, several Jira pages become unresponsive or crash "aw, snap!". The error code 5 may be present on the crash page message.
This only affects some instances.

We're still investigating this problem and will keep this Jira Issue updated. We're not certain the fix is on Chrome, on Jira or 3rd party software (apps, libraries, OS, etc), yet.

Atlassian hasn't been able to reproduce this yet — we're relying mostly on customers reports at this moment.
Other products are starting to report similar issues with Chrome 125 on the web.

This is likely related to a P1 bug affecting Chromium reported on https://issues.chromium.org/issues/341095522.

Steps to Reproduce

This issue's been reported with Chrome 125 (released mid May 2024) on some Jira pages.

Reported failing Chrome versions:

• 125.0.6422.0
• 125.0.6422.60
• 125.0.6422.61

1. Login to Jira on a new browser window
2. Open a Project page listing issues like:

   https://jira-base-url/projects/PKEY/issues?filter=allopenissues
   

1. The page should load alright the first time.
2. Reload the page one or two times and it'll crash.

Expected Results

Jira would behave on Chrome 125 as it did on Chrome 124 or Firefox.

Actual Results

• Some pages become unresponsive or break ("aw, snap!") after some time loading.
• Reverting to Chrome 124 works just fine.
• Other browsers like Firefox work just fine.
• Enabling Safe Mode doesn't fix the issue (didn't fix for a customer)

Workarounds

While the issue's investigated and no definitive fix is available (from Google, Atlassian or third parties involved):

• Revert to version 124 of Chrome
• Use other Browsers like Firefox, Safari or any non-Chromium
• Try Chrome 127 (Canary release)

Attempted workarounds:

• Disabling the module "com.atlassian.plugins.jquery:jquery-migrate" may delay the issue from happening, but customers reported it happened eventually (Admin > Manage apps > System filter > Search "jquery" > Expand "modules" > Disable "jQuery - Migration extensions").
• Starting Chrome with some Feature Flags disabled also delayed the issue, but customers reported it happened eventually, too:
  MacOS example Chrome startup command

  /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --js-flags="--no-js-regexp-duplicate-named-groups --no-js-regexp-modifiers"
  

  (from chromestatus.com/features milestone=125)

Other workarounds will be published here as we learn and confirm them.