Closed Bug 1954252 Opened 1 year ago Closed 1 year ago

Tabs showing Instagram videos became unresponsive and crashed after closing with [@ IPCError-browser | ShutDownKill ]

Categories

(Core :: DOM: Content Processes, defect)

Firefox 138
defect

Tracking

()

RESOLVED DUPLICATE of bug 1954244

People

(Reporter: matt.fagnani, Unassigned)

Details

(Keywords: regression)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:138.0) Gecko/20100101 Firefox/138.0

Steps to reproduce:

I ran Firefox 138.0a1 20250314211155 on Wayland in Plasma 6.3.3 in a Fedora 42 KDE installation. I logged into my account on instagram.com. I loaded instagram.com/?variant=following I scrolled up and down so that videos were shown many times. I went into the Accounts Center login settings.

Actual results:

Tabs showing Instagram videos became unresponsive. The first video played sometimes, but clicking on it didn't stop the video as it normally would. The pages ' content eventually froze. When I closed the tab, the content process crashed with signatures [@ IPCError-browser | ShutDownKill ] like the following
https://crash-stats.mozilla.org/report/index/4ac61777-0c89-4964-aee7-05acc0250315
https://crash-stats.mozilla.org/report/index/32663bdf-9c06-4e26-b85a-7d7240250315
https://crash-stats.mozilla.org/report/index/e0d05649-d460-4925-9ddc-86dbb0250315

The menu bar and tab bar remained responsive after the tab froze. The tab froze once when I was using the Instagram Accounts Center login settings.

When I closed Firefox, some Firefox processes remained running for about a minute. The crash reporter appeared showing crashes with the signature [@ AsyncShutdownTimeout | Places Clients shutdown | sanitize.js: Sanitize on shutdown ] Crash reports after closing Firefox were:
https://crash-stats.mozilla.org/report/index/1a302b7a-3a84-428f-84eb-3c15c0250315
https://crash-stats.mozilla.org/report/index/c78ca904-7abf-435c-833b-31bc20250315
https://crash-stats.mozilla.org/report/index/6d80c447-796b-4a82-b454-9f8920250315

The problem didn't happen with 138.0a1 20250314044514. I bisected the problem to a patch for Bug 85686 - Mimic Chromium's getSelection().toString() behaviour

19:21.22 INFO: Narrowed integration regression window from [9618bcf1, 30b35b0e] (3 builds) to [9618bcf1, a3cd9e42] (2 builds) (~1 steps left)
19:21.22 INFO: No more integration revisions, bisection finished.
19:21.22 INFO: Last good revision: 9618bcf1929211ce4b5700a9271ddbc1038878d6
19:21.22 INFO: First bad revision: a3cd9e42558548438158c779bcda4ef92187418a
19:21.22 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=9618bcf1929211ce4b5700a9271ddbc1038878d6&tochange=a3cd9e42558548438158c779bcda4ef92187418a

Expected results:

The tabs showing Instagram shouldn't have frozen and should have shown their content normally.

Keywords: regression
Regressed by: 85686

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

For more information, please visit BugBot documentation.

Flags: needinfo?(sefeng)

Thanks for the bug!

Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Duplicate of bug: 1954244
Flags: needinfo?(sefeng)
Resolution: --- → DUPLICATE
No longer regressed by: 85686
Severity: -- → S4
You need to log in before you can comment on or make changes to this bug.