enabling tor causes OBW to spawn connections when closing

[pony-montana]

Hi, the problem accour only with the "use tor connection" option enable (without setting any custom electrum server).

When I close the app the tor connections terminate, but after 1-2 seconds new connections spawns like if I'm starting the app.
They then remain in backgroung for long time, until android kills the process correlated. If I start OBW when these connections are running in background, it will uses them and no connections are killed or spawn during the startup and sync process (2 times over 3 it fails to fetch data and results "offline").
At this point if I close the app, the connections will be closed; after 1-2 seconds new tor connections will spawn and the cicle will goes on. ..
If I force-close OBW killing all the prcessess the cicle ends, connections are killed and no connections will start unless I decide to start the app.

When on clearnet (default servers), when I close OBW all the connections stop as expected and nothing strange spawn.

This different behaviour of tor and clearnet make me think that the problem is not related to my specific android-ui/launcher/process-killer, but could be something broken with handling tor connections.
I analized the internet traffic on-the-go with the app from fdroid "PCAPdroid", a useful and simple tool.

[pony-montana]

I found exactly the same behaviour on simple bitcoin wallet.

Retesting OBW and SBW under optimal network conditions I see that the failures on fetching data are less. They could not depend at all on the pre-spawn connections, and that could be something more like a feature than a bug (speculating, the intention could be to have some node preventively connected so to speedup sync on startup). Even if that was the intention I still dont like it.