Testcase generating N Async XHR is slower, uses far more memory, uses time on Parent-process, and the Socket Thread keep on using CPU ( and sometimes persists after closing Firefox)
Categories
(Core :: DOM: Networking, defect, P3)
Tracking
()
People
(Reporter: mayankleoboy1, Unassigned, NeedInfo)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
Attachments
(1 file)
|
2.46 KB,
text/html
|
Details |
Open attached testcase
Enter some number and press enter
N=10000
Nightly: https://share.firefox.dev/3WBkwua
Chrome: https://share.firefox.dev/3WE7Y5b (faster and uses far less memory)
Nightly to reload the page in background: https://share.firefox.dev/4jCyC8b
N=100000
Nightly: https://share.firefox.dev/4h9EILV (Partial because it rapidly used up all memory)
Chrome: Ran pretty well to completion.
We are slower, use far more memory, spend time in parent-process, the socket thread keep on using CPU for a long time, and one time the socket process persisted after I had quit firefox.
Disclaimer: I created teh testcase using chatgpt with the intention of highlighting potential hotspots and inefficiencies. I have no idea how real-work this usecase is. Feel free to WONTFIX/INVALID.
|
||
Updated•11 days ago
|
|
||
Comment 1•3 days ago
|
||
The severity field is not set for this bug.
:valentin, could you have a look please?
For more information, please visit BugBot documentation.
Description
•