Example failure: http://bit.ly/2g5LfKe

system_health.memory_mobile and system_health.memory_mobile.reference are both failing often (25% of the time?) on all Android configurations. There doesn't seem to be a consistent story that they fail on: I've seen browse:news:flipboard, browse:news:nytimes, background:media:imgur, and background:tools:gmail all fail. In each case, the error seems to stem from Chrome crashing, which makes me believe that something about memory tracing is likely overloading the browser and causing the crash. Clock sync failures (https://paste.googleplex.com/6136840817999872) and WebSocketConnectionClosedExceptions (https://paste.googleplex.com/5261492525989888) are two common ways that this manifests.

ulan@, are you the right person to assign this to? If not, please feel free to redirect elsewhere.

This bug is high-priority: because the failures aren't isolated to a single user story, it's impossible to resolve this problem without disabling the system health memory benchmarks on Android altogether.