Open
Bug 1982245
Opened 6 months ago
Updated 5 months ago
Testcase querying a protected localhost N times takes 1 minute. Chrome throttles instantly.
Categories
(Core :: DOM: Networking, defect, P2)
Core
DOM: Networking
Tracking
()
NEW
People
(Reporter: mayankleoboy1, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged][necko-priority-next])
Attachments
(2 files)
Open testcase
Enter 50000
Click run
https://share.firefox.dev/3UmCJtO
Chrome throttles instantly. Maybe we should too?
Also look at the cc time near the end freeing history.
|
Reporter | |
Comment 1•6 months ago
|
||
|
|
Reporter | |
Comment 2•6 months ago
|
||
Gecko profile for N=5000: https://share.firefox.dev/4lkeYxm
|
||
Comment 3•6 months ago
|
||
Indeed, Chrome stops after 23 messages, and the following message is printed in the console:
Throttling navigation to prevent the browser from hanging. See https://crbug.com/1038223. Command line switch --disable-ipc-flooding-protection can be used to bypass the protection
I guess it would help to have a similar IPC flood protection here too.
Severity: -- → S3
Priority: -- → P2
See Also: → https://issues.chromium.org/issues/40113103
Whiteboard: [necko-triaged][necko-priority-new]
|
|
||
Updated•6 months ago
|
Whiteboard: [necko-triaged][necko-priority-new] → [necko-triaged][necko-priority-next]
You need to log in
before you can comment on or make changes to this bug.
Description
•