Closed Bug 2058181 Opened 1 month ago Closed 5 days ago

www.cerave.pt - Tab crashes during navigation across product pages

Categories

(Core :: Layout: Grid, defect, P2)

Firefox 152
Desktop
Windows 10
defect

Tracking

()

RESOLVED FIXED
157 Branch
Webcompat Priority P2
Webcompat Score 5
Tracking Status
firefox-esr140 --- unaffected
firefox-esr153 --- fixed
firefox153 --- wontfix
firefox154 --- wontfix
firefox155 --- wontfix
firefox156 --- fixed
firefox157 --- verified

People

(Reporter: bfarkas, Assigned: emilio)

References

(Depends on 1 open bug, Regression, )

Details

(4 keywords, Whiteboard: [webcompat-source:web-bugs][autowebcompat:processed][autowebcompat:repro-failed], [wptsync upstream])

Crash Data

User Story

autowebcompat-repro-status:failed
autowebcompat-repro-reason:not_reproducable
platform:windows,mac,linux,android
impact:site-broken
configuration:general
affects:some
branch:release
diagnosis-team:layout
user-impact-score:150

Attachments

(4 files, 1 obsolete file)

Environment:
Operating system: Windows 10
Firefox version: Firefox 153.0 / Firefox Nightly 155.0a1 (2026-07-27)

Steps to reproduce:

  1. Access: https://www.cerave.pt/
  2. Select different products
  3. Scroll down the page to view the product information
  4. Observe the page

Expected Behavior:
The product pages load accordingly

Actual Behavior:
Tab crashes during navigation across product pages

Notes:

  • Reproduces regardless of the status of ETP
  • Reproduces in firefox-nightly, and firefox-release
  • Does not reproduce in chrome

Created from https://github.com/webcompat/web-bugs/issues/229678

Attached video Crash Nightly vs Chrome
Whiteboard: [webcompat-source:web-bugs] → [webcompat-source:web-bugs][autowebcompat:processed]

Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.

User Story: (updated)
Whiteboard: [webcompat-source:web-bugs][autowebcompat:processed] → [webcompat-source:web-bugs][autowebcompat:processed][autowebcompat:repro-failed]
User Story: (updated)

Bernadett, I can't reproduce this, and what you show in the screen recording looks like a severe performance issue. Can you capture a profile?

Flags: needinfo?(bfarkas)

Crash with Firefox 154.0b3
bp-08ef59df-abfa-4a7c-a244-fc38a0260728

Flags: needinfo?(bfarkas)

The crashes look like OOM'ing in layout, so let's have the layout team have a look. I can't reproduce this?

Severity: -- → S2
User Story: (updated)
Webcompat Priority: --- → P2
Webcompat Score: --- → 5
Priority: -- → P2

FWIW I can't reproduce either.

Alice0775's crash reports show us OOM'ing in ExpandNonRepeatAutoTracks which is here:
https://searchfox.org/firefox-main/rev/2c35ff84ed7d1ca088a41f830bfab0be50868536/layout/generic/nsGridContainerFrame.cpp#1849-1851

// Store mTrackListValues into mExpandedTracks with `repeat(INTEGER, ...)`
// tracks expanded.
void ExpandNonRepeatAutoTracks() {

Based on that, it seems like this would happen if the site were asking for an absurd number of repeated grid tracks, and we're explicitly allocating space for them, when instead we could be collapsing them into a compact representation as proposed in bug 1752237. So for now I'm triaging as dependent on that platform bug.

(bp-08ef59df-abfa-4a7c-a244-fc38a0260728 shows OOM Allocation Size: 2,208,301,056 bytes (2.21 GB) which I think means that's how much space we thought we needed for this array-of-tracks, which would be a massive number of tracks...)

Perusing the site's CSS for repeat() expressions, I'm not finding any cases with an absurd number of repeated tracks, though - everything looks like it's single-digits number of repeats. I wonder if this was a brief mistake that the site has corrected. Alice0775 & Bernadett, can you still reproduce? If so, I wonder if you're able to come up with a reduced testcase that reliably triggers the crash, maybe starting with the SingleFile extension in Chrome to produce a standalone html testcase that might crash in Firefox and can be chipped away at to reduce it?

Depends on: 1752237
Flags: needinfo?(bfarkas)
Flags: needinfo?(alice0775)

I can reproduce the crash on Nightly156.0a1 Build ID 20260825090428.
bp-8937adea-4f49-41d8-87bb-ab4390260825
bp-dfdb78e5-8379-469c-9e42-aecc20260825

Flags: needinfo?(alice0775)

STR:

  1. Open https://www.cerave.pt/todos-os-produtos/locao-facial-hidratante
  2. Click Aceitar todos os cookies if any
  3. Click x button of SUBSCREVA A NOSSA NEWSLETTER!
  4. Mouse hover navigation menu such as PRODUTOS SOBRE CERAVE ...

Regression window:
https://hg-edge.mozilla.org/integration/autoland/pushloghtml?fromchange=55931b4d2f4bfbe49194a948c289262bd9221e4c&tochange=75a370cf4d9816ef738c4397c52cda04c19ed838

Keywords: regression
Regressed by: 2038512

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

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

Flags: needinfo?(emilio)
Crash Signature: [@ OOM | large | NS_ABORT_OOM | nsTArray_Impl<T>::EmplaceBackInternal | nsTArray<T>::EmplaceBack | nsGridContainerFrame::TrackSizingFunctions::ExpandNonRepeatAutoTracks ]
Keywords: crash

Style of the crashing grid:

  Rules(None):
    [--columns: 1, --rows: 2147483647] - CascadePriority { cascade_level: CascadeLevel(3), flags: RuleCascadeFlags(0x0), layer_order: LayerOrder(65535) }
    [display: grid, grid-template-columns: repeat(var(--columns),auto), grid-template-rows: repeat(var(--rows),auto), align-content: flex-start, text-align: left, row-gap: 0px, column-gap: 3.125rem] - CascadePriority { cascade_level: CascadeLevel(3), flags: RuleCascadeFlags(0x0), layer_order: LayerOrder(65534) }
    [--columns: 2, --rows: 6] - CascadePriority { cascade_level: CascadeLevel(3), flags: RuleCascadeFlags(0x0), layer_order: LayerOrder(65534) }
    [margin-top: 0px, margin-right: 0px, margin-bottom: 0px, margin-left: 0px] - CascadePriority { cascade_level: CascadeLevel(3), flags: RuleCascadeFlags(0x0), layer_order: LayerOrder(65534) }
    [padding-top: 0px, padding-right: 0px, padding-bottom: 0px, padding-left: 0px] - CascadePriority { cascade_level: CascadeLevel(3), flags: RuleCascadeFlags(0x0), layer_order: LayerOrder(65534) }
    [list-style-position: outside, list-style-image: none, list-style-type: none, margin-top: 0px, margin-right: 0px, margin-bottom: 0px, margin-left: 0px] - CascadePriority { cascade_level: CascadeLevel(3), flags: RuleCascadeFlags(0x0), layer_order: LayerOrder(65534) }
    [box-sizing: border-box] - CascadePriority { cascade_level: CascadeLevel(3), flags: RuleCascadeFlags(0x0), layer_order: LayerOrder(65534) }
    [list-style-type: circle] - CascadePriority { cascade_level: CascadeLevel(0), flags: RuleCascadeFlags(0x0), layer_order: LayerOrder(65534) }
    [margin-block-start: 0px, margin-block-end: 0px] - CascadePriority { cascade_level: CascadeLevel(0), flags: RuleCascadeFlags(0x0), layer_order: LayerOrder(65534) }
    [counter-reset: list-item 0] - CascadePriority { cascade_level: CascadeLevel(0), flags: RuleCascadeFlags(0x0), layer_order: LayerOrder(65534) }
    [display: block, list-style-type: disc, margin-block-start: 1em, margin-block-end: 1em, padding-inline-start: 40px] - CascadePriority { cascade_level: CascadeLevel(0), flags: RuleCascadeFlags(0x0), layer_order: LayerOrder(65534) }
    [unicode-bidi: isolate] - CascadePriority { cascade_level: CascadeLevel(0), flags: RuleCascadeFlags(0x0), layer_order: LayerOrder(65534) }

I think fix should be trivial-ish.

Flags: needinfo?(bfarkas)
Assignee: nobody → emilio
Status: NEW → ASSIGNED
Flags: needinfo?(emilio)
Attachment #9632852 - Attachment is obsolete: true

Backed out for causing mass failures

Flags: needinfo?(emilio)
Flags: needinfo?(emilio)
Component: Site Reports → Layout: Grid
Product: Web Compatibility → Core
Version: unspecified → Firefox 152
Status: ASSIGNED → RESOLVED
Closed: 5 days ago
Resolution: --- → FIXED
Target Milestone: --- → 157 Branch

The patch landed in nightly and beta is affected, along with ESR.
:emilio, is this bug important enough to require an uplift?

For more information, please visit BugBot documentation.

Flags: needinfo?(emilio)
Attachment #9634135 - Flags: approval-mozilla-beta?

firefox-beta Uplift Approval Request

  • User impact if declined/Reason for urgency: OOM crash reachable from website
  • Code covered by automated testing?: yes
  • Fix verified in Nightly?: yes
  • Needs manual QE testing?: yes
  • Steps to reproduce for manual QE testing: comment 10
  • Risk associated with taking this patch: low
  • Explanation of risk level: relatively well tested codepath, and edge case behavior anyway.
  • String changes made/needed?: none
  • Is Android affected?: yes
Flags: qe-verify+

firefox-esr153 Uplift Approval Request

  • User impact if declined/Reason for urgency: OOM crash reachable from website
  • Code covered by automated testing?: yes
  • Fix verified in Nightly?: yes
  • Needs manual QE testing?: yes
  • Steps to reproduce for manual QE testing: comment 10
  • Risk associated with taking this patch: low
  • Explanation of risk level: relatively well tested codepath, and edge case behavior anyway.
  • String changes made/needed?: none
  • Is Android affected?: yes
Attachment #9634137 - Flags: approval-mozilla-esr153?
Flags: needinfo?(emilio)
QA Whiteboard: [uplift][qa-ver-needed-c157/b156]

I was able to reproduce the crash(https://crash-stats.mozilla.org/report/index/3ae905fd-4144-4362-beee-ff5720260902) on Win11x64 using Firefox build 154.0b1(20260722090302).
Verified as fixed on Win11x64/Mac 15.5 using Firefox build 157.0a1. Waiting for beta.

QA Contact: mchiorean
Attachment #9634135 - Flags: approval-mozilla-beta? → approval-mozilla-beta+

Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/62396 for changes under testing/web-platform/tests

Whiteboard: [webcompat-source:web-bugs][autowebcompat:processed][autowebcompat:repro-failed] → [webcompat-source:web-bugs][autowebcompat:processed][autowebcompat:repro-failed], [wptsync upstream]
Attachment #9634137 - Flags: approval-mozilla-esr153? → approval-mozilla-esr153+

Upstream PR merged by moz-wptsync-bot

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: