| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
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}
|
LGTM. Didn't you already back port this? |
Sorry, something went wrong.
Sorry, something went wrong.
|
Cc @nodejs/lts |
Sorry, something went wrong.
|
Tagged... @Fishrock123 and @indutny , if possible, please use the lts-watch label. I'm working up a tool that'll help triage and cherry pick these kinds of commits in a more automated way and the label definitely helps with that 👍 |
Sorry, something went wrong.
|
I guess CI is looking good? cc @jasnell |
Sorry, something went wrong.
|
@indutny @Fishrock123 ... I'll be working up a new v4.x release today and tomorrow. How about I look to do a release candidate by tomorrow afternoon? Then cut the actual v4.2.2 release on Thursday or Monday assuming everything looks good with the RC? Or is this a much higher priority than that? |
Sorry, something went wrong.
|
Of course! Just be aware that this bug is already causing issues for one company, and they are waiting for the patch to deploy 4.x in their product. (Can't really name the company unless they will decide to comment on this themselves) |
Sorry, something went wrong.
|
Ok, I'll work on getting the final few commits landed into v4.x-staging today and will get the v4.2.2 Request Proposal put together this evening. I'll do a release candidate build tomorrow and we can go from there. If all goes well, we can hopefully get v4.2.2 out by Thursday but if there are any regressions it could slip to Monday because we definitely do not want to do a new LTS release on a Friday. |
Sorry, something went wrong.
|
@jasnell of course. Thank you for this! |
Sorry, something went wrong.
|
@indutny ... looking at cherry picking commits now. I can only pull over commits that have landed so please give me a ping when this one hits in master |
Sorry, something went wrong.
Sorry, something went wrong.
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>
|
Ok, I optimistically attempted to cherry pick it onto v4.x-staging and the commit definitely does not land cleanly. It'll need a bit of fixing up before it can land. @indutny, if you have the time I'd appreciate some help with that. |
Sorry, something went wrong.
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>
Sorry, something went wrong.
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>
Sorry, something went wrong.
|
Thank you, James! |
Sorry, something went wrong.
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>
|
I've had a go at backporting to v3.x @ 6a457bd for inclusion in v3.3.2, it seem to be still relevant for V8 4.4. |
Sorry, something went wrong.
|
Without much success, perhaps it's not a problem in V8 4.4 but I'd love confirmation if you have time @indutny: ../deps/v8/src/heap/heap.cc:5046:19: error: no member named 'ContentType' in 'v8::internal::HeapObject'
switch (target->ContentType()) {
~~~~~~ ^
1 error generated.
|
Sorry, something went wrong.
|
@rvagg this patch should not be backported to it. |
Sorry, something went wrong.
|
thanks, backing it out and pushing 3.3.2 forward |
Sorry, something went wrong.
|
@rvagg I will look into it deeply tomorrow to see if there should be any kind of other fix for 3.3.2 |
Sorry, something went wrong.
|
Belated LGTM. |
Sorry, something went wrong.
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>
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>
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>
| Back | FazBrowse Home | New Git URL |
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}This is very critical ArrayBuffer fix, and we should backport it to v4 and make a release.
R= @bnoordhuis
cc @nodejs/v8