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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=d4601ede1ee7b4b4bd7949c3bbac6ae98aaf1a2a193e1d32e56926a7de0e35a3


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

chromium-rel-win8-dual

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/15d38f2b440000

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/15d38f2b440000

Reland "Add test coverage of field trial for Certificate Transparency log auditing" by robpercival@chromium.org
https://chromium.googlesource.com/chromium/src/+/12795821a0a35b9ca4a6145d9c60da691b356daa

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

I'm not sure why Windows would be seeing a significant increase in memory usage with the CertificateTransparencyLogAuditing feature enabled, since it doesn't do much on that platform. At the time that this bug was created, the only effect of enabling this feature on Windows was that a lookup would be performed in the net::HostCache for each host that provided Signed Certificate Timestamps. This shouldn't affect memory usage. 

We've since made some changes that should reduce memory usage when the feature is disabled (https://crrev.com/c/1009913). The only thing I can suggest would be to remove Windows from the field trial config for the time being; the feature isn't planned for launch on Windows anyway.

Does anyone have recommendations for investigating this? The docs weren't particularly helpful for tracking down the cause of this diff.