Running testem on latest Chrome version results in error

[char0n]

not ok 1 Chrome - [undefined ms] - error
    ---
        message: >
            Error: Browser exited unexpectedly
            Stderr: 
             [0516/174119.736985:ERROR:gpu_init.cc(426)] Passthrough is not supported, GL is egl
            [0516/174120.448800:INFO:CONSOLE(2)] "SharedArrayBuffer will require cross-origin isolation as of M91, around May 2021. See https://developer.chrome.com/blog/enabling-shared-array-buffer/ for more details.", source: http://localhost:7357/59787911301/tmp-test-bundle.js (2)
            
            
        browser log: |
            {"type":"error","text":"Error: Browser exited unexpectedly"}
            {"type":"error","text":"[0516/174119.736985:ERROR:gpu_init.cc(426)] Passthrough is not supported, GL is egl\n[0516/174120.448800:INFO:CONSOLE(2)] \"SharedArrayBuffer will require cross-origin isolation as of M91, around May 2021. See https://developer.chrome.com/blog/enabling-shared-array-buffer/ for more details.\", source: http://localhost:7357/59787911301/tmp-test-bundle.js (2)\n"}

More about the problem here: https://developer.chrome.com/blog/enabling-shared-array-buffer/

Testem, when serving needs to send additional headers

[runspired]

Similarly, all testem versions > 3.4.0 seem to be affected by this. Not sure why newer testem results in newer chrome and/or bumping into this.

[johanneswuerbach]

As far as I know testem isn't using SharedArrayBuffer, are you using this in your code?

Reading https://developer.chrome.com/blog/enabling-shared-array-buffer/ and
https://developer.mozilla.org/en-US/docs/Web/HTTP/Cross-Origin_Resource_Policy_(CORP) it seems using SharedArrayBuffer requires setting Cross-Origin-Embedder-Policy: require-corp and Cross-Origin-Opener-Policy: same-origin, but seems like a breaking change so would need to be an opt-in feature 🤔

Why now?

Seems like they did a change in Chrome 103, which is what I get on the stable channel.