Issue
A user encounters the following error when runningnpm run start or npm run build:
RangeError: WebAssembly.Instance(): Out of memory: Cannot allocate Wasm memory
Environment
- CloudLinux
- Node.Js Selector
Solution
Verify that Node.Js is working by creating a test application.
If it is working, this issue is not directly related to CloudLinux.
It's important to note that Cloudlinux OS does not deploy the application and does not affect the file in any way. Also, the Nodejs selector only allows the user to work in his virtual environment to work with Nodejs, nothing more. It has no other specifics for setting up and handling files or applications.
As for this error:
[RangeError: WebAssembly.instantiate(): Out of memory: Cannot allocate Wasm memory for new instance]
we recommend reaching out to your developer or application provider. For reference, here are several related community discussions:
https://github.com/piscinajs/piscina/issues/158
https://github.com/webpack/webpack/issues/15584
https://github.com/vercel/next.js/issues/33858
https://community.n8n.io/t/failed-to-asynchronously-prepare-wasm-rangeerror-webassembly-instantiate-out-of-memory-wasm-memory/11779/6
Please note that we don't provide support for the issues that aren't related to our selectors (NodeJS / Python / Ruby), for example:
- Application installations or configuration.
- Setting up the environment variables for the application.
- Develop any additional software for the application.
- Installing dependencies for an application with the application-related commands, for example:
npm -i
npm install
pip install
- Any kind of application debugging, reconfiguration, or bug fix.
Comments
0 comments
Please sign in to leave a comment.