Chrome Version       : 62.0.3202.94
OS Version: 10.0
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari:
    Firefox:
    IE/Edge:

What steps will reproduce the problem?
1. Start memory profiling on the page "about:blank"
2. Run the following code in the console:

    const context = new AudioContext();
    for (var i = 0; i < 1000000; i++) {
        const node = context.createOscillator();
        node.start();
        node.stop();
    }

3. Stop profiling after some time.

What is the expected result?

The stopped oscillator nodes should be garbage collected. The JS heap in the profiler should increase and decrease to nearly the same memory usage as when the profiler began. Once the stopped oscillator goes out of context, it should be eligible for garbage collection.

What happens instead of that?

The JS heap size only increases, by about ~50MB. The stopped oscillator nodes (appear) to not be garbage collected.

Please provide any additional information below. Attach a screenshot if
possible.

UserAgentString: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36