UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.162 Safari/537.36

Steps to reproduce the problem:
1. Set up a developer environment to serve a site in HTTPS using a self-signed certificate (I used stunnel).
2. Load a page which attempts to register a service worker on page load: `window.addEventListener('load' () => navigator.serviceWorker.register('/sw.js', {scope: './'}))`
3. The registration will reject because sw.js is signed with a self-signed certificate (and we did NOT start chrome with the --ignore-certificate-errors flag).
4. Open Dev Tools > Performance, check the memory box, and then click the refresh button to refresh the page and log memory.

What is the expected behavior?
The JS Heap value should consistently be reasonable: On my page this should be about ~20MB.

What went wrong?
Approximately 50% of the time, the JS Heap is ~20MB, and 50% of the time it is ~90MB.

Did this work before? N/A 

Chrome version: 65.0.3325.162  Channel: stable
OS Version: 
Flash Version: 

I found this while trying to profile my application and found the numbers very inconsistent. I began removing code and eventually found that this particular line is the one which causes the problem. However, I am performing local development on HTTPS using a self-signed certificate, so the service worker never actually installs, it always fails.

Despite this consistent failed install, 50% of the time my captured metrics are highly inflated, and 50% of the time they are not. Removing the line which registers the service worker fixes this particular performance metric, and it will always log ~20MB.