You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.
I just happened to notice that node v0.12 ships V8 3.28.73. That's a pretty bad choice, as 3.28.73 was just a random trunk snapshot that was briefly considered as the basis for the 3.28 branch, but was then discarded/abandoned because it was too unstable. The tip of the branch is 3.28.71.19: https://chromium.googlesource.com/v8/v8.git/+/branch-heads/3.28
While the 3.28 branch is generally outdated and hence unmaintained anyway, at least using its tip is very strongly preferable over using a random trunk commit from shortly after the branch point. To be very clear: There are known crash and security bugs in 3.28.73 that are fixed in 3.28.71.19!
The text was updated successfully, but these errors were encountered:
I just happened to notice that node v0.12 ships V8 3.28.73. That's a pretty bad choice, as 3.28.73 was just a random trunk snapshot that was briefly considered as the basis for the 3.28 branch, but was then discarded/abandoned because it was too unstable. The tip of the branch is 3.28.71.19: https://chromium.googlesource.com/v8/v8.git/+/branch-heads/3.28
While the 3.28 branch is generally outdated and hence unmaintained anyway, at least using its tip is very strongly preferable over using a random trunk commit from shortly after the branch point. To be very clear: There are known crash and security bugs in 3.28.73 that are fixed in 3.28.71.19!
The text was updated successfully, but these errors were encountered: