macOS 11.2: Fatal error `Check failed: allocator->SetPermissions`

[andreialecu]

• Version: v15.6.0
• Platform: Darwin Andreis-Mac-mini.local 20.3.0 Darwin Kernel Version 20.3.0: Thu Jan 14 14:38:22 PST 2021; root:xnu-7195.81.2~2/RELEASE_ARM64_T8101 arm64
• Subsystem: wasm(?)

What steps will reproduce the bug?

Use latest macOS Beta 11.2 (released 24 Jan 2021) and node 15.6.0

npm install -g yarn
cd `mktemp -d`
yarn init -2
yarn add lodash

How often does it reproduce? Is there a required condition?

All the time.

What is the expected behavior?

No crash.

What do you see instead?

#
# Fatal error in , line 0
# Check failed: allocator->SetPermissions(reinterpret_cast<void*>(region.begin()), region.size(), PageAllocator::kNoAccess).
#
#
#
#FailureMessage Object: 0x16f986408
 1: 0x100575758 node::NodePlatform::GetStackTracePrinter()::$_3::__invoke() [/Users/andreialecu/.nvm/versions/node/v15.6.0/bin/node]
 2: 0x1012bdd50 V8_Fatal(char const*, ...) [/Users/andreialecu/.nvm/versions/node/v15.6.0/bin/node]
 3: 0x100c0fb98 v8::internal::wasm::WasmCodeManager::Decommit(v8::base::AddressRegion) [/Users/andreialecu/.nvm/versions/node/v15.6.0/bin/node]
 4: 0x100c13218 v8::internal::wasm::NativeModule::FreeCode(v8::internal::Vector<v8::internal::wasm::WasmCode* const>) [/Users/andreialecu/.nvm/versions/node/v15.6.0/bin/node]
 5: 0x100c22400 v8::internal::wasm::WasmEngine::FreeDeadCodeLocked(std::__1::unordered_map<v8::internal::wasm::NativeModule*, std::__1::vector<v8::internal::wasm::WasmCode*, std::__1::allocator<v8::internal::wasm::WasmCode*> >, std::__1::hash<v8::internal::wasm::NativeModule*>, std::__1::equal_to<v8::internal::wasm::NativeModule*>, std::__1::allocator<std::__1::pair<v8::internal::wasm::NativeModule* const, std::__1::vector<v8::internal::wasm::WasmCode*, std::__1::allocator<v8::internal::wasm::WasmCode*> > > > > const&) [/Users/andreialecu/.nvm/versions/node/v15.6.0/bin/node]
 6: 0x100c20108 v8::internal::wasm::WasmEngine::PotentiallyFinishCurrentGC() [/Users/andreialecu/.nvm/versions/node/v15.6.0/bin/node]
 7: 0x100c2157c v8::internal::wasm::WasmEngine::ReportLiveCodeForGC(v8::internal::Isolate*, v8::internal::Vector<v8::internal::wasm::WasmCode*>) [/Users/andreialecu/.nvm/versions/node/v15.6.0/bin/node]
 8: 0x100c23d20 v8::internal::wasm::(anonymous namespace)::WasmGCForegroundTask::RunInternal() [/Users/andreialecu/.nvm/versions/node/v15.6.0/bin/node]
 9: 0x100573bf4 node::PerIsolatePlatformData::RunForegroundTask(std::__1::unique_ptr<v8::Task, std::__1::default_delete<v8::Task> >) [/Users/andreialecu/.nvm/versions/node/v15.6.0/bin/node]
10: 0x10057288c node::PerIsolatePlatformData::FlushForegroundTasksInternal() [/Users/andreialecu/.nvm/versions/node/v15.6.0/bin/node]
11: 0x100d551a8 uv__async_io [/Users/andreialecu/.nvm/versions/node/v15.6.0/bin/node]
12: 0x100d66d68 uv__io_poll [/Users/andreialecu/.nvm/versions/node/v15.6.0/bin/node]
13: 0x100d55638 uv_run [/Users/andreialecu/.nvm/versions/node/v15.6.0/bin/node]
14: 0x100472bd0 node::SpinEventLoop(node::Environment*) [/Users/andreialecu/.nvm/versions/node/v15.6.0/bin/node]
15: 0x10054caf4 node::NodeMainInstance::Run(node::EnvSerializeInfo const*) [/Users/andreialecu/.nvm/versions/node/v15.6.0/bin/node]
16: 0x1004ecc20 node::Start(int, char**) [/Users/andreialecu/.nvm/versions/node/v15.6.0/bin/node]
17: 0x199435f34 start [/usr/lib/system/libdyld.dylib]

Additional information

This started happening after the macOS beta update I think. I was on beta before, but everything was working fine until after the update.

I'm on an ARM64 M1 chip (mac mini 16gb ram)

node/deps/v8/src/wasm/wasm-code-manager.cc

Lines 1630 to 1631 in 770d9e2

	CHECK(allocator->SetPermissions(reinterpret_cast<void*>(region.begin()),
	region.size(), PageAllocator::kNoAccess));

[andreialecu]

Some additional information:

• It appears that nodejs 15.6 runs on v8 8.6, sharing the same V8 version with Chromium 86.
• I installed Chromium 86 to test WASM, and it crashes there too.
• However, Chromium 88+ which use v8 8.8 do not have the crash.

See microsoft/vscode#113410 (comment) for more details.

[GautierT]

@andreialecu : did you find a workaround ? Thanks !

[andreialecu]

Unfortunately no. I had to revert to nodejs 14, using Rosetta. Hopefully only temporarily.

arch -x86_64 zsh

nvm install 14
nvm alias default 14
exit

[GautierT]

yes i did the same but sad to have to use back Rosetta... Thanks.

[EriksRemess]

Same crash happens on latest MacOS 11.2 RC2 (20D62).

Update:
Node v15.7.0 released today has the same issue.

[MarcoZehe]

Thanks for filing this and investigating the cause, @andreialecu . I am running into this when trying to run the Netlify CLI.

[matinzd]

I also have this problem on apple silicon node v 15.7.0.

System info

Darwin Matins-MacBook-Pro.local 20.3.0 Darwin Kernel Version 20.3.0: Thu Jan 14 14:38:22 PST 2021; root:xnu-7195.81.2~2/RELEASE_ARM64_T8101 arm64

Error:

$ react-native start

#
# Fatal error in , line 0
# Check failed: allocator->SetPermissions(reinterpret_cast<void*>(region.begin()), region.size(), PageAllocator::kNoAccess).
#
#
#
#FailureMessage Object: 0x16efd4748
 1: 0x100f09044 node::NodePlatform::GetStackTracePrinter()::$_3::__invoke() [/opt/homebrew/Cellar/node/15.7.0/bin/node]
 2: 0x101890fdc V8_Fatal(char const*, ...) [/opt/homebrew/Cellar/node/15.7.0/bin/node]

[panr]

Big Sur 11.2 RC3 doesn't change anything. Still get the same error...

[andreialecu]

@aduh95 apologies for tagging you on this, but given your mac arm64 commits, perhaps you would know who to forward this to since it is a very serious problem.

11.2 will be out any day now and this will hit a lot of people.

[panr]

I just reported this directly to Apple. Will see what happens...