Chrome Deprecation warning: SharedArrayBuffer will require cross-origin isolation as of M91

Running TFJS 3.5.0 with WASM backend and SIMD & multithreading enabled results in warnings in browser console:

[Deprecation] 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.

  (anonymous)	@	flags_wasm.ts:49
  evaluateFlag	@	environment.ts:141
  getAsync	@	environment.ts:88

Which happens in internal WASM test in flags_wasm.ts:

// Test for transferability of SABs (needed for Firefox)
// https://groups.google.com/forum/#!msg/mozilla.dev.platform/IHkBZlHETpA/dwsMNchWEQAJ
new MessageChannel().port1.postMessage(new SharedArrayBuffer(1));
// This typed array is a WebAssembly program containing threaded
// instructions.
return WebAssembly.validate(new Uint8Array([
  0, 97, 115, 109, 1, 0,  0,  0, 1, 4, 1,  96, 0,   0,  3, 2, 1,  0, 5,
  4, 1,  3,   1,   1, 10, 11, 1, 9, 0, 65, 0,  254, 16, 2, 0, 26, 11
]));

Environment: TFJS 3.5.0 with Edge/Chromium 90 on Windows 10 with WASM backend (SIMD and MultiThreading enabled)

[jinjingforever]

Hi @SukkaW, without cross-origin isolation, the wasm baskend will fallback to simd only (without multi-threading support).

[jinjingforever]

@huningxin We set up a new benchmark site that has the cross-origin isolation set up: https://tfjs-benchmarks.web.app/local-benchmark/. Thanks!