WebAssembly "Out of memory: wasm memory" bug
See original GitHub issueSteps to reproduce: I can’t provide any steps to reproduce. I’ve just been changing the code in my environment with Hot Module Reloading and at one point I was getting tis error. I doesn’t happen when I open a new incognito tab and run the same code.
Error log
ERROR: Unable to initialize @polkadot/wasm-crypto:: WebAssembly Instantiation: Out of memory: wasm memory
| __stack_frame_overlay_proxy_console__ | @ | index.js:2178
-- | -- | -- | --
| createExportPromise | @ | wasm_bg.js:23
| async function (async) | |
| createExportPromise | @ | wasm_bg.js:19
| ./node_modules/@polkadot/wasm-crypto/wasm.js | @ | wasm.js:789
| __webpack_require__ | @ | bootstrap:788
| fn | @ | bootstrap:149
| ./node_modules/@polkadot/wasm-crypto/index.js | @ | index.js:6
| __webpack_require__ | @ | bootstrap:788
| fn | @ | bootstrap:149
| ./node_modules/@polkadot/util-crypto/index.js | @ | index.js:15
| __webpack_require__ | @ | bootstrap:788
| fn | @ | bootstrap:149
| ./node_modules/@polkadot/keyring/index.js | @ | index.js:30
| __webpack_require__ | @ | bootstrap:788
| fn | @ | bootstrap:149
| ./node_modules/@polkadot/ui-identicon/Identicon.js | @ | Identicon.js:16
| __webpack_require__ | @ | bootstrap:788
| fn | @ | bootstrap:149
| ./node_modules/@polkadot/ui-identicon/index.js | @ | index.js:11
| __webpack_require__ | @ | bootstrap:788
| fn | @ | bootstrap:149
| ./pages/index.js | @ | xxhash64.js:444
| __webpack_require__ | @ | bootstrap:788
| fn | @ | bootstrap:149
| (anonymous) | @ | next-client-pages-loader.js:3
| register | @ | page-loader.js:149
| registerPage | @ | page-loader.js:191
| register | @ | index.js:94
| ./node_modules/next/dist/build/webpack/loaders/next-client-pages-loader.js?page=%2F&absolutePagePath=%2FUsers%2Fstefaniedoll%2FParity%2FCustom%2Fsubstrate-nextjs%2Fpages%2Findex.js!./ | @ | next-client-pages-loader.js:2
| __webpack_require__ | @ | bootstrap:788
| fn | @ | bootstrap:149
| 6 | @ | crypto (ignored)?a400:1
| __webpack_require__ | @ | bootstrap:788
| checkDeferredModules | @ | bootstrap:45
| webpackJsonpCallback | @ | bootstrap:32
| (anonymous)
Tech Stack:
"dependencies": {
"@babel/plugin-proposal-export-default-from": "^7.2.0",
"@now/next": "^0.1.2",
"@polkadot/api": "^0.76.0-beta.2",
"@polkadot/keyring": "^0.76.0-beta.2",
"@polkadot/rpc-provider": "^0.76.0-beta.2",
"@polkadot/ui-identicon": "^0.36.1",
"@polkadot/util": "^0.76.0-beta.2",
"@polkadot/util-crypto": "^0.76.0-beta.2",
"@zeit/next-css": "^1.0.1",
"babel-plugin-module-resolver": "^3.2.0",
"create-subscription": "^16.8.6",
"dotenv-webpack": "^1.7.0",
"file-loader": "^3.0.1",
"next": "latest",
"react": "^16.7.0",
"react-dom": "^16.7.0",
"react-with-observable": "^2.0.1",
"semantic-ui-css": "^2.4.1",
"semantic-ui-react": "^0.86.0",
"url-loader": "^1.1.2"
}
Environment: Google Chrome 73.0.3683.86 (Official Build) (64-bit) Mac OS Mojave 10.14.3
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:12 (3 by maintainers)
Top Results From Across the Web
RangeError [Error]: WebAssembly.instantiate(): Out of memory ...
Running into this error when running in production. I have a use case where I'm running a non-api nodejs instance for crunching large ......
Read more >Chasing Memory Bugs through V8 and WebAssembly
This is telling us that each worker consumed around ~1MiB of memory for all its WebAssembly Memory instances. If we are profiling the...
Read more >RangeError: WebAssembly.Instance(): Out of memory: wasm ...
Getting error when compiling assets using (npx mix or npm run dev/prod). I have already tried reinstalling and different versions of node and ......
Read more >RangeError: WebAssembly.instantiate(): Out of memory: wasm ...
The error message suggests there is not enough memory available to execute the WebAssembly.instantiate() function (which seems to come from ...
Read more >Help me with WebAssembly.Instance(): Out of memory
I use cpanel, and when I try to build the project, I have this error: RangeError: WebAssembly.Instance(): Out of memory: wasm memory at ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Seems to be fixed in Chromium since may 2020 https://bugs.chromium.org/p/chromium/issues/detail?id=912153
Yup, exactly! 😃 Shall I close this or leave it as a reference in case others are experiencing the same behaviour?