[tor-bugs] #30162 [Applications/Tor Browser]: Tor Browser bootstrap process got stuck after interrupting it

[Tor Bug Tracker & Wiki]

#30162: Tor Browser bootstrap process got stuck after interrupting it
-------------------------------------------------+-------------------------
 Reporter:  gk                                   |          Owner:  tbb-
                                                 |  team
     Type:  defect                               |         Status:  new
 Priority:  Very High                            |      Milestone:
Component:  Applications/Tor Browser             |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  tbb-mobile, tbb-8.5-must,            |  Actual Points:
  TorBrowserTeam201904                           |
Parent ID:  #27609                               |         Points:
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------

Comment (by sisbell):

 I followed the steps to reproduce. It takes me about a dozen times of
 configuring a new bridge and reconnecting to see the problem but it does
 show up.

 pid 31900 is the currently starting (original) tor process. When I
 reconnected, I briefly see two new tor processes starting (not sure how we
 get two here): pid 32088 and 32092. Then a second later, those new
 processes die with the CookieAuth failure.


 {{{
 adb shell ps -ef | grep libTor
 u0_a236      31900     1 11 09:52:50 ?    00:00:18 libTor.so -f
 /data/user/0/org.torproject.torbrowser_alpha/app_torservice/torrc
 __OwningControllerProcess 31391
 u0_a236      32088 31391 2 09:55:41 ?     00:00:00 libTor.so -f
 /data/user/0/org.torproject.torbrowser_alpha/app_torservice/torrc
 __OwningControllerProcess 31391
 u0_a236      32091 32088 0 09:55:41 ?     00:00:00 [libTor.so]
 u0_a236      32092     1 0 09:55:41 ?     00:00:00 libTor.so -f
 /data/user/0/org.torproject.torbrowser_alpha/app_torservice/torrc
 __OwningControllerProcess 31391

 adb shell ps -ef | grep libTor
 u0_a236      31900     1 10 09:52:50 ?    00:00:18 libTor.so -f
 /data/user/0/org.torproject.torbrowser_alpha/app_torservice/torrc
 __OwningControllerProcess 31391
 }}}

 So we can see this is related to not cleaning up the existing tor process.
 I believe this can be handled as a check: before starting any tor process,
 cleanup old processes (either done in TOPL or tor-android-service).

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/30162#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online