Open Bug 1548003 Opened 5 years ago Updated 2 years ago

WipeContainingBlock marker is invalid

Categories

(Core :: Gecko Profiler, defect, P2)

defect

Tracking

()

Tracking Status
firefox68 --- affected

People

(Reporter: julienw, Unassigned)

Details

WipeContainingBlock marker is invalid: it uses the type "tracing" but has no "interval" value.

{
  "start": 31428.499575484377,
  "dur": 0,
  "name": "WipeContainingBlock: IB splits",
  "title": null,
  "data": {
    "type": "tracing",
    "category": "Layout"
  }
}

[1] https://searchfox.org/mozilla-central/rev/b756e6d00728dda4121f8278a744381d8643317a/layout/base/nsCSSFrameConstructor.cpp#11245-11246

This was lately changed in bug 1520526 but the marker itself was added in bug 1498067. I don't know if bug 1520526 changed the behavior by adding this "category", what do you think Greg?

Flags: needinfo?(gtatum)

I don't understand the intent of that marker, or the intent of the TracingKind::TRACING_EVENT.

I wonder if they meant to use AUTO_PROFILER_TRACING instead.

Flags: needinfo?(gtatum)

Hey Emilio, I think you were the one interested by this marker in the first place as you did it in bug 1498067. Could you look at it, or at least shed some light? Thanks!

Flags: needinfo?(emilio)

The intent of that marker is to know in the profiler UI that that codepath has been hit. That causes some other work to be done asynchronously, but it's helpful to know that this is the origin of the codepath.

I checked with Markus before landing that patch and in theory an interval was not needed. The profiler UI needed a fix to show that: https://github.com/devtools-html/perf.html/pull/1351

I don't understand why a tracing marker would need an interval.

Flags: needinfo?(emilio)

Thanks Emilio, I'll double check with Markus. I realize that I asked the exact same question in the pull request, but I don't remember if I got an answer in another channel.

In our terminology a "tracing" marker is a pair of start and end markers. Maybe the terminology needs to be clarified better. We can as easily add a "marker" that wouldn't be "tracing" and representing one point in time.

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.