Entering invalid config info makes Orbot go into infinite loop

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]