Closed Bug 1388111 Opened 7 years ago Closed 7 years ago

Ghost window regression on telemetry in 56

Categories

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

Product:
Core
Component:
DOM: Core & HTML
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: mccr8, Assigned: mccr8)

References

(Blocks 1 open bug,
URL
)

Details

(Whiteboard: [MemShrink])

Telemetry shows that something went awry with our ghost windows somewhere between the July 11th Nightly and the July 29th Nightly. Unfortunately due to broken telemetry (bug 1384337), we don't have a more specific window than that. I'm not really sure what to do with this besides investigating our known ghost window issues (open bugs blocking the ghost windows bug) and see which ones might possibly not affect builds before July 11th.
It is possible that this is not a real regression, but simply a result of bug 1384337 changing how we measure ghost windows.
Eric, could you please back out bug 1384337 so we can see if this is just a new higher baseline level of ghost windows, or if we landed a regression during that 2.5 weeks? I'm fine with having a higher level, I just want to know what my level of panic should be.
Flags: needinfo?(erahm)
RyanVM backed it out. Thanks, Ryan!
Flags: needinfo?(erahm)
Needinfo'ing myself to check telemetry in a few days.
Flags: needinfo?(continuation)
Whiteboard: [MemShrink]
Alright, the level of ghost windows has gone down again, so this is in fact a change related to how we are measuring ghost windows. At the present time, we probably care more about avoiding perf issues than accurately measuring ghost windows, so feel free to reland your patches, Eric, if you think that makes sense.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(continuation)
Resolution: --- → WORKSFORME
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.