Closed Bug 1915316 Opened 1 year ago Closed 1 year ago

Excessive CC/GC time on Google Cloud Console

Categories

(Core :: Cycle Collector, task)

Product:
Core
Component:
Cycle Collector
Type:
task

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: tcampbell, Unassigned)

Details

Profile: https://share.firefox.dev/4dGk6ZF

This is after using Google Cloud Console for a while (GKE, Cloud SQL, Logs Explorer) the performance gets very bad with 10+ second CC Graph Builder janks. This was captured on a slow Windows-on-ARM64 laptop, but I've heard complaints from others on more performant hardware.

Component: JavaScript: GC → Cycle Collector

What does about:memory look like? Note that the memory report will contain URLs unless you check anonymous for the report. Which is fine, except please note which process is the problematic one, though usually it is obvious.

The general situation with a lot of this "monitoring" style pages is that they leak old entries which the cycle collector unfortunately does not handle well.

Flags: needinfo?(tcampbell)
Status: NEW → RESOLVED
Closed: 1 year ago
Flags: needinfo?(tcampbell)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.