[tor-bugs] #21312 [Obfuscation/Snowflake]: snowflake-client is pegged at 100% cpu

[Tor Bug Tracker & Wiki]

#21312: snowflake-client is pegged at 100% cpu
-----------------------------------+--------------------------
 Reporter:  arlolra                |          Owner:  arlolra
     Type:  defect                 |         Status:  assigned
 Priority:  High                   |      Milestone:
Component:  Obfuscation/Snowflake  |        Version:
 Severity:  Major                  |     Resolution:
 Keywords:                         |  Actual Points:
Parent ID:                         |         Points:
 Reviewer:                         |        Sponsor:
-----------------------------------+--------------------------

Comment (by dcf):

 Replying to [comment:26 cypherpunks]:
 > @dcf I'm seeing 80-120sec interruptions at times following your change
 (it's definitely noticeable), looking at the snowflake.log at around the
 intervals in which it happens I found this,

 @cypherpunks which change do you mean? The patches in comment:21 (go-
 webrtc), comment:22 (snowflake-client), and comment:24 (proxy-go) are by
 arlolra. If you mean comment:25, all I did was recompile with the patch
 from command:24 and deploy the public proxy-go instances.

 I too have noticed some occasional short delays, but I assumed they were
 because of the client closing connections after 30 seconds (#25429). Maybe
 I'm wrong, but your log line `No messages received for 30 seconds --
 closing stale connection.` is consistent with that assumption.

 If you know how to compile Go code, you could try changing
 `SnowflakeTimeout` in snowflake.go from `30` to `3600`, replacing
 Browser/TorBrowser/Tor/PluggableTransports/snowflake-client in your Tor
 Browser, and leaving a note at #25429 to say if it improved the situation.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21312#comment:27>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online