Tor Browser sets different Guard for one of the tabs when goes crazy

New tabs show nothing (old bug). Some previously opened tabs show default Guard in France, after refresh too, after new circuit - nothing. But when new tab was opened from previously opened tab by 'Search Disconnect for', it lags a lot to connect and then shows Guard in Russian Federation! What’s going on here?

added component::applications/tor browser owner::tbb-team priority::medium resolution::not a bug severity::normal status::closed type::defect labels

Browser Console confirms Guard reselection! Ordinary tabs continue to use the default Guard. 'Open in a New Tab' for the video and etc leads to the same behavior sometimes.

Trac:
Priority: Medium to Very High
Summary: Circuit visualizer shows different Guard for one tab! to Circuit visualizer shows different Guard for one of the tabs!
Severity: Major to Critical

I could not reproduce this using "context menu > Search Disconnect for ...".

What's this video you talk about?

Is this a personal american spam or what?

Takes part in ticket:18080#comment:14.

Trac:
Summary: Circuit visualizer shows different Guard for one of the tabs! to Tor Browser sets different Guard for one of the tabs when goes crazy

Right now I'm observing two tabs with separate guard for each on TBB 7.0a3. "New Tor Circuit for this Site" changes circuits as usual, preserving guards on both tabs.

Wow, what made this ticket attract so many spammers? :)

Replying to cypherpunks:

Wow, what made this ticket attract so many spammers? :)

I deleted all the spam comments and hope they won't come back and spam again. ;)

It's normal for tor to use more than one guard in some circumstances, particularly if the connection to one of the primary guards is unreliable.

I don't think this is even a bug.

Trac:
Severity: Critical to Normal
Priority: Very High to Medium

Replying to teor:

It's normal for tor to use more than one guard in some circumstances, particularly if the connection to one of the primary guards is unreliable.

I don't think this is even a bug.

I agree.

Trac:
Status: new to closed
Resolution: N/A to not a bug

closed

mentioned in issue #24038 (moved)

moved to tpo/applications/tor-browser#18222 (closed)