#24826: LZMA-compressed consensus diffs stall Tor Browser launch for at least 20s or break it entirely --------------------------+------------------------------------ Reporter: gk | Owner: (none) Type: defect | Status: new Priority: Medium | Milestone: Tor: 0.3.3.x-final Component: Core Tor/Tor | Version: Severity: Normal | Resolution: Keywords: | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: --------------------------+------------------------------------
Comment (by cypherpunks): Replying to [comment:3 gk]: > Replying to [comment:2 cypherpunks]: > > 7.0.11 sometimes gives > > {{{ > > [01-09 05:25:15] Torbutton NOTE: Exception on control port [Exception... "Component returned failure code: 0x804b000e (NS_ERROR_NET_TIMEOUT) [nsIBinaryInputStream.readBytes]" nsresult: "0x804b000e (NS_ERROR_NET_TIMEOUT)" location: "JS frame :: chrome://torbutton/content/torbutton.js :: torbutton_socket_readline :: line 824" data: no] > > }}} > > on a slow Windows machine (didn't you forget to set the compression thread's priority below normal?). > > That's a different issue. There is no released Tor Browser that supports LZMA compression at the moment. Not so different as you think. Without LZMA it stalls for ~15 sec there and breaks Torbutton when more. And it's not funny that Tor periodically causes glitches in all other programs (check with 1 CPU VM). BTW, shouldn't Tor respond to Tor Launcher even when it's parsing diffs in the background? (Is timeout set to 15 sec as your logs show?) -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/24826#comment:4> 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