-
Notifications
You must be signed in to change notification settings - Fork 29
Open
Labels
env:browserkind/bugA bug in existing code (including security flaws)A bug in existing code (including security flaws)need/triageNeeds initial labeling and prioritizationNeeds initial labeling and prioritization
Description
Ref. https://bugs.chromium.org/p/chromium/issues/detail?id=1473980
What steps will reproduce the problem?
- Visit https://helia-identify.on.fleek.co/
- Open the console
- Wait a minute or two
What is the expected result?
- No uncatchable WebTransport errors or warnings should appear in the console
- 👉 We should be able to detect when we have too many pending WebTransport sessions and close them
- 👉 We should be able to recover from this state and begin opening WebTransport sessions again
What happens instead?
A warning appears in the console: WebTransport session establishment failed. Too many pending WebTransport sessions (64)
All subsequent attempts to open a WebTransport session on any server fail with "WebTransportError: Connection lost"
Timeline
- 2024-Q2
- Prototyping the origin's hashmap as the first mitigation issue
- Implementation of strategy pattern, under a runtime flag
- Implementation of a MVP and asked Google engineers for an early review
- Prototyping the origin's hashmap as the first mitigation issue
SgtPooki
Metadata
Metadata
Assignees
Labels
env:browserkind/bugA bug in existing code (including security flaws)A bug in existing code (including security flaws)need/triageNeeds initial labeling and prioritizationNeeds initial labeling and prioritization