Closed Bug 1920996 Opened 2 years ago Closed 2 years ago

Categories

(Core :: DOM: Core & HTML, defect)

Firefox 132
Desktop
Windows 11
defect

Tracking

()

VERIFIED FIXED
132 Branch
Tracking Status
firefox-esr115 --- unaffected
firefox-esr128 --- unaffected
firefox130 --- unaffected
firefox131 --- unaffected
firefox132 + verified
firefox133 --- verified

People

(Reporter: alice0775, Assigned: baku)

References

(Regression)

Details

(4 keywords)

Attachments

(1 file, 1 external file)

Attached file about:support —

This is clone of Bug 1920101.
The rendering problem is gone, but the problem of high CPU and memory usage persists even after bug 1920101 has been fixed.
The problem is reproduced on Nightly132.0a1(20240925090641) Windows11 with new clean profile.

Steps to reproduce:

  1. Open https://www.microsoft.com/en-us
  2. Wait for a while

Actual results:
Memory usage keeps increasing over time. (5GB/2min, 10GB/5min ...).
And Close button of windows control(at the top right of browser) becomes unresponsive.

Profiler log(Only 5 seconds seems to be the limit of what can be captured.)
https://share.firefox.dev/3Xx4xwG

After recording for a certain amount of time in the profiler, the profiler does not appear due to a timeout error.

crash Id : bp-cdcfd683-cc95-4e90-99d8-b9a5e0240924

Expected results:
No such high CPU & memory usage.

OS: Unspecified → Windows 11
Hardware: Unspecified → Desktop
Version: unspecified → Firefox 132
Severity: -- → S2

Tried to capture a profile with the "cookies" preset logging enabled: https://share.firefox.dev/3XARudL

Flags: needinfo?(amarchesini)

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

It looks like most of the main process CPU time is being spent in CookieLogging::LogFailure(), inside the logging module's printing code. Maybe these error messages can be cached to avoid repeated printf'ing?

Summary: https://www.microsoft.com/en-us hangs in Nightly → https://www.microsoft.com/en-us hangs in Nightly in CookieLogging::LogFailure()

Are we supposed to be logging information about cookies in Nightly? Where is it going?

Eh maybe that's just from profiling in cookie mode? I'll stop talking as I clearly don't know what is going on here.

Summary: https://www.microsoft.com/en-us hangs in Nightly in CookieLogging::LogFailure() → https://www.microsoft.com/en-us hangs in Nightly
Assignee: nobody → amarchesini
Status: NEW → ASSIGNED
Flags: needinfo?(amarchesini)
Pushed by amarchesini@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/cce647667216 Do not dispatch a CookieChangeEvent for an already expired unknown cookie, r=cookie-reviewers,valentin
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/48360 for changes under testing/web-platform/tests
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 132 Branch
Upstream PR merged by moz-wptsync-bot
Flags: qe-verify+

I was able to reproduce the issue on Win11x64 using FF build 132.0a1(20240925152840), I reached 8GB in 2mins.
Verified as fixed on Win11x64 using FF build 133.0a1(20241003094710) and 132.0b2.

Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: