Isopacket load failed on meteor start

I’m trying to start my project on centos 7 and it gives me the error WebAssembly.instantiate(): Out of memory: wasm memory

Here is everything else if you may need it:

Errors prevented isopacket load:

While loading isopacket combined:
error: WebAssembly.instantiate(): Out of memory: wasm memory

/home/digtlemperium/.meteor/packages/meteor-tool/.1.10.2.121ry7f.gueme++os.linux.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.linux.x86_64/dev_bundle/lib/node_modules/meteor-promise/promise_server.js:218
throw error;
^

Error: isopacket load failed?
at loadIsopacketFromDisk (/tools/tool-env/isopackets.js:320:11)
at /tools/tool-env/isopackets.js:113:9
at loadIsopackage (/tools/tool-env/isopackets.js:104:21)
at ProjectContext._buildResolver (/tools/project-context.js:817:34)
at /tools/project-context.js:530:29
at Object.enterJob (/tools/utils/buildmessage.js:388:12)
at /tools/project-context.js:529:20
at /tools/packaging/catalog/catalog.js:100:5
at Object.capture (/tools/utils/buildmessage.js:283:5)
at Object.catalog.runAndRetryWithRefreshIfHelpful (/tools/packaging/catalog/catalog.js:99:31)
at ProjectContext._resolveConstraints (/tools/project-context.js:528:13)
at /tools/project-context.js:300:9
at Object.enterJob (/tools/utils/buildmessage.js:388:12)
at ProjectContext._completeStagesThrough (/tools/project-context.js:290:18)
at /tools/project-context.js:260:12
at Function.run (/home/digtlemperium/.meteor/packages/meteor-tool/.1.10.2.121ry7f.gueme++os.linux.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.linux.x86_64/tools/tool-env/tools/tool-env/profile.ts:289:14)
at ProjectContext.resolveConstraints (/tools/project-context.js:259:13)
at /tools/runners/run-all.js:75:27
at Object.capture (/tools/utils/buildmessage.js:283:5)
at new Runner (/tools/runners/run-all.js:74:18)
at Object.exports.run (/tools/runners/run-all.js:365:16)
at Command.doRunCommand [as func] (/tools/cli/commands.js:438:17)
at /tools/cli/main.js:1528:15

Hi, I have the same problem, did you solve it?

A cursory search suggests this may be a Node issue. What version of Node is running?

In your project directory, what do you get when you type:

node -v