Michaël Zasso
Michaël Zasso
It looks like something is broken on the release builds too. Locally, I get this stack trace: ``` Process 239 launched: '/Users/mzasso/git/nodejs/v8-next-update/out/Release/node' (arm64) Process 239 stopped * thread #1, name...
Some tests with a log in `BuiltinLoader::CompileAndCall`: ``` $ out/Release/node Compiling and calling internal/main/repl [1] 15840 segmentation fault out/Release/node $ out/Release/node -p process.version Compiling and calling internal/main/eval_string [1] 15895 illegal...
I started a discussion on the Chromium Slack about the build issues. The DCHECK in the snapshot serializer happens with a value of type `InterceptorInfo`. This corresponds to the error...
Nice! I rebased and added your patch so we can try in CI.
CI looks good, modulo the usual build memory issues.
@joyeecheung thanks for the V8 patch! @nodejs/tsc @nodejs/v8-update This is ready for reviews.
Note that I'm unable to SSH into this machine.
We could try to setup `venv` like I did with https://github.com/nodejs/build/pull/3560 and https://github.com/nodejs/build/pull/3678
Stress test: https://ci.nodejs.org/view/Stress/job/node-stress-single-test/520/
I wish we were able to reproduce these more reliably, because I don't know how to debug something that only happens once or twice every 10k runs!