Also I should add that neither the page sets or archives have changed. Something in Telemetry or in Chromium is causing much more frequent crashes than before.

Ravi, since this a browser crash, I suspect that it's due to some browser change rather than telemetry change.

From the stack, I see:
Standard output:
********************************************************************************
	[3230:3230:0322/225830:ERROR:browser_main_loop.cc(220)] Running without the SUID sandbox! See https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the sandbox on.


Hmhh, is this expected? We usually always run telemetry with the sandbox

I have always been running CT with --extra-browser-args="--disable-setuid-sandbox --enable-threaded-compositing --enable-impl-side-painting" I do not remember why but I would be surprised if that was the cause of the crashes in last couple of days.

And yes I agree that it is likely a browser change. Do you see anything similar (increased crashes) in the chromium.perf waterfall that started after "Tue Mar 22 22:22:32 2016"?

I see similar failures in Linux Perf (5) that started at around the same time:
https://build.chromium.org/p/chromium.perf/builders/Linux%20Perf%20%285%29?numbuilds=50

Example failure from https://build.chromium.org/p/chromium.perf/builders/Linux%20Perf%20%285%29/builds/14244 is in https://build.chromium.org/p/chromium.perf/builders/Linux%20Perf%20%285%29/builds/14244/steps/rasterize_and_record_micro.key_mobile_sites_smooth/logs/stdio

so this does not appear to be localized to CT.

Looks like this is happening again. The CT bot is reporting about 920 webpages instead of 940+ consistently. This is a smaller loss than before, but I noticed that Linux Perf (5) again has similar failures at around the same time.

If there is an existing bug about the failures in Linux Perf then please merge this one into that.

I think it's  issue 599505