electionbettingodds.com - excessive CPU and RAM usage (Ryzen 7 5700U)
Categories
(Core :: Performance: General, defect)
Tracking
()
People
(Reporter: 08xjcec48, Unassigned)
Details
(Whiteboard: tech-evangelism)
Attachments
(2 files)
Steps to reproduce:
- Open https://electionbettingodds.com/President2024.html#chart
- Click on the different tabs on the chart (Maximum, Last Month, etc.)
Actual results:
Abnormally high CPU and RAM usage.
Comment 1•1 year ago
|
||
Can confirm.
Profile: https://share.firefox.dev/4b9jUQG
Time spent in layout and JS.
cc :dholbert and :jandem.
Updated•1 year ago
|
Comment 2•1 year ago
•
|
||
This is bad on Chrome too. Looks like a poorly designed website.
Comment 3•1 year ago
|
||
(In reply to Mayank Bansal from comment #1)
Can confirm.
Profile: https://share.firefox.dev/4b9jUQGTime spent in layout and JS.
cc :dholbert and :jandem.
Nothing really obvious stands out for the JS time. Mostly time in JIT code.
Comment 4•1 year ago
|
||
This bug was moved into the Performance component.
:08xjcec48, could you make sure the following information is on this bug?
✅ For slowness or high CPU usage, capture a profile with http://profiler.firefox.com/, upload it and share the link here.- For memory usage issues, capture a memory dump from
about:memoryand attach it to this bug. - Troubleshooting information: Go to
about:support, click "Copy raw data to clipboard", paste it into a file, save it, and attach the file here.
If the requested information is already in the bug, please confirm it is recent.
Thank you.
Comment 7•1 year ago
|
||
Thanks for attaching that info -- though, bugbot may have been a bit overzealous in requesting it in this case.
Given comment 2's observation about this affecting other browsers as well, I'm not sure it's worth spending too much time investigating this as a Firefox bug; it sounds like the site is just doing a lot of work (perhaps unnecessarily/inefficiently) behind the scenes.
Reporter, are you seeing other browsers handling this site substantially better than Firefox? If it's similarly bad everywhere, then your best bet would be to get in touch with the folks who run the site.
I thought this could be an issue affecting Firefox and my hardware specifically (and Mayank has a similar CPU), but I can reproduce this issue with Edge too.
Bug 1902867, on the other hand, only affects Firefox.
This has now been corrected (by reducing the number of data points in the chart.) Thank you!
Description
•