-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
deps: remove extra field from v8::HeapStatistics #7526
Conversation
Remove the `_malloced_memory` field from the `HeapStatistics` class to achieve full ABI compatibility with V8 5.0. Ref: nodejs#7016
LGTM, I guess. Any chance V8 would accept this? |
Yeah, this should likely be pushed up stream first. |
@bnoordhuis +1 SGTM! |
Landed in 4c774e1 |
@addaleax Is this supposed to land on v6 but not v7? |
@addaleax Correct, but wouldn't we want this new field for V7? |
for v7 we will have a new version of V8. The process of upgrading V8 to a new major version cancels all patches that we apply to |
Remove the `_malloced_memory` field from the `HeapStatistics` class to achieve full ABI compatibility with V8 5.0. Ref: nodejs#7016 PR-URL: nodejs#7526 Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: James M Snell <jasnell@gmail.com>
Checklist
make -j4 test
(UNIX), orvcbuild test nosign
(Windows) passesAffected core subsystem(s)
deps/v8
Description of change
Remove the
_malloced_memory
field from theHeapStatistics
class to achieve full ABI compatibility with V8 5.0 (as far as I can tell).This structure is probably not something used by addons anyway, since the information from that struct is already made available through Node’s
v8.getHeapStatistics()
, but better safe than sorry.Ref: #7016 (comment) (and it would need to be landed in v6 together with #7016).
/cc @ofrobots @nodejs/v8