-
Notifications
You must be signed in to change notification settings - Fork 7.3k
jslint segfaults in v0.11.7 #6201
Comments
Can you try this?
Can you post the backtrace here? |
Sorry, this is a bit late, but here you go.
|
NOTE: This is from the latest github version. 3d4c663 |
Confirmed, thanks. Not sure yet what exactly is causing it but I'm reasonably sure it's a regression introduced by the recent vm2 changes. If you go back a few commits, you get the following backtrace with
|
Update: the regression was introduced in a3bf3d1 ("vm: use MakeWeak to fix leaking contexts"). |
If you don't mind, I'll look into it. Also, I'm cut-off from IRC for a couple of days, so please use email for contacting me ;) |
Don't worry, I'm pretty sure I've found and fixed the issue. I'll open a pull request in a few for you guys to review once I'm sure it's not causing regressions. |
Okay, after some more investigation I've come to the conclusion that there are a couple of fundamental issues with the vm2 module that probably require a fair amount of rework to fix. I'm moving to revert it for now in #6228 and re-roll in v0.13. |
Apparently, context->Global() won't be destroyed if the context itself isn't marked as weak and independent. Also, the weakness flag should be cleared once the weak callback is executed, otherwise we'll get crashes in Debug builds. fix nodejs#6115 and nodejs#6201
Closing, this was fixed last month in 59a075e. |
Starting from scratch I compiled node and npm both from the truck and then from v0.11.7 and tried installing and running jslint.
It simply segfaults and doesn't provide any other information.
The text was updated successfully, but these errors were encountered: