Janking when browsing multiple pages including tradingview.com
Categories
(Core :: Graphics: Canvas2D, defect)
Tracking
()
Performance Impact | ? |
People
(Reporter: yoasif, Unassigned)
Details
Attachments
(1 file)
31.26 KB,
text/plain
|
Details |
From https://www.reddit.com/r/firefox/comments/ozutze/heavy_js_freezing_the_ui/
Basic information
Steps to Reproduce:
Websites with heavy js are able to freeze the firefox interface, including tab switching
it happens frequently when I am on a different tab for a while and then try to switch to tradingview tab.
Expected Results:
No janking.
Actual Results:
The browser UI freezes for about 10seconds and then the tab appears
the entire browser became white for a while, like it does when it loads from pagefile instead of memory
More information
Profile URL:
https://share.firefox.dev/3jxIFgF
https://share.firefox.dev/3s14Kbk
Basic systems configuration:
OS version: Windows 10
GPU model: NVIDIA GeForce RTX 3080
Number of cores: 6
Amount of memory (RAM): 16GB
Thanks so much for your help.
Reporter | ||
Comment 1•3 years ago
|
||
Comment 2•3 years ago
•
|
||
The original profile has most time spent in Canvas
I played with the charts - zoomed in and out and dragged the chart area. My profile shows some time spent in Baseline for a few functins.
https://share.firefox.dev/3yB37n1
Iain, is there anything that can be improved here?
Comment 3•3 years ago
|
||
The original profiles show 20 second long composites. Example: https://share.firefox.dev/3ixMQtJ
It seems like there are one or two textures that are deadlocked on, where we only make progress once both the Renderer and the content have timed out from their 10 second timeout.
For example, the Renderer blocks in RenderDXGITextureHost::LockInternal()
, which calls mKeyedMutex->AcquireSync(0, 10000)
.
Updated•3 years ago
|
Comment 4•3 years ago
|
||
This looks very similar to bug 1717209.
Asif - can you re-test this please once Fx91 is released tomorrow (or maybe now in Beta).
Reporter | ||
Comment 5•3 years ago
|
||
Bob, user says Firefox 91 resolves the issue.
Comment 6•3 years ago
|
||
(In reply to Asif Youssuff from comment #5)
Bob, user says Firefox 91 resolves the issue.
Great, thanks for following-up on this.
Updated•3 years ago
|
Description
•