Seeing this fail semi-regularly on different windows bots due to non-deterministic crashes, eg:

https://uberchromegw.corp.google.com/i/chromium.perf/builders/Win%207%20ATI%20GPU%20Perf%20%282%29/builds/5704/steps/page_cycler_v2.typical_25/logs/stdio

https://uberchromegw.corp.google.com/i/chromium.perf/builders/Win%207%20Intel%20GPU%20Perf%20%282%29/builds/4210/steps/page_cycler_v2.typical_25/logs/stdio

https://uberchromegw.corp.google.com/i/chromium.perf/builders/Win%2010%20Perf%20%282%29/builds/4211/steps/page_cycler_v2.typical_25/logs/stdio

Without stacks ( issue 530197 ) this sort of non-deterministic crash is very time consuming to track down.


Revision range first seen
:
Link to failing step log:


If the test is disabled, please downgrade to Pri-2.