GitLab

When configured to use only a single bridge, if the connection to that bridge is lost (which typically happen when suspending or hoping from one network to another), tor will not try to reconnect even when the bridge is reachable available again.

At notice level, you can see a loop of:

smartlist_choose_node_by_bandwidth(): Empty routerlist passed in to old node selection for rule weight as guard
should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
compute_weighted_bandwidths(): Empty routerlist passed in to consensus weight node selection for rule weight as guard

I don't think this happen when there is more than one bridge configure but I'm not 100% sure at this time.

I also have the feeling that this did not happen with version 0.2.3, but I'm not 100% sure either.