Investigate persistent Windows test failure on test.wasi/test-return-on-exit

[Trott]

• Test: test.wasi/test-return-on-exit
• Platform: win2012r2
• Console Output:

00:30:50 not ok 778 wasi/test-return-on-exit # TODO : Fix flaky test
00:30:50   ---
00:30:50   duration_ms: 49.248
00:30:50   severity: flaky
00:30:50   exitcode: 134
00:30:50   stack: |-
00:30:50     (node:972) ExperimentalWarning: WASI is an experimental feature. This feature could change at any time
00:30:50     (Use `node --trace-warnings ...` to show where the warning was created)
00:30:50     
00:30:50     <--- Last few GCs --->
00:30:50     
00:30:50     
00:30:50     <--- JS stacktrace --->
00:30:50     
00:30:50     FATAL ERROR: Zone Allocation failed - process out of memory
00:30:50   ...

• Build Links:

https://ci.nodejs.org/job/node-test-binary-windows-js-suites/8229/RUN_SUBSET=3,nodes=win2012r2-COMPILED_BY-vs2019-x86/console and pretty much any other recent Jenkins CI run as the failure is persistent.

[Trott]

Refs: #36139 (comment)

[Trott]

@nodejs/platform-windows

[Trott]

Since this apparently started happening with the V8 update to 8.8: @nodejs/v8

[targos]

Also @nodejs/wasi

[targos]

There's probably a real bug somewhere, because this only happens on a 32 bit system.

[Trott]

There's probably a real bug somewhere, because this only happens on a 32 bit system.

Any thoughts on how we can make some progress on this?

[Trott]

Refs: #36139 (comment)

@gengjiawen Any ideas on what to do here?