#32576: Fix race condition in snowflake broker -------------------------------------+------------------------------ Reporter: cohosh | Owner: cohosh Type: defect | Status: needs_review Priority: Very High | Milestone: Component: Circumvention/Snowflake | Version: Severity: Normal | Resolution: Keywords: metrics | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: Sponsor28 -------------------------------------+------------------------------
Comment (by cohosh): Replying to [comment:7 dcf]: > Perhaps because the old broker had 1 CPU core and the new one has 2 CPU cores? I can imagine that might affect goroutine scheduling which might affect the visibility of race conditions. Ah that would do it :) The reason we didn't notice then was because clients and proxies weren't around to trigger the race until we switched over the DNS records for the bamsoftware.com domains. > > You might try setting `GOMAXPROCS=1` in /etc/service/snowflake- broker/run as a temporary workaround, if indeed it helps. Okay I did this and restarted the broker as of `2019/11/22 22:50:27` that should work until we get this patch reviewed. Thanks! -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/32576#comment:9> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs