Skip to content

Explicitly set v8_enable_handle_zapping to false - #1188

Merged
littledivy merged 2 commits into
denoland:mainfrom
littledivy:v8_enable_handle_zapping
Feb 11, 2023
Merged

Explicitly set v8_enable_handle_zapping to false#1188
littledivy merged 2 commits into
denoland:mainfrom
littledivy:v8_enable_handle_zapping

Conversation

@littledivy

Copy link
Copy Markdown
Member

No description provided.

@ry ry left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add a comment that this is for perf

LGTM

@aapoalas

Copy link
Copy Markdown
Contributor

What is "handle zapping" actually?

@littledivy

littledivy commented Feb 11, 2023

Copy link
Copy Markdown
Member Author

@aapoalas IIUC zapping is rewriting a memory region with garbage (read it somewhere in a v8 issue).

-DENABLE_HANDLE_ZAPPING enables this bit of code: https://source.chromium.org/chromium/chromium/src/+/main:v8/src/handles/handles.cc;l=182;bpv=1;bpt=1?q=ENABLE_HANDLE_ZAPPING&ss=chromium%2Fchromium%2Fsrc

Also relevant Node.js PR: nodejs/node#23801

@littledivy
littledivy merged commit 6043e7d into denoland:main Feb 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants