Issue metadata
Sign in to add a comment
|
v8.browsing_desktop and v8.browsing_desktop_ignition failure on chromium.perf on several mac bots |
||||||||||||||||||||||
Issue descriptionWe are seeing failures of these two benchmarks on Mac 10.10 Perf (4): https://uberchromegw.corp.google.com/i/chromium.perf/builders/Mac%2010.10%20Perf%20%284%29/builds/6492 Mac Retina Perf (4): https://uberchromegw.corp.google.com/i/chromium.perf/builders/Mac%20Retina%20Perf%20%284%29/builds/6536 Mac HDD Perf (4): https://uberchromegw.corp.google.com/i/chromium.perf/builders/Mac%20HDD%20Perf%20%284%29/builds/3688 Mac Pro 10.11 Perf https://chromium-swarm.appspot.com/user/task/32578b567a440e10 Mac Air 10.11 Perf https://chromium-swarm.appspot.com/user/task/3257255014be0710 We are seeing a similar stack trace for most of them where the test is timing out, but the browser log is showing errors with memory_dump_manager.cc. Link to a failing log on Mac 10.10 Perf: https://uberchromegw.corp.google.com/i/chromium.perf/builders/Mac%2010.10%20Perf%20%284%29/builds/6492/steps/v8.browsing_desktop/logs/stdio Relevant stack trace: INFO:root:*************** BROWSER STANDARD OUTPUT *************** INFO:root:2016-11-07 10:57:15.215 Google Chrome[22675:178469] NSWindow warning: adding an unknown subview: <FullSizeContentView: 0x7fe5984b1670> 2016-11-07 10:57:15.216 Google Chrome[22675:178469] Call stack: ( "+callStackSymbols disabled for performance reasons" ) [22675:1299:1107/105719:ERROR:memory_dump_manager.cc(573)] Disabling MemoryDumpProvider "ContextProviderCommandBuffer". Dump failed multiple times consecutively. [22681:17155:1107/105719:ERROR:memory_dump_manager.cc(573)] Disabling MemoryDumpProvider "ContextProviderCommandBuffer". Dump failed multiple times consecutively. [22675:1299:1107/105719:ERROR:memory_dump_manager.cc(573)] Disabling MemoryDumpProvider "ContextProviderCommandBuffer". Dump failed multiple times consecutively. A Parser-blocking, cross-origin script, http://aax.amazon-adsystem.com/e/dtb/bid?src=3276&u=http%3A%2F%2Fwww.12news.com%2Fnews%2Flocal%2Farizona%2Flargest-us-measles-outbreak-in-arizona-after-people-refused-vaccinations%2F266726754&cb=4620000, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details. A Parser-blocking, cross-origin script, http://aax.amazon-adsystem.com/e/dtb/bid?src=3276&u=http%3A%2F%2Fwww.12news.com%2Fnews%2Flocal%2Farizona%2Flargest-us-measles-outbreak-in-arizona-after-people-refused-vaccinations%2F266726754&cb=4620000, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details. [22681:1299:1107/105728:ERROR:memory_dump_manager.cc(573)] Disabling MemoryDumpProvider "ContextProviderCommandBuffer". Dump failed multiple times consecutively. [22681:1299:1107/105728:ERROR:memory_dump_manager.cc(573)] Disabling MemoryDumpProvider "ContextProviderCommandBuffer". Dump failed multiple times consecutively. INFO:root:*********** END OF BROWSER STANDARD OUTPUT ************ INFO:root:********************* BROWSER LOG ********************* INFO:root:No log file INFO:root:***************** END OF BROWSER LOG ****************** Traceback (most recent call last): File "/b/c/b/Mac_10_10_Perf__4_/src/third_party/catapult/telemetry/telemetry/internal/story_runner.py", line 87, in _RunStoryAndProcessErrorIfNeeded state.RunStory(results) File "/b/c/b/Mac_10_10_Perf__4_/src/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 "/b/c/b/Mac_10_10_Perf__4_/src/third_party/catapult/telemetry/telemetry/page/shared_page_state.py", line 299, in RunStory self._current_page.Run(self) File "/b/c/b/Mac_10_10_Perf__4_/src/third_party/catapult/telemetry/telemetry/page/__init__.py", line 109, in Run self.RunPageInteractions(action_runner) File "/b/c/b/Mac_10_10_Perf__4_/src/tools/perf/page_sets/system_health/system_health_story.py", line 112, in RunPageInteractions self._DidLoadDocument(action_runner) File "/b/c/b/Mac_10_10_Perf__4_/src/tools/perf/page_sets/system_health/browsing_stories.py", line 74, in _DidLoadDocument self._ScrollMainPage(action_runner) File "/b/c/b/Mac_10_10_Perf__4_/src/tools/perf/page_sets/system_health/browsing_stories.py", line 83, in _ScrollMainPage action_runner.tab.WaitForDocumentReadyStateToBeComplete() File "/b/c/b/Mac_10_10_Perf__4_/src/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 "/b/c/b/Mac_10_10_Perf__4_/src/third_party/catapult/telemetry/telemetry/internal/browser/web_contents.py", line 76, in WaitForDocumentReadyStateToBeComplete 'document.readyState == "complete"', timeout) File "/b/c/b/Mac_10_10_Perf__4_/src/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 "/b/c/b/Mac_10_10_Perf__4_/src/third_party/catapult/telemetry/telemetry/internal/browser/web_contents.py", line 142, in WaitForJavaScriptExpression e.message + '\n' + debug_message) TimeoutException: Timed out while waiting 90s for IsJavaScriptExpressionTrue. Ulan can you please investigate and reassign if necessary?
,
Nov 8 2016
,
Nov 8 2016
,
Nov 8 2016
This has been pretty consistently failing since last week on some memory issues and I think it is worth another look since the stack trace is very different from what we marked as a duplicate. Maybe Juan would have some insight into that.
,
Nov 8 2016
I see that the consistent failures started on Nov 4 on this benchmark: https://uberchromegw.corp.google.com/i/chromium.perf/builders/Mac%2010.10%20Perf%20%284%29?numbuilds=200 System health benchmark failures from 663025 also started on Nov 4: https://uberchromegw.corp.google.com/i/chromium.perf/builders/Mac%20HDD%20Perf%20%283%29
,
Nov 8 2016
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by u...@chromium.org
, Nov 8 2016