turbotunnel-quic snowflake-client occasionally uses lots of CPU
As originally noted at comment:7:ticket:33211, the quic-go turbotunnel client sometimes uses 100+% CPU for a few minutes before returning to normal operation. It is specific to the quic-go implementation; it doesn't happen with the kcp-go implementation nor the non-turbotunnel client.
As best I can figure, the cause has something to do with timers created under (*session) maybeResetTimer.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information