chrome webworkers OOM (windows/macos exclusive)

[9001]

this issue will be tracked here: https://issues.chromium.org/issues/383568268

one of the chrome memleaks are back, but this time with slightly different behavior:

• doesn't matter if it's http or https, crashes either way
• doesn't matter if it's cryptosubtle or wasm-hashing, crashes either way
• only happens on nonlocal websites; 127.0.0.1 does not crash
• only happens with webworkers enabled; mt off is fine
• appears to be windows and macos only; not linux (??)
  • definitely happens on windows (chrome-beta 132.0.6834.32)
  • chrome-stable (131.0.6778.140) rapidly hits same memory usage, but does not OOM; oscillates around peak ram usage while doing productive work
  • definitely happens on macos (chrome-stable 131.0.6778.140)
  • does NOT occur with chromium 131.0.6778.108 @ archlinux
  • does NOT occur with chromium 131.0.6778.85 @ fedora
• seen during a filesearch for a collection of 13 files with sizes ranging from 1 to 8 GiB each, so not related to uploading

mre:

• https://ocv.me/stuff/bugs/chrome/worker-gc/v2/ reproduces this every time; rapid leak into oom with no sign of gc
• https://ocv.me/stuff/bugs/chrome/worker-wasm-leak/ (orig/var2/var3) does NOT reproduce it; gc correctly kicks in when ram usage exceeds 8 GiB
• https://ocv.me/stuff/bugs/chrome/crypto-subtle-mt/ (v1/v2) does not leak at all, confirming filesystem-related

when the issue occurs, copyparty crashes loudly with the browser leak modal, but the mre crashes more silently -- usually the mre html/dom continues looking just fine, but the hashing thread dies in the background, dropping cpu load to 0% while keeping ram usage peaked

best way to avoid this browser bug is probably conditionally disabling webworkers for chrome-based browsers, maybe only desktop if phones are unaffected