All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=712557

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggqDrjgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg_O-s-wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgguKz9AoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg_P2nowoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggumKowsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggqakuAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg_Mvv6woM


Bot(s) for this bug's original alert(s):

webrtc-android-tests-nexus5-kitkat

Hi, Magnus,

this apparent regression correlates with your changes to android logging. Can you investigate? Graphs have varied quite a lot, see e.g., the opposite change tracked in issue https://bugs.chromium.org/p/chromium/issues/detail?id=708925

It sounds unlikely that this is related to the changes I made to Android logging since Chromium shouldn't be using that code. I will take a look when I have time.