Closed Bug 1376868 Opened 7 years ago Closed 2 years ago

Understand why some PBrowser messages are showing up as not labeled

Categories

(Core :: DOM: Content Processes, task, P3)

Product:
Core
Component:
DOM: Content Processes
Type:
task

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: billm, Unassigned)

References

Details

In the telemetry data from June 26, I see these runnables unlabeled:

PBrowser::Msg_AsyncMessage
PBrowser::Msg_RealMouseMoveEvent

In theory all PBrowser messages should be labeled with a TabGroup. We need to figure out how this is happening.
Priority: -- → P3

I am not sure if this as at all relevant anymore? mccr8, ni? you based on bug 1321812 comment 21.

Type: enhancement → task
Flags: needinfo?(continuation)

Labeling was part of the Quantum DOM work, which has been removed for a long time.

Status: NEW → RESOLVED
Closed: 2 years ago
Flags: needinfo?(continuation)
Resolution: --- → WONTFIX

(I went through and closed a bunch of the other bugs blocking the Labeling meta bug.)

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