Comment 78 for bug 1959747

Revision history for this message
In , Vseerror-i (vseerror-i) wrote :

(In reply to Frank from Matrix and #68)
> I narrowed it down to a change between Thunderbird 110_0b4 and 111_0b1.

That's good work.

Bad news: the number of [Firefox](https://hg.mozilla.org/releases/mozilla-beta/pushloghtml?fromchange=FIREFOX_110_0b4_RELEASE&tochange=FIREFOX_111_0b1_RELEASE) and [Thunderbird](https://hg.mozilla.org/releases/comm-beta/pushloghtml?fromchange=THUNDERBIRD_110_0b4_RELEASE&tochange=THUNDERBIRD_111_0b1_RELEASE) patches in that span is massive.

Good news: 111.0b1 is the first beta with Supernova code. So there is a high chance the cause is Supernova code whose first daily build is 2023-01-16.

Bad news: I'm guessing the cause is straight up Supernova "ash" massive code landing on 2023-01-17. So you might try **nightly** builds on either side of 2023-01-17. If the problem is not seen there, use mozregression to try **nightly** builds between and 2023-02-27

(above comment edited to remove duplicate text)