Opened 8 days ago

Last modified 8 days ago

#30162 new defect

Tor Browser bootstrap process got stuck after interrupting it

Reported by: gk Owned by: tbb-team
Priority: Very High Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: tbb-mobile, tbb-8.5-must, TorBrowserTeam201904
Cc: igt0, sisbell, sysrqb, hans@…, n8fr8 Actual Points:
Parent ID: #27609 Points:
Reviewer: Sponsor:

Description

I am still trying to figure out good steps to reproduce that bug but if you click on the gear icon and configure bridges then during bootstrap click again and change them or get back to start without bridges then you end up with a broken bootstrap process saying:

SUCCESS connected to Tor control port.
Cookie Auth file not created
Unable to start Tor: java.io.Exception: Cookie Auth file not created: /data/user/0/org.torproject.torbrowser_alpha/app_torservice/lib/tor/control_auth_cookie, len = 0

There is usually no way to recover from that and one has to start over again by kiling the app.

That's with the TOPL changes landed.

Child Tickets

Change History (3)

comment:1 Changed 8 days ago by gk

Priority: HighVery High
Summary: Tor Browser bootsrap process got stuck after changing bridges sometimesTor Browser bootsrap process got stuck after interrupting it

Okay, here are steps that work for me:

1) Open TBA and tap the start button
2) In the log see the SUCCESS connected to Tor control port. line and tap the gear icon
3) Don't configure anything but go back to the bootstrap panel and start again.
4) You get the exception and bootstrap is broken

comment:2 Changed 8 days ago by gk

Summary: Tor Browser bootsrap process got stuck after interrupting itTor Browser bootstrap process got stuck after interrupting it

comment:3 Changed 8 days ago by sisbell

I've seen this message before when running the Java Tor client. It occurs (100% reproducible) when there is an existing tor control connection already running. I didn't think this condition would occur on Android.

First, I'll verify we aren't somehow starting Tor twice.

Second, I'll look into if old processes aren't getting cleaned up. In this case, we can takeownership and it should clean up automatically when the Android app closes. I have an open issue for this:

https://github.com/thaliproject/Tor_Onion_Proxy_Library/issues/59

Note: See TracTickets for help on using tickets.