-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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
src: lock the thread properly in snapshot builder #56327
Conversation
Otherwise it can crash DCHECK when V8 expects that at least someone is locking the current thread.
Review requested:
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #56327 +/- ##
=======================================
Coverage 88.54% 88.54%
=======================================
Files 657 657
Lines 190295 190394 +99
Branches 36536 36544 +8
=======================================
+ Hits 168491 168582 +91
- Misses 14981 14991 +10
+ Partials 6823 6821 -2
|
Just to help me understand, do we have to lock because of this check? |
This comment was marked as outdated.
This comment was marked as outdated.
Yes, it's not technically serious for us to not lock it because we don't have other threads trying to take over the isolate here, but V8 uses it as a shortcut for current thread check, so it's needed to circumvent the DHCECK. |
This comment was marked as outdated.
This comment was marked as outdated.
Landed in 7c3aa9f |
Otherwise it can crash DCHECK when V8 expects that at least someone is locking the current thread.
Fixes: nodejs/node-v8#294