Opened 10 years ago

Closed 9 years ago

#1286 closed defect (fixed)

Entering invalid config info makes Orbot go into infinite loop

Reported by: Sebastian Owned by: n8fr8
Priority: Low Milestone:
Component: Applications/Orbot Version: 1.0
Severity: Keywords:
Cc: Sebastian, gouki Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by ioerror)

When Tor dies due to a config error, orbot tries to start it repeatedly. It doesn't
realize that Tor will never start, and it'll just spam the log with "starting Tor. waiting"
messages.

This loop is not interrupted by clicking the symbol again, even though the symbol
goes grey. Orbot keeps trying to start Tor and spamming the log.

The only way to get out of this mess seems to be force-stopping the orbot
application or killing the service.

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (2)

comment:1 Changed 9 years ago by ioerror

Description: modified (diff)

It seems reasonable to check the return code from Tor or simply that Tor has returned right away.

comment:2 Changed 9 years ago by n8fr8

Resolution: Nonefixed
Status: assignedclosed

The exit code from Tor is now checked, and Orbot will report the error and not be allowed to start. The infinite loop issue should not occur anymore, as well.

Note: See TracTickets for help on using tickets.