Skip to content
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: V8: workaround V8 leak w track constant fields #28740

Closed
wants to merge 1 commit into from

Conversation

ofrobots
Copy link
Contributor

track_constant_fields exposes a large regression in memory leak due
to a suspected memory leak. Disable this until a proper fix is ready.

Ref: https://bugs.chromium.org/p/v8/issues/detail?id=9507
Ref: #28205

/cc @hashseed @filipesilva

This needs to be backported to v12 once this lands.

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • commit message follows commit guidelines

track_constant_fields exposes a large regression in memory leak due
to a suspected memory leak. Disable this until a proper fix is ready.

Ref: https://bugs.chromium.org/p/v8/issues/detail?id=9507
Ref: nodejs#28205
@nodejs-github-bot nodejs-github-bot added build Issues and PRs related to build files or the CI. v8 engine Issues and PRs related to the V8 dependency. labels Jul 17, 2019
@ofrobots
Copy link
Contributor Author

/cc @ulan

@ofrobots
Copy link
Contributor Author

Root cause turned out to be a bug in angular (see #28205 (comment)). Abandoning.

@ofrobots ofrobots closed this Jul 18, 2019
@ofrobots ofrobots deleted the fix/28205 branch July 18, 2019 16:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Issues and PRs related to build files or the CI. v8 engine Issues and PRs related to the V8 dependency.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants