Skip to content
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

[wasm] Application exit (RangeError: Maximum call stack size exceeded) #542

Open
bsiegelwax opened this issue Jan 8, 2024 · 9 comments
Open
Labels

Comments

@bsiegelwax
Copy link

https://aqua.sfc.wide.ad.jp/quisp-online/0.2.1/ is displaying:

Application exit (RangeError: Maximum call stack size exceeded)
@zigen
Copy link
Contributor

zigen commented Jan 10, 2024

thanks for reporting it. the v0.2.1 is an old version. it might be fixed in the master branch
https://aqua.sfc.wide.ad.jp/quisp-online/master/ or https://aqua.sfc.wide.ad.jp/quisp-online/v0.3.0/
I'd be happy if you provide what you did in the simulator to reproduce this error.

note that inherently the WebAssembly version has several limitations for the execution like memory size and stack depth because it should run on a web page.

you can see other revisions in quisp wasm version here https://github.com/sfc-aqua/quisp-online .

@zigen zigen changed the title Application exit (RangeError: Maximum call stack size exceeded) [wasm] Application exit (RangeError: Maximum call stack size exceeded) Jan 10, 2024
@zigen zigen added the wasm label Jan 10, 2024
@bsiegelwax
Copy link
Author

I haven't done anything with the simulator. If I click on the 0.2.1, master, or v0.3.0 links, I see that error message before I can even see what the simulator looks like.

@zigen
Copy link
Contributor

zigen commented Jan 10, 2024

hmm, that sounds weird. could you tell me the full stack trace and your OS and browser version?

@bsiegelwax
Copy link
Author

Windows 11 Home Single Language 22H2
Microsoft Edge Version 120.0.2210.121 (Official build) (64-bit)
quisp

@zigen
Copy link
Contributor

zigen commented Jan 10, 2024

thanks! i haven't tried it on Edge. i'll try it tomorrow.

i confirmed it works on Google Chrome.

@zigen
Copy link
Contributor

zigen commented Jan 11, 2024

I tried it but it works.
Windows 10 Pro 22H2 19045.3930
Microsoft Edge 120.0.2210.121

@bsiegelwax
Copy link
Author

That's my screenshot. It starts off and stays just like that. Any other ideas?

@zigen
Copy link
Contributor

zigen commented Jan 15, 2024

could you show me the stacktrace in web console? I think there's more detailed log.

@bsiegelwax
Copy link
Author

All it shows is:

console.trace
(anonymous) @ VM95:1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants