UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.84 Safari/537.36

Steps to reproduce the problem:
1. Load attached HTML, which loads an AudioWorklet module but does not create any AudioWorkletNodes.
2. Open dev tools.
3. Reload the page multiple times.

What is the expected behavior?

What went wrong?
Reloading eventually causes the tab to hang (cannot interact with the page or reload, closing the tab doesn't work at first) and the expected console messages to not appear.

In the real code which this is the reduced test case of, it consistently hangs on the first reload.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 65.0.3298.0  Channel: canary
OS Version: OS X 10.11.6
Flash Version: 

I don't see a hang if the dev tools are not open.

I'm attempting to use/test the new AudioWorklet feature as my existing code uses ScriptProcessorNode, but this problem is making it hard to debug my code.

I don't know whether the specific code in the worklet module script is relevant or not — in any case, it obviously ought to be harmless.

The script does not create any AudioWorkletNodes and is therefore kind of useless, but that's because I hit this bug while debugging failures to successfully create the node I intended to create (exceptions occurring in my code before getting to registerProcessor).
 

Deleted: hang.html 278 bytes

hang.html 278 bytes View Download

Deleted: worker.js 136 bytes

worker.js 136 bytes View Download