New issue
Advanced search Search tips

Issue 787120 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Dec 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

system_health.common_desktop/load_accessibility:shopping:amazon failing on win8 and win10 perf vots

Project Member Reported by rnep...@chromium.org, Nov 20 2017

Issue description

https://build.chromium.org/p/chromium.perf/builders/Win%2010%20Perf
https://build.chromium.org/p/chromium.perf/builders/Win%208%20Perf/builds/1570

.....
.....
	00007ff8`4c5313d2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : chrome!base::`anonymous namespace'::ThreadFunc+0xf2
	00007ff8`4d3a5444 : 00007ff8`4c5313b0 00000000`00000000 00000000`00000000 00000000`00000000 : KERNEL32!BaseThreadInitThunk+0x22
	00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x34
	
	  41  Id: d6c.880 Suspend: 0 Teb: 00007ff7`83a06000 Unfrozen
	*** WARNING: Unable to verify checksum for mswsock.dll
	*** ERROR: Symbol file could not be found.  Defaulted to export symbols for mswsock.dll - 
	RetAddr           : Args to Child                                                           : Call Site
	00007ff8`49cfc979 : 00007ff8`49cfc900 00007ff8`49cf0000 00000000`00000000 00000000`00000000 : ntdll!ZwRemoveIoCompletion+0xa
	00007ff8`4c5313d2 : 00007ff8`49cfca40 0000007b`2facc220 0000007b`2fab6490 0000007b`2fab6490 : mswsock!NSPStartup+0x2449
	00007ff8`4d3a5444 : 00007ff8`4c5313b0 00000000`00000000 00000000`00000000 00000000`00000000 : KERNEL32!BaseThreadInitThunk+0x22
	00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x34
********************************************************************************
Standard output:
********************************************************************************
********************************************************************************
System log:
(Not implemented)
(INFO) 2017-11-19 21:36:20,315 devtools_client_backend._IsDevToolsAgentAvailable:80  Devtools client not yet ready: [Errno 10061] No connection could be made because the target machine actively refused it
(INFO) 2017-11-19 21:36:20,315 exception_formatter.PrintFormattedException:19  Try printing formatted exception: None None None
Exception raised when cleaning story run: 
Traceback (most recent call last):
  _RunStoryAndProcessErrorIfNeeded at c:\b\s\w\ir\third_party\catapult\telemetry\telemetry\internal\story_runner.py:130
    test.DidRunStory(state.platform, results)
  DidRunStory at c:\b\s\w\ir\third_party\catapult\telemetry\telemetry\web_perf\timeline_based_measurement.py:290
    trace_result, _ = platform.tracing_controller.StopTracing()
  StopTracing at c:\b\s\w\ir\third_party\catapult\telemetry\telemetry\core\tracing_controller.py:53
    return self._tracing_controller_backend.StopTracing()
  StopTracing at c:\b\s\w\ir\third_party\catapult\telemetry\telemetry\internal\platform\tracing_controller_backend.py:109
    self._IssueClockSyncMarker()
  _IssueClockSyncMarker at c:\b\s\w\ir\third_party\catapult\telemetry\telemetry\internal\platform\tracing_controller_backend.py:215
    self._RecordIssuerClockSyncMarker)
  RecordClockSyncMarker at c:\b\s\w\ir\third_party\catapult\telemetry\telemetry\internal\platform\tracing_agent\chrome_tracing_agent.py:178
    raise ChromeClockSyncError('Cannot issue clock sync. No devtools clients')
ChromeClockSyncError: Cannot issue clock sync. No devtools clients
Locals:
  devtools_clients                             : []
  record_controller_clock_sync_marker_callback : <bound method TracingControllerBackend._RecordIssuerClockSyncMarker of <telemetry.internal.platform.tracing_controller_backend.TracingControllerBackend object at 0x00000000050EF9E8>>
  sync_id                                      : '068b25a8-12ba-4246-8d1f-724e7abb9785'
(INFO) 2017-11-19 21:36:20,325 browser.Close:240  Browser is closed.
[  FAILED  ] load_accessibility:shopping:amazon@{'case': 'load_accessibility', 'group': 'shopping'} (54884 ms)


 
I believe https://build.chromium.org/p/chromium.perf/builders/Win%2010%20Perf/builds/1682 is the oldest run I can find with this failure mode, will start bisecting around there. 
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 21 2017

Cc: dmazz...@chromium.org
Owner: dmazz...@chromium.org
Status: Assigned (was: Untriaged)

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

Hi dmazzoni@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 : Dominic Mazzoni
  Commit : f51324e71030221b7908c7b8b1efe29cee360079
  Date   : Fri Nov 17 18:34:14 2017
  Subject: Only fire live region events on text changes.

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:all_processes:dump_count:heap_profiler_avg/load_accessibility_shopping/load_accessibility_shopping_amazon

Revision             Exit Code      N
chromium@517326      0 +- N/A       20      good
chromium@517421      0 +- N/A       20      good
chromium@517468      0 +- N/A       20      good
chromium@517480      0 +- N/A       20      good
chromium@517483      0 +- N/A       20      good
chromium@517485      0 +- N/A       20      good
chromium@517486      1 +- N/A       20      bad       <--
chromium@517492      1 +- N/A       20      bad
chromium@517515      1 +- N/A       20      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=load.accessibility.shopping.amazon system_health.memory_desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8962369560832408128


For feedback, file a bug with component Speed>Bisection
Should be fixed by this change:

https://chromium-review.googlesource.com/c/chromium/src/+/779062

Status: Fixed (was: Assigned)

Sign in to add a comment