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

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


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

chromium-rel-mac11-pro
chromium-rel-win7-dual
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/12d31cdac40000

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

Adding SupportsDX12 and SupportsVulkan to UMA histogram for the Windows platform by magchen@chromium.org
https://chromium.googlesource.com/chromium/src/+/35d65e4a3183aaf2a394493288df064b444d74f8

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

This regression won't be fixed as it works as intended. This CL will start a separate GPU process to collect DX12 and Vulkan information 15 seconds after the browser launch. Then the process will quit when the job is done. The duration is short. This job needs to load D3d12.dll and vulkan-1.dll. Thus the memory consumption will increase. Both dlls will be unloaded at the end of this GPU process.