Open
Bug 1958712
Opened 4 months ago
Updated 13 days ago
Testcase generating N <META> elements is 20x slower than Chrome and does weird stuff in Compositor and SceneBuilder (PAPZCTreeManager::Msg_UpdateZoomConstraints)
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
NEW
| Performance Impact | ? |
People
(Reporter: mayankleoboy1, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
752 bytes,
text/html
|
Details |
N=500000
Chrome: https://share.firefox.dev/41ZoxeT (660ms)
Firefox: https://share.firefox.dev/4i9Y17n (13s)
|
Reporter | |
Updated•4 months ago
|
Summary: Testcase generating N <META> elements is 20x slower than Chrome and does weird stuff in Compositor and RenderBackend → Testcase generating N <META> elements is 20x slower than Chrome and does weird stuff in Compositor and RenderBackend (PAPZCTreeManager::Msg_UpdateZoomConstraints)
|
|
Reporter | |
Comment 1•4 months ago
•
|
||
N=5000000
Samply
Firefox: https://share.firefox.dev/3FRNNuP (130s)
Chrome: https://share.firefox.dev/4j35Z3q (8s)
(For whatever reason, Samply doesnt seem to capture the time spent in compositor and Scenebuilder.)
|
|
Reporter | |
Updated•4 months ago
|
Summary: Testcase generating N <META> elements is 20x slower than Chrome and does weird stuff in Compositor and RenderBackend (PAPZCTreeManager::Msg_UpdateZoomConstraints) → Testcase generating N <META> elements is 20x slower than Chrome and does weird stuff in Compositor and SceneBuilder (PAPZCTreeManager::Msg_UpdateZoomConstraints)
|
||
Comment 3•4 months ago
|
||
I think this is an S3, not that important given it's an extreme case.
I also set Performance Impact to ? so that the perf team can triage it as well.
Severity: -- → S3
Performance Impact: --- → ?
Flags: needinfo?(sefeng)
You need to log in
before you can comment on or make changes to this bug.
Description
•