One tab crashed and transformed the other tab to about:newtab with no history!

What a mess!

added component::applications/tor browser ff68-esr-will-have owner::tbb-team priority::medium resolution::fixed severity::normal sponsor::44-can status::closed tbb-crash type::defect labels

Trac:
Keywords: N/A deleted, tbb-crash added

Is that reproducible? If so, how? On which platform and version?

Trac:
Status: new to needs_information

Hah, indeed, that's reproducible by opening a lot of tabs with Trac tickets and killing child processes one by one on Windows 7.

Replying to cypherpunks:

Hah, indeed, that's reproducible by opening a lot of tabs with Trac tickets and killing child processes one by one on Windows 7.

What is lots here? 5? 10? And how are you killing those processes?

2 per child process at least. Kill by standard Task Manager.

Replying to cypherpunks:

2 per child process at least. Kill by standard Task Manager.

Can you reproduce that with a vanilla Firefox ESR 60, too? (See: https://www.mozilla.org/en-US/firefox/organizations/all/ and select the "Firefox 60" item there)

Yes, in PBM only, it seems.

Replying to cypherpunks:

Yes, in PBM only, it seems.

Interesting. How does Firefox 68 ESR do? (You get it under the "Firefox 68" column at the above URL)

Does good.

Good! So, we'll have this fixed once we transition to the new ESR. If you could help with figuring out what exactly fixed this bug we might be able to backport it. You could start by trying different releases between Firefox 60 and 68 to narrow the major version down and then getting the nightly that fixed it https://ftp.mozilla.org/pub/firefox/nightly/.

Trac:
Keywords: N/A deleted, ff68-esr-will-have added

Adding Sponsor 44 to ESR68 tickets

Trac:
Sponsor: N/A to Sponsor44-can

9.0a6, which is about to get built, is based on ESR 68, so closing.

Trac:
Resolution: N/A to fixed
Status: needs_information to closed

closed

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