Repository navigation
Flaky crash on worker-addon-exit test #63923
Description
Activity
It was also reported in #63642 (comment), the PR that introduced this test. Looks like the test failed in that PR (https://ci.nodejs.org/job/node-test-commit-linux-containered/56671/nodes=ubi81_sharedlibs_openssl111fips_x64/console) but it wasn't noticed during review unfortunately
[110:37|% 100|+ 600000|- 0]: Done
All tests passed.
600k runs without a reproduction 😓 It would be lovely to get a better stack trace here for actually pinpointing where this is coming from. I guess the simplest fix would be to use an async cleanup hook instead of the synchronous one, where the current Environment* isn't required to be on-context, but this does admittedly point to a bit of a usability problem with cleanup hooks in their current form
Happened to have a debug build around and could reproduce it with: tools/test.py -j32 --repeat=128 addons/worker-addon-exit/test.js. It seems to me your assessment is correct: when gc runs we're not in-context anymore. Here's the bt: https://github.com/proxy/gist.github.com/santigimeno/0cb38039629aeca161c8656442aca96f. Let me know if you need more info (I have the coredump)
#63985 should hopefully address this
Test
worker-addon-exit
Platform
No response
Console output
Build links
Additional information
Looking at https://github.com/nodejs/reliability/issues?q=is%3Aissue%20state%3Aopen%20addons%2Fworker-addon-exit%2Ftest, it seems to be happening since June 6th