New issue
Advanced search Search tips

Issue 726686 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

browse:media:imgur system_health.memory_desktop failing on win-7-ati-gpu

Project Member Reported by perezju@chromium.org, May 26 2017

Issue description

Number of failures seen on recent builds since 779: 12111---

Example recent build:
https://luci-milo.appspot.com/buildbot/chromium.perf/Win%207%20ATI%20GPU%20Perf/779

The error happens while trying to navigate to an item, waiting for an element to appear:

  File "c:\b\s\w\ir\tools\perf\page_sets\system_health\browsing_stories.py", line 38, in _NavigateToItem
    action_runner.WaitForElement(element_function=item_selector)
  File "c:\b\s\w\ir\third_party\catapult\common\py_trace_event\py_trace_event\trace_event_impl\decorators.py", line 75, in traced_function
    return func(*args, **kwargs)
  File "c:\b\s\w\ir\third_party\catapult\telemetry\telemetry\internal\actions\action_runner.py", line 280, in WaitForElement
    timeout_in_seconds=timeout_in_seconds))

And a second timeout exception is raised while trying to stop tracing and gather a trace:

ChromeTracingStoppedError: Exceptions raised when trying to stop Chrome devtool tracing:
Error when trying to stop Chrome tracing on devtools at port 63794:
Traceback (most recent call last):
  File "c:\b\s\w\ir\third_party\catapult\telemetry\telemetry\internal\platform\tracing_agent\chrome_tracing_agent.py", line 214, in StopAgentTracing
    client.StopChromeTracing()
  File "c:\b\s\w\ir\third_party\catapult\telemetry\telemetry\internal\backends\chrome_inspector\devtools_client_backend.py", line 360, in StopChromeTracing
    backend_id=backend.id)
  File "c:\b\s\w\ir\third_party\catapult\common\py_trace_event\py_trace_event\trace_event_impl\decorators.py", line 75, in traced_function
    return func(*args, **kwargs)
  File "c:\b\s\w\ir\third_party\catapult\telemetry\telemetry\internal\backends\chrome_inspector\inspector_backend.py", line 243, in EvaluateJavaScript
    return self._EvaluateJavaScript(expression, context_id, timeout)
[...]
  File "c:\b\s\w\ir\third_party\catapult\telemetry\third_party\websocket-client\websocket\_socket.py", line 83, in recv
    raise WebSocketTimeoutException(message)
TimeoutException: 

Furthermore, there is a timeout exception when trying to take a screenshot:
WARNING:root:Exception when trying to capture screenshot: TimeoutException('',)

Full log:
https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Fchromium.perf%2FWin_7_ATI_GPU_Perf%2F779%2F%2B%2Frecipes%2Fsteps%2Fsystem_health.memory_desktop_on_ATI_GPU_on_Windows_on_Windows-2008ServerR2-SP1%2F0%2Fstdout

First failure was spotted at:
https://luci-milo.appspot.com/buildbot/chromium.perf/Win%207%20ATI%20GPU%20Perf/775

With cl range:
http://test-results.appspot.com/revision_range?start=474275&end=474398
 
For the screenshot, I filed https://github.com/catapult-project/catapult/issues/3592 so that we don't need to rely on devtool.
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, May 26 2017

Cc: scottmg@chromium.org
Owner: scottmg@chromium.org

=== Auto-CCing suspected CL author scottmg@chromium.org ===

Hi scottmg@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Test failure found with culprit

Suspected Commit
  Author : scottmg
  Commit : e87ca325b7641587a273968c077adac3a3fa5edb
  Date   : Wed May 24 17:54:17 2017
  Subject: fuchsia: Implement base::debug::StackTrace

Bisect Details
  Configuration: winx64ati_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:all_processes:reported_by_chrome:allocated_objects_size_avg/browse_media/browse_media_imgur

Revision             Exit Code      N
chromium@474274      0 +- N/A       10      good
chromium@474336      0 +- N/A       10      good
chromium@474344      0 +- N/A       10      good
chromium@474348      0 +- N/A       10      good
chromium@474349      1 +- N/A       10      bad       <--
chromium@474350      1 +- N/A       10      bad
chromium@474352      1 +- N/A       10      bad
chromium@474367      1 +- N/A       10      bad
chromium@474398      1 +- N/A       10      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.media.imgur system_health.memory_desktop

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8978534886603195968

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6405825599373312


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!
Status: Assigned (was: Untriaged)
Components: Test>Telemetry
Components: -Tests>Telemetry

Sign in to add a comment