Yes, even there. [0]

[0] https://github.com/nodejs/node/pulls?utf8=%E2%9C%93&q=is%3Ap...

node dev here - none of the prs here deal with segfaults from js code, because that doesn't really happen (at least, I've never seen it happen). You might have some more success searching V8's bug tracker.

This [0] one had a segfault in a JS test file.

[0] https://github.com/nodejs/node/pull/22273#issuecomment-41588...

it was not caused by a failure of the js vm though, it was caused (from what i can tell) by a failure in c++ tracing code.

V8 is not immune to memory corruption.