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 }}
Repository navigation
Setting __proto__ on vm context's globalThis causes a crash (regression in v19.9.0) #47798
Hey! I ran a git bisect seems like this problem arose in #46615, I confirmed reverting the commit fixes this regression, although it seems that PR solved quite a lot of bugs so probably can blanket revert it, I am trying to understand the code if anyone has any more context on it that would be great! cc @dubzzz
Indeed the PR is solving many regressions introduced with the bump of v8 done at the beginning of node 18. There were multiple attempts to fix it, but it seems we still miss some cases.
For the record, I have another PR attempting to fix some remaining issues: #47572. But it will probably not fix the one reported here. Maybe I can check if I see something that could solve the reported issue, we might have something missing in my last attempt of fix.
In the meantime, @domenic did you checked if you have the issue on the head of 18 (highly probable) and head of 20 (bump of v8 done with 20 fixed some issues).
Activity
targos commentedon May 1, 2023
Debug trace:
targos commentedon May 1, 2023
@nodejs/vm
Update Node.js minimum and dependencies
Update Node.js minimum and dependencies
Update Node.js minimum and dependencies
debadree25 commentedon May 5, 2023
Hey! I ran a git bisect seems like this problem arose in #46615, I confirmed reverting the commit fixes this regression, although it seems that PR solved quite a lot of bugs so probably can blanket revert it, I am trying to understand the code if anyone has any more context on it that would be great! cc @dubzzz
Thank You!
dubzzz commentedon May 5, 2023
Indeed the PR is solving many regressions introduced with the bump of v8 done at the beginning of node 18. There were multiple attempts to fix it, but it seems we still miss some cases.
For the record, I have another PR attempting to fix some remaining issues: #47572. But it will probably not fix the one reported here. Maybe I can check if I see something that could solve the reported issue, we might have something missing in my last attempt of fix.
In the meantime, @domenic did you checked if you have the issue on the head of 18 (highly probable) and
head of 20 (bump of v8 done with 20 fixed some issues).debadree25 commentedon May 5, 2023
looking at the stack trace I think this caused maybe because we are calling
GetPropertyDescriptor()on a null value maybe thats causing it?node/src/node_contextify.cc
Lines 530 to 533 in 03db049
dubzzz commentedon May 5, 2023
I have not read the stack yet but the null could be a good culprit. I'd rather suspect
node/src/node_contextify.cc
Lines 539 to 540 in 03db049
debadree25 commentedon May 5, 2023
You are correct, putting checked putting some printf's around 😄, I think this needs some additional check but dont know what that could be
dubzzz commentedon May 5, 2023
We should probably add a check for
IsNullbefore doing theAscast 🤔Something like:
That said, that's strange to receive null from a get property descriptor 🤔
debadree25 commentedon May 5, 2023
Oh ok, I doesnt actually return null, the condition is executed with even with this null check this part probably needs some check
node/src/node_contextify.cc
Lines 539 to 540 in 03db049
fix(vm): cachedData fingerprints, proxy sandboxes, module link errors