pyodide: RangeError: Maximum call stack size exceeded
π Bug
Trying to run pydantic-coreβs tests on wasm with node locally, and Iβm getting the following crash, tests are working ok on github CI. My local machine is an M1 mac.
============================= test session starts ==============================
platform emscripten -- Python 3.10.2, pytest-7.1.2, pluggy-1.0.0
rootdir: /test_dir
plugins: hypothesis-6.49.1, speed-0.3.1
collecting ... Pyodide has suffered a fatal error. Please report this to the Pyodide maintainers.
The cause of the fatal error was:
RangeError: Maximum call stack size exceeded
at getter_call_trampoline (/Users/samuel/code/pydantic-core/tests/node_modules/pyodide/pyodide.asm.js:7647:36)
at wasm://wasm/0244357a:wasm-function[1069]:0x137410
at wasm://wasm/0244357a:wasm-function[2223]:0x17ff94
at wasm://wasm/0244357a:wasm-function[1927]:0x16e527
at wasm://wasm/0244357a:wasm-function[1929]:0x16e7d5
at wasm://wasm/0244357a:wasm-function[703]:0x11c70f
at wasm://wasm/0244357a:wasm-function[702]:0x11c6bb
at wasm://wasm/0244357a:wasm-function[701]:0x11c542
at wasm://wasm/0244357a:wasm-function[2960]:0x1e0ea6
at wasm://wasm/0244357a:wasm-function[1851]:0x16b264 {
pyodide_fatal_error: true
}
RangeError: Maximum call stack size exceeded
at getter_call_trampoline (/Users/samuel/code/pydantic-core/tests/node_modules/pyodide/pyodide.asm.js:7647:36)
at wasm://wasm/0244357a:wasm-function[1069]:0x137410
at wasm://wasm/0244357a:wasm-function[2223]:0x17ff94
at wasm://wasm/0244357a:wasm-function[1927]:0x16e527
at wasm://wasm/0244357a:wasm-function[1929]:0x16e7d5
at wasm://wasm/0244357a:wasm-function[703]:0x11c70f
at wasm://wasm/0244357a:wasm-function[702]:0x11c6bb
at wasm://wasm/0244357a:wasm-function[701]:0x11c542
at wasm://wasm/0244357a:wasm-function[2960]:0x1e0ea6
at wasm://wasm/0244357a:wasm-function[1851]:0x16b264 {
pyodide_fatal_error: true
}
To Reproduce
See https://github.com/samuelcolvin/pydantic-core/pull/148 and in particular https://github.com/samuelcolvin/pydantic-core/pull/148/commits/782b64f54fa88351623739368fba16d5541ca588
Iβm just running those tests locally.
Expected behavior
no crash
Environment
- Pyodide Version:
0.21.0-alpha.2 - Browser version: node
v16.13.0 - Any other relevant information:
About this issue
- Original URL
- State: open
- Created 2 years ago
- Comments: 20 (8 by maintainers)
When I was seeing this, the error is more likely to happen when the devtools panel is closed - enabling devtools in chrome obviously changes the way JS is executed to allow introspection, there stopping the error (or making it less likely).