Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

512
Views
Nodejs with macOS: # Fatal error in , line 0 - gatsby develop

I am using gatsby cli, Suddenly gatsby develop command returning an error even if I create new site from scratch. I am using M1 macbook pro with big sur, is there anyone faced same issue? if yes how to resolve this?. I have configured everything properly by following official doc, am I missing something? here is my terminal screenshot

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

Parts of the stacktrace:

#
# 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() 
...
over 4 years ago · Santiago Trujillo
3 answers
Answer question

0

It seems a Node-related issue. According to this GitHub thread, try:

arch -x86_64 zsh

nvm install 14
nvm alias default 14
exit

All the solutions are related to the Node version. Remember to clean your cache by running gatsby clean and removing the node_modules in each trial.

As other threads points the issue seems to be related to the latest Node version. With the snippet above you'll roll back to version 14 as a temporal workaround while the issue is being fixed.

over 4 years ago · Santiago Trujillo Report

0

This was fixed in Node v15.9.0 If you installled using homebrew on a mac you can do brew upgrade node to get the latest version

over 4 years ago · Santiago Trujillo Report

0

Unfortunately the only solution is to revert to nodejs 14, using Rosetta.

Additional here's the issue in V8: https://bugs.chromium.org/p/v8/issues/detail?id=11389

No ETA. Everyone, please stop asking for when this will be resolved. We know about the issue and are working on it.

Also note that Node.js is still not officially supported on macOS+arm64. We do not produce binaries for it and you can use the x64 ones in the mean time.

https://github.com/nodejs/node/issues/37061#issuecomment-772559363

over 4 years ago · Santiago Trujillo Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!