Investigate flaky addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-binary on FreeBSD 11 #22317
Labels
buffer
Issues and PRs related to the buffer subsystem.
flaky-test
Issues and PRs related to the tests with unstable failures on the CI.
freebsd
Issues and PRs related to the FreeBSD platform.
Refs: nodejs/reliability#12
Example stack:
This only happens on FreeBSD 11 nodes. The process gets killed when allocating the external string so it's probably our code hitting the resource limit and killed by the system - but it's supposed to check carefully not to hit the limit and throw proper errors instead of crashing.
See output of `--trace_gc --trace_gc_verbose`
#22301 fixes it temporarily by calling
global.gc()
to force V8 release the string along with the external memory so that it does not hit the resource limit, hence it won't be killed by the system even though that's what we are supposed to test (that it returns early before being killed).The text was updated successfully, but these errors were encountered: