title: Why Chrome is sometimes creating a new virtual machine VM and sometimes not?
body: <p>Look at my example at codepen :</p>
  <p><a href="https://codepen.io/jimver04/pen/gORdBwp" rel="nofollow noreferrer">https://codepen.io/jimver04/pen/gORdBwp</a></p>
  <p>When I see in the console</p>
  <pre><code>put_char    @   selfie_segmentation_…_simd_wasm_bin.js:9
  </code></pre>
  <p>everything works well.</p>
  <p>When I see</p>
  <pre><code>put_char    @VM152  selfie_segmentation_…_simd_wasm_bin.js:9
  </code></pre>
  <p>or whatever @VM+number everything is stack.</p>
  <p>How can I force to run selfie_segmentation_…_simd_wasm_bin.js without VM number ?</p>
  <p>See also my issue posted in Mediapipe : <a href="https://github.com/google/mediapipe/issues/2590" rel="nofollow noreferrer">https://github.com/google/mediapipe/issues/2590</a></p>