New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 901869 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Yesterday
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

Duplicate IssueBeginFrame When Computing Pipeline Metrics

Project Member Reported by chiniforooshan@chromium.org, Nov 5

Issue description

When I run rendering.desktop benchmark, on ToT, I get the following error:

page_test_results.Fail:540  Failure recorded: Error: Unexpected duplicate step: IssueBeginFrame
    at eventIsValidGraphicsEvent_ (/tracing/metrics/rendering/pipeline.html:34:15)
    at Object.addPipelineHistograms (/tracing/metrics/rendering/pipeline.html:94:14)
    at new renderingMetric (/tracing/metrics/rendering/rendering_metric.html:31:28)
    at runMetrics (/ssd/chromium/src/third_party/catapult/tracing/tracing/metrics/metric_map_function.html:61:16)
    at metricMapFunction (/ssd/chromium/src/third_party/catapult/tracing/tracing/metrics/metric_map_function.html:190:24)
    at Object.mapSingleTrace (/tracing/mre/map_single_trace.html:39:7)
    at eval (/ssd/chromium/src/third_party/catapult/tracing/tracing/mre/map_single_trace_cmdline.html:61:18)
    at Object.runAndConvertErrorsToFailures (/tracing/mre/map_single_trace.html:24:10)
    at mapSingleTraceWithResult (/ssd/chromium/src/third_party/catapult/tracing/tracing/mre/map_single_trace_cmdline.html:52:12)
    at Object.mapSingleTraceMain (/ssd/chromium/src/third_party/catapult/tracing/tracing/mre/map_single_trace_cmdline.html:77:20)

The commend that I run is:
tools/perf/run_benchmark run rendering.desktop --browser=system --output-dir=<OUTDIR> --pageset-repeat=1 --story-filter=amazon_2018

A trace from a run is attached.
 
amazon_2018_2018-11-05_11-34-57_20284.html
7.5 MB View Download
Hm, interesting. I could repro this from the 'system' browser, which for me is 70.0.3538.77. I couldn't repro on tot, or on unstable (which for me is 72.0.3602.2). Perhaps there was a trace-event related bug in the earlier versions?
Status: Assigned (was: Untriaged)
Labels: -Pri-1 Pri-3
I am going to bump the priority to 3 since this is not repro-ing on unstable or tot.

Comment 4 by sadrul@chromium.org, Yesterday (40 hours ago)

Status: WontFix (was: Assigned)
It doesn't look like this is happening? I suspect some change already resolved this issue.

Sign in to add a comment