Investigate why many DidComposite messages are not labeled

RESOLVED INVALID

Status

()

Product:
Core
Component:
Graphics: Layers
Type:
enhancement
Status:
RESOLVED INVALID
Opened:
2 years ago
Updated:
2 years ago

People

(Reporter: billm, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [gfx-noted]) 

Bug 1333968 was supposed to label the DidComposite message. However, it seems that about 6% of DidComposite messages end up not having a label. I'm guessing that's because we take this branch:
http://searchfox.org/mozilla-central/rev/fdb811340ac4e6b93703d72ee99217f3b1d250ac/gfx/layers/ipc/CompositorManagerChild.cpp#249

However, I can't figure out what the circumstances are where we would do that.

This is important because DidComposite messages are extremely common. Although only 6% of them are unlabeled, this still makes them the most common unlabeled message!

Another odd thing is that, despite the fix for bug 1337548, we still get about 3x as many DidComposite messages as vsync messages. That seems odd.
See Also: → 1337548
Whiteboard: [gfx-noted]
See Also: → 1349991
The data here was incorrect because of bug 1380880. The issue with there being many more DidComposite messages than Vsyncs is still extant, but 1349991 will hopefully fix that,
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.