-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Call stack size exceeded of wasm asyncify #87
Comments
Can you try:
Then rebuild the WASM artifacts. You would need to follow the build instructions on the README. If you don't have the time or the background, I'll get around to it at some point. |
I tried here quolpr@7c0d9bd , but it didn't help. I suspect that this error is about JS VM stack error 🤔 |
Thanks for taking a look! I'm puzzled because I really thought one of those changes would fix it. I'll investigate myself when I can. This isn't a valid SQL(ite) statement, right? Not that it should produce a stack overflow, but I'm wondering if that is part of what triggers the issue. |
Nope, it's valid. You can run it with not asyncify build, or you can also paste it to here https://sql.js.org/examples/GUI/ . For me, it even fails with 1...100 range (in the example I used 1...200 VALUES). I used |
Thanks, I never knew you could use a bare VALUES clause as a statement. Is there a reason you need so many VALUES, as opposed to just: VALUES (0), (1), (2), ... The internal functions I think that explains why you're putting so much pressure on the stack, though it doesn't explain why it won't fail on the first try or with dev tools open. |
I'm going to mark this WONTFIX. I don't see a compelling reason to use nested VALUES in this way causing the deep recursion here. And unfortunately, even if there is a good reason to do this, the "obvious" ways that Emscripten provides to tune the stack size don't seem to have any effect. |
Hey! I found one weird bug, I have RangeErrors for some queries when I use asyncified version of wa-sqlite. SQLite just fails to prepare this query:
The interesting thing is that:
I tested it on m1 MacBook with Chrome
The query run ok with any wasm
standard
building under any condition.The text was updated successfully, but these errors were encountered: