-
Notifications
You must be signed in to change notification settings - Fork 29.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
deps: backport 8d6a228 from the v8's upstream #4259
deps: backport 8d6a228 from the v8's upstream #4259
Conversation
Original commit message: [heap] fix crash during the scavenge of ArrayBuffer Scavenger should not attempt to visit ArrayBuffer's storage, it is a user-supplied pointer that may have any alignment. Visiting it, may result in a crash. BUG= R=jochen Review URL: https://codereview.chromium.org/1406133003 Cr-Commit-Position: refs/heads/master@{#31611} PR-URL: #3549 Reviewed-By: Trevor Norris <trev.norris@gmail.com>
The upstream patch included a condition for + } else if (target->IsBytecodeArray()) {
+ IterateAndMarkPointersToFromSpace(
+ target, obj_address + BytecodeArray::kConstantPoolOffset,
+ obj_address + BytecodeArray::kHeaderSize, record_slots, callback); |
@zcbenz you are absolutely right. Thanks for catching this! |
Original commit message: [heap] fix crash during the scavenge of ArrayBuffer Scavenger should not attempt to visit ArrayBuffer's storage, it is a user-supplied pointer that may have any alignment. Visiting it, may result in a crash. BUG= R=jochen Review URL: https://codereview.chromium.org/1406133003 Cr-Commit-Position: refs/heads/master@{nodejs#31611} PR-URL: nodejs#3549 Reviewed-By: Trevor Norris <trev.norris@gmail.com>
f64194b
to
65c6208
Compare
Force pushed, PTAL |
Seems to be just one unrelated failure on fedora, otherwise CI is green. @ofrobots does this PR still look good to you? |
I get gateway timeouts on the tap results page for the CI so I cannot verify that the failure is unrelated . LGTM, otherwise. |
Rubber stamp LGTM. @indutny ... should this go into LTS? |
@jasnell I don't think so, we just forgot to cherry-pick it when upgrading V8 somewhere after LTS (AFAIK) |
Landed in 36ac3d6, thank you! |
Original commit message: [heap] fix crash during the scavenge of ArrayBuffer Scavenger should not attempt to visit ArrayBuffer's storage, it is a user-supplied pointer that may have any alignment. Visiting it, may result in a crash. BUG= R=jochen Review URL: https://codereview.chromium.org/1406133003 Cr-Commit-Position: refs/heads/master@{#31611} PR-URL: #4259 Reviewed-By: Ali Ijaz Sheikh <ofrobots@google.com> Reviewed-By: James M Snell <jasnell@gmail.com>
@jasnell: I missed this commit when upgrading from V8 4.6 to V8 4.7 😰. This is not needed in stable or LTS. |
@ofrobots I've added dont-land-on-v4.x please let me know if this should be changed |
Original commit message: [heap] fix crash during the scavenge of ArrayBuffer Scavenger should not attempt to visit ArrayBuffer's storage, it is a user-supplied pointer that may have any alignment. Visiting it, may result in a crash. BUG= R=jochen Review URL: https://codereview.chromium.org/1406133003 Cr-Commit-Position: refs/heads/master@{nodejs#31611} PR-URL: nodejs#4259 Reviewed-By: Ali Ijaz Sheikh <ofrobots@google.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Original commit message:
PR-URL: #3549
Reviewed-By: Trevor Norris trev.norris@gmail.com
cc @nodejs/v8