https://www.microsoft.com/en-us hangs in Nightly
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
| 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)
|
36.46 KB,
text/plain
|
Details |
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:
- Open https://www.microsoft.com/en-us
- 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.
| Reporter | ||
Updated•2 years ago
|
| Reporter | ||
Updated•2 years ago
|
Updated•2 years ago
|
Comment 1•2 years ago
|
||
Tried to capture a profile with the "cookies" preset logging enabled: https://share.firefox.dev/3XARudL
Comment 2•2 years ago
|
||
Set release status flags based on info from the regressing bug 1918643
Comment 3•2 years ago
|
||
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?
Comment 4•2 years ago
|
||
Are we supposed to be logging information about cookies in Nightly? Where is it going?
Comment 5•2 years ago
|
||
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.
| Assignee | ||
Comment 6•2 years ago
|
||
Updated•2 years ago
|
| Assignee | ||
Updated•2 years ago
|
Updated•2 years ago
|
Comment 9•2 years ago
|
||
| bugherder | ||
Updated•2 years ago
|
Comment 11•2 years ago
|
||
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.
Description
•