-
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
Abort during Object.keys after vm.runInContext #22723
Comments
looks like #22390 is to blame, reverting those commits makes it happy again. |
I’m okay with reverting #22390 for now, though this looks like a V8 issue. /cc @camillobruni |
Agreed. Let's revert 22390. |
Could you rule out an issue on node side? |
Hmm, upon a further look this might be caused by our indexed enumerator returning non-integers. Will take a closer look. |
thanks! |
@TimothyGu Any updates? Should we revert for now? |
Adding the 11.0.0 milestone so we don't release this bug by mistake |
@addaleax Yeah, reverting is the best idea for now. |
Potential fix in #22836 :) |
This reverts commit 85c356c from PR nodejs#22390. See the discussion in the (proposed) fix at nodejs#22836. Refs: nodejs#22836 Refs: nodejs#22390 Fixes: nodejs#22723
Some of the choices here are odd, including that symbols are missing. However, that matches previous behaviour. What had to be changed was that inherited properties are no longer included; the alternative would be to also refactor the descriptor callbacks to provide data for inherited properties. Fixes: nodejs#22723 Refs: nodejs#22390
This occurs in both master and v10.x-staging but didn't repro in 10.9.0
Here's the llnode backtrace:
The text was updated successfully, but these errors were encountered: