-
Notifications
You must be signed in to change notification settings - Fork 262
Description
Describe the bug
Failed to construct transformer: RuntimeError: memory access out of bounds
at https://w-credentialless-staticblitz.com/internal_bindings_bg.5a421e5b.wasm:wasm-function[341]:0x747ee
at new _0x48529e (https://sb1fkfsa84v-uwgz.w-credentialless-staticblitz.com/blitz.5a421e5b.js:40:272996)
at new _0x2caa7e (https://sb1fkfsa84v-uwgz.w-credentialless-staticblitz.com/blitz.5a421e5b.js:40:849292)
at new Hash (https://sb1fkfsa84v-uwgz.w-credentialless-staticblitz.com/builtins.8cb5228f.js:70:945)
at createHash (https://sb1fkfsa84v-uwgz.w-credentialless-staticblitz.com/builtins.8cb5228f.js:24:2531)
at sha1hex (file:///home/projects/sb1-fkfsa84v/node_modules/metro-file-map/src/worker.js#cjs:24:10)
at Object.worker (file:///home/projects/sb1-fkfsa84v/node_modules/metro-file-map/src/worker.js#cjs:80:12)
at execFunction (file:///home/projects/sb1-fkfsa84v/node_modules/jest-worker/build/workers/processChild.js#cjs:149:17)
at execHelper (file:///home/projects/sb1-fkfsa84v/node_modules/jest-worker/build/workers/processChild.js#cjs:137:5)
at execMethod (file:///home/projects/sb1-fkfsa84v/node_modules/jest-worker/build/workers/processChild.js#cjs:140:5) {
type: 'RuntimeError'
}
Link to the blitz that caused the error
https://stackblitz.com/edit/sb1-fkfsa84v?file=.env
Steps to reproduce
Application doesn't execute
Expected behavior
Application should be working
Parity with Local
- I have run the project in my local machine and I could not reproduce the issue.
Screenshots
Failed to construct transformer: RuntimeError: memory access out of bounds
Platform
Browser name = Chrome
Full version = 134.0.0.0
Major version = 134
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36
performance.memory = {
"totalJSHeapSize": 84045119,
"usedJSHeapSize": 75144447,
"jsHeapSizeLimit": 4294705152
}
Hash = 5a421e5b
Additional context
No response