Chrome Version: Chrome 66.0.3359.33 (Official Build) beta (64-bit)
OS: macOS 10.12.6 (16G29)

What steps will reproduce the problem?
This only happens sometimes unfortunately. It's not something that can be reliably reproduced. We have code like this:

try {
  console.log('Calling WebAssembly.instantiate');
  const promise = WebAssembly.instantiate(binary, info);
  console.log('Awaiting WebAssembly.instantiate');
  output = await promise;
  console.log('Finished WebAssembly.instantiate');
} finally {
  const afterTime = performance.now();
  console.log(`WebAssembly.instantiate: ${(afterTime - beforeTime).toFixed(1)}ms`);
}

What is the expected result?
A log of 'Finished WebAssembly.instantiate' should follow 'Awaiting WebAssembly.instantiate' in around 8 seconds.

What happens instead?
Twice this past week, a coworker has tried to load our app and gotten logs for 'Calling WebAssembly.instantiate' and 'Awaiting WebAssembly.instantiate' but not 'Finished WebAssembly.instantiate' or 'WebAssembly.instantiate: ms', at least not for several minutes. And the CPU seems idle so it's not an infinite loop somewhere. Have you gotten any reports of this happening before? What would you recommend we do? Right now we're considering disabling our WebAssembly build in Chrome for everyone using our product.