Open
Bug 1977138
Opened 3 months ago
Updated 3 months ago
Testcase creating and immediately deleting Async XHR is 23x slower in Firefox compared to Chrome
Categories
(Core :: Networking, defect, P2)
Core
Networking
Tracking
()
NEW
People
(Reporter: mayankleoboy1, Unassigned)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [necko-triaged][necko-priority-next])
Attachments
(1 file)
|
579 bytes,
text/html
|
Details |
Open testcase
Enter 500000
Click Run
Firefox: https://share.firefox.dev/4loJqHr (17s)
Firefox with networking preset logging: https://share.firefox.dev/4lxnbiW
Chrome: https://share.firefox.dev/40DR7l5 (750ms)
Testcase generated using chatgpt. Very artificial, so feel free to WONTFIX/INVALID.
Comment 1•3 months ago
|
||
Yes, we know that when creating tons of HTTP requests, we are not fast enough.
Blocks: necko-perf
Severity: -- → S3
Priority: -- → P2
Whiteboard: [necko-triaged][necko-priority-next]
| Reporter | ||
Comment 2•3 months ago
|
||
There is a testcase that stresses XHR (but in a different way) in bug 1944331. To me, they seemed different, and hence i created this separate bug. But feel free to dupe it over.
See Also: → 1944331
You need to log in
before you can comment on or make changes to this bug.
Description
•