1998332 - Crash in [@ mozilla::dom::ThreadSafeWorkerRef::Private ] when opening Instagram

Status: RESOLVED FIXED

(Core :: DOM: Workers, defect)

Description

[Francesco Lodolo [:flod]]

This morning (20251104214230, macOS 26.0.1 (25A362)) I'm seeing consistent crashes when trying to open Instagram. Not sure if it's relevant, but I'm using Facebook Container, so Instagram is in a container tab.

I haven't seen crashes before, the previous app was 20251104095417

File in this component based on bug 1837736

Comment 1

[Sören Hentzschel]

Not sure if it's relevant, but I'm using Facebook Container, so Instagram is in a container tab

It happens in non-container tabs as well.

Comment 2

[Francesco Lodolo [:flod]]

mozregression gives me https://hg-edge.mozilla.org/integration/autoland/pushloghtml?fromchange=2a2054735049d03ad335768c5e40ccf829b361ec&tochange=53e6b7106a63749468b2716bc59d32344de513ea

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

:RyanVM, since you are the author of the regressor, bug 1998070, could you take a look? Also, could you set the severity field?

For more information, please visit BugBot documentation.

Comment 4

[Paul Oiegas [:poiegas], PM for Ecosystem QA (OMC, New Tab, Contextual, Nimbus, Experiments), Services QA (VPN, FxA/Subplat, Relay, Monitor), WebCompat QA, and Solo QA teams)]

Happens to me also on Nightly 146.0a1 (2025-11-04) on Facebook, I'm also using FB Container, but it might not be related as mentioned above. Same crash signature in about:crashes.

Comment 5

[Emilio Cobos Álvarez [:emilio]]

I think that regression range must be wrong, there's also a bunch of windows crashes...

Comment 6

[Emilio Cobos Álvarez [:emilio]]

And the code that is crashing just landed in bug 1360870...

Comment 7

[Emilio Cobos Álvarez [:emilio]]

Flod, I'm ~99% sure at this point that the SDK update is not the culprit but if you could double-check locally it'd be great.

Comment 8

[Francesco Lodolo [:flod]]

You're correct (sorry Ryan). I have no clue why the SDK one showed up the first time, considering that I'm using the same profile for mozregression.

New range: https://hg-edge.mozilla.org/integration/autoland/pushloghtml?fromchange=861ffe17791585147d78dcbf64ac4e4adceddd27&tochange=ac46df43805a50507a34b3455ec307bbfbb21629

Comment 9

[BugBot [:suhaib / :marco/ :calixte]]

Set release status flags based on info from the regressing bug 1360870

Comment 10

[BugBot [:suhaib / :marco/ :calixte]]

The bug is marked as blocking firefox146 (nightly). We have limited time to fix this, the soft freeze is in a day. However, the bug still isn't assigned.

:slloyd, could you please find an assignee for this tracked bug? Given that it is a regression and we know the cause, we could also simply backout the regressor. If you disagree with the tracking decision, please talk with the release managers.

For more information, please visit BugBot documentation.

Comment 11

[Sam Lloyd [:slloyd]]

Have flagged this to the relevant developer on my team

Comment 12

[Pascal Chevrel (relman team) -> :pascalc]

Removing the "blocking" status for 146 as it was fixed by backout.

Comment 13

[Harveer Singh]

Yes, seems that this has been caused by my recent push. I am on it. Apologies for the trouble and thank you for narrowing it down to the commit.

Comment 14

[Emilio Cobos Álvarez [:emilio]]

We can close this as fixed by backout :)

Comment 15

[Ciprian Georgiu, Desktop QA]

Francesco, Sören, are you still able to reproduce the crash on the latest Beta 146?

I’m not able to verify it myself, as I can’t reproduce the issue on an affected Nightly build (146.0a1 – 20251104214230). Tested with macOS 26.1.

Comment 16

[Francesco Lodolo [:flod]]

This was backed out in bug 1360870.

Comment 17

[Sören Hentzschel]

I can no longer reproduce it for the reason mentioned in comment 16. I also tested the latest beta version to verify that Firefox Beta 146 is not affected and can confirm that it does not crash on Instagram.