Testcase querying CSS properties is 8x slower and takes 150x more memory cmpared to Chrome (N=5000)
Categories
(Core :: CSS Parsing and Computation, defect, P3)
Tracking
()
People
(Reporter: mayankleoboy1, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
Open testcase
N=5000
Firefox: https://share.firefox.dev/3YEyYSR (2.8s)
Chrome: https://share.firefox.dev/4j9Ygk6 (350ms)
Firefox to release memory: https://share.firefox.dev/4jiFkQo (1.7s)
Firefox takes ~3.2GB RAM whereas chrome only takes maybe 20MB.
Something to improve?
| Reporter | ||
Updated•8 months ago
|
Comment 1•8 months ago
|
||
If you change all: unset by any other property presumably things are more consistent across browsers? Chrome doesn't expand all (which causes correctness issues for them but is more efficient in this particular case).
| Reporter | ||
Comment 2•8 months ago
|
||
i replaced all:unset with appearance:none. Hopefully that is syntactically and logically correct.
The timings and memory use are much improved : https://share.firefox.dev/42ERR9E
Comment 3•8 months ago
|
||
Yeah, so that's expected then. Do you know how we compare to chrome on your machine with that test-case? If it's not meaningfully different I'd say this is all expected.
| Reporter | ||
Comment 4•8 months ago
|
||
N=5000
Chrome: https://share.firefox.dev/3YyYzwr (350ms)
Firefox: https://share.firefox.dev/42ERR9E (650ms)
Comment 5•8 months ago
|
||
Ok, so I can't see native chrome stacks there but there's something interesting and worth addressing which is the double hash when dealing with the inline stylesheet cache (of those two blue spots there, only the first should be needed).
Not the top priority to address but I'm looking at this code anyways for bug 1956486, so will keep it in mind.
| Reporter | ||
Updated•8 months ago
|
| Reporter | ||
Updated•8 months ago
|
| Reporter | ||
Comment 6•8 months ago
|
||
Profile with latest Nightly, N=5000: https://share.firefox.dev/3GxMphs
| Reporter | ||
Updated•5 months ago
|
Comment 7•1 month ago
|
||
The severity field is not set for this bug.
:emilio, could you have a look please?
For more information, please visit BugBot documentation.
Updated•1 month ago
|
| Reporter | ||
Comment 8•1 month ago
|
||
Testcase2 (without all:unset)
N=50000
Firefox: https://share.firefox.dev/4pCRQwI (7.5s)
Chrome: https://share.firefox.dev/3Y1oPit (3.5s)
Description
•