[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #9531 [TorBrowserButton]: More Torbutton hangs on New Identity control port access

#9531: More Torbutton hangs on New Identity control port access
----------------------------------+---------------------------------------
     Reporter:  mikeperry         |      Owner:  mikeperry
         Type:  defect            |     Status:  new
     Priority:  major             |  Milestone:
    Component:  TorBrowserButton  |    Version:
   Resolution:                    |   Keywords:  tbb-usability, tbb-newnym
Actual Points:                    |  Parent ID:
       Points:                    |
----------------------------------+---------------------------------------

Comment (by gk):

 Replying to [comment:25 mcs]:
 > Does the deadlock still occur if we use buffered sockets?  The
 combination of blocking + unbuffered is unusual.  I don't remember why
 buffering causes problems, but Mike probably does.

 https://trac.torproject.org/projects/tor/ticket/8642#comment:1 ? It seems
 we get buffering for free if we have blocking sockets :) So, the comments
 in torbuttons.js are wrong. Well, they are not wrong but they just don't
 match reality.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9531#comment:26>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs