Opened 3 months ago

Last modified 2 months ago

#31278 new defect

Chrome proxies hang with open idle connection

Reported by: cypherpunks Owned by:
Priority: Medium Milestone:
Component: Circumvention/Snowflake Version:
Severity: Normal Keywords: snowflake-webextension
Cc: arlolra, cohosh, phw, dcf Actual Points:
Parent ID: Points: 2
Reviewer: Sponsor:

Description

Using Chrome 75.0.3770.142 on Windows, with addon 0.0.7 and the latest static page at https://snowflake.torproject.org/snowflake that was committed 2019-07-27. Started Chrome, enabled addon, and opened 3 tabs with the static page. The addon and all 3 tabs all established good client connections within an hour or two, exchanged data both directions for a while, and then stalled out with the client connection staying open, preventing serving any other clients.

All 4 client connections have been stuck in this state for 2 days now, with the addon just showing 1 connected and 0 in the past 24 hours, never changing, and the 3 tabs all just repeating "websocket --> WebRTC data: 543 bytes" every couple minutes with no transfer size change or any data flowing in the other direction. The 3 tabs show connections to clients at different IP addresses, so I don't think it's just a user leaving their client window open forever.

A similar test on Firefox with the same deployment date shows more expected behavior of a few clients served each day per tab or addon, with connections being closed after transferring data for a while and then later serving another client (so the dropped broker connection bug seems fixed there).

Child Tickets

Change History (2)

comment:1 Changed 2 months ago by dcf

There's a new ticket at https://github.com/keroserene/go-webrtc/issues/107 that has to do with Chrome.

According https://bugs.chromium.org/p/webrtc/issues/detail?id=9484 new versions of Chrome are sending new offer format and answer cannot be generated.

For example, for RemoteDescription with info

m=application 54111 UDP/DTLS/SCTP webrtc-datachannel a=sctp-port:5000

pc.CreateAnswer does not produce any result - no error, no answer

Similiar issue for node implementation - node-webrtc/node-webrtc#483

comment:2 Changed 2 months ago by cohosh

Points: 2
Note: See TracTickets for help on using tickets.