Memory Leak in Bitbucket > PR > Files Changed

[Marc C_ S_]

Issue Summary

Opening a recently created Pull Request and navigating to Files changed triggers a severe client-side memory leak / runaway memory usage. In Google Chrome, this eventually causes the tab (and in my case the entire browser) to become unresponsive, impacting the whole desktop session (UI outside the browser also becomes sluggish/unresponsive).

Environment

• Browser: Chrome (version: 144.0.7559.110)
• OS: Windows 11
• PR size: 30+ changed files (likely relevant)

Steps to Reproduce

1. Open a recently created PR
2. Navigate to Files changed.
3. Scroll down through the file list/diffs.
   1. In my case, the issue consistently triggers around file ~15 (with 30+ files total).
4. Observe memory growth and eventual UI freeze.

Expected Result

• Scrolling through the PR diff should remain responsive.
• Browser memory usage should stabilize (no continuous growth).
• Chrome and the OS UI should remain usable.

Actual Result

• Memory usage increases continuously while viewing/scrolling Files changed.
• Chrome becomes unresponsive (tab freeze → browser freeze).
• System/UI responsiveness degrades significantly (including UI outside the browser window).
• Recovery typically requires closing the tab or force-quitting Chrome.

There is also a Content security Policy exeption, someone should add https://bbc-frontbucket-static.prod-east.frontend.public.atl-paas.net/ to the meta.

[Syahrul]

Hi Marc,

Welcome to the community.

Could you please raise a support ticket and include the URL of the affected pull request? This will help our team investigate and attempt to reproduce the issue, as I’m currently unable to do so on my end.

You can raise a ticket via our Support portal here: 

https://support.atlassian.com/contact/

Regards,
Syahrul