web-bugs
web-bugs copied to clipboard
webcompat
www.cineworld.co.uk - see bug description
URL: https://www.cineworld.co.uk
Browser / Version: Firefox 104.0 Operating System: Windows 10 Tested Another Browser: Yes Chrome
Problem type: Something else Description: Runaway memory usage on seat picker page, eventually causing unresponsive browser. Steps to Reproduce: Pick a cinema, pick a film, add a couple of tickets, click Confirm, leave the seat picker page open for 10 minutes or so. Memory usage increases quickly (about 1GB after 10 minutes) and the browser becomes unresponsive. Chrome shows the increasing memory usage as well but the browser remains responsive.
Browser Configuration
- None
From webcompat.com with ❤️
@matthewkogan We appreciate your report. I was not able to reproduce the issue. I can see an increase in memory usage, but the browser did not crash. Chrome exhibits the same behaviour.
Does the issue reproduce on Firefox Nightly as well?
Tested with:
Browser / Version: Firefox Release 104.0 (64-bit)/ Chrome Version Version 105.0.5195.102 (Official Build) (64-bit) / Operating System: Windows 10 PRO x64
Suggestion: Try clearing cache/data/cookies, disabling add-ons and Ad-blocker (if available) and extensions or use a clean profile, and check again? If there are any changes made to the default settings of the browser (e.g. in about:config) please revert to the default settings and try again. Also, have the required cookies been accepted for this page?
[qa_36/2022]
Yes, I can reproduce it in a brand new installation of Firefox Nightly with no extensions installed. The unresponsiveness starts when the content process memory usage gets to about 4.5GB and the main process is at about 500MB. It's not a crash - just long periods of unresponsiveness. Also FYI my system is not out of memory.
@matthewkogan Can you please submit a performance profiole here? Please submit a performance profile following these steps (https://firefox-source-docs.mozilla.org/performance/reporting_a_performance_problem.html and https://profiler.firefox.com/docs/#/ ) by commenting here with the attached profile
[inv_36/2022]
@matthewkogan That is great. @wisniewskit Any info we can use from this?
[inv_36/2022]
@matthewkogan Does the issue reproduces for you on the latest build of Firefox Nightly?
[inv_41/2022]
It seemed a bit better today. Here's the new performance profile: https://share.firefox.dev/3VwhIMo
Thanks for the profile! I do indeed see the web page using a steadily increasing amount of memory in that profile, with a lot of time being spent trying to reclaim that memory (with incremental garage collection).
To try to confirm what's using the memory, I re-ran a profile with advanced settings to determine retained RAM usage via the settings "JS allocations" and "native allocations" options: https://share.firefox.dev/3g6TxUI
(For the very curious, I waited for a few minutes on the seat picker for two adult seats for Lyle, Lyle Crocodile in Brackneil, using a VPN).
It looks like a minified JS function in their scripts called En is calling setInterval, and that's somehow eating up RAM forever. Unfortunately I think we'll need to actually investigate that function closer to find out more (it's in the script at https://experience.cineworld.co.uk/js/site.js?v=202210142148:53:112530, access to which requires a VPN connection).
@wisniewskit Any updates on the issue? Is it still reproducible?
[inv_03/2023]
@matthewkogan Does the issue still reproduces on the latest Nightly version?
[inv_31/2023]
Yes; memory usage took off like a rocket. https://share.firefox.dev/3OCTgHQ
@matthewkogan Does is still reproduce on the latest Nightly?
[inv_19/2024]