mirror of
https://github.com/nodejs/node.git
synced 2024-11-21 10:59:27 +00:00
src,test: disable freezing V8 flags on initialization
Node.js still changes flags after initializationg; either because tests need to set their own flags (which V8 tests also still allow), or because it's explicitly requested via the "v8.setFlagsFromString" method that Node.js provides. PR-URL: https://github.com/nodejs/node/pull/44741 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Jiawen Geng <technicalcute@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
This commit is contained in:
parent
fd52c62bee
commit
2e49b99cc2
@ -741,6 +741,11 @@ static ExitCode InitializeNodeWithArgsInternal(
|
||||
// used in diagnostic reports.
|
||||
per_process::cli_options->cmdline = *argv;
|
||||
|
||||
// Node provides a "v8.setFlagsFromString" method to dynamically change flags.
|
||||
// Hence do not freeze flags when initializing V8. In a browser setting, this
|
||||
// is security relevant, for Node it's less important.
|
||||
V8::SetFlagsFromString("--no-freeze-flags-after-init");
|
||||
|
||||
#if defined(NODE_V8_OPTIONS)
|
||||
// Should come before the call to V8::SetFlagsFromCommandLine()
|
||||
// so the user can disable a flag --foo at run-time by passing
|
||||
|
@ -24,6 +24,11 @@ void NodeTestEnvironment::SetUp() {
|
||||
#endif
|
||||
cppgc::InitializeProcess(
|
||||
NodeZeroIsolateTestFixture::platform->GetPageAllocator());
|
||||
|
||||
// Before initializing V8, disable the --freeze-flags-after-init flag, so
|
||||
// individual tests can set their own flags.
|
||||
v8::V8::SetFlagsFromString("--no-freeze-flags-after-init");
|
||||
|
||||
v8::V8::Initialize();
|
||||
}
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user