[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:30 mikeperry]:
> We went with blocking sockets because New Identity needed to ensure that
it actually got a new circuit before allowing the user to do anything else
with the browser.
>
> I am wondering if we should try clearing the event queue as cypherpunks
suggested. It may be a good idea for a few reasons. We may be able to use
https://developer.mozilla.org/en-
US/docs/Mozilla/Tech/XPCOM/Reference/Interface/nsIDOMWindowUtils#suppressEventHandling%28%29
to suppress UI events in the meantime, if need be.
Yes, sounds reasonable. Alas, this idea is not working for the hang during
start-up. There a blank Tor Launcher window is visible for a short amount
of time until the usual messages appear giving a weird user experience. So
I wonder whether we should separate the two problems and treat them
differently: fixing the hang on New Identity with the
processNextEvent/suppressEventHandling idea and trying the other one for
the hang during start-up.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9531#comment:32>
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