Skip to content

Uncaught RangeError: Maximum call stack size exceeded with custom Elements #8050

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

Closed
yannkost opened this issue Nov 23, 2022 · 3 comments
Closed

Comments

@yannkost
Copy link

Describe the bug

After upgrading from version 3.43.0 to the actual version 3.53.1 I had to revert back as my webcomponents (which can contain a lot of conditional rendering/lot's of HTML/combinations with other webcomponents) often can't render with following error:

image

I also saw that this error only occurs in Chrome and not in Firefox, so I'm at a loss here. I have seen some similar bugs in the issues, but I don't really know what the fix should be. I will try to make a reproduction but it won't be easy as my components rely on another project that is intern to our company and can't be published.

I think this is a issue with the 'inifinite loop of flush'?

Reproduction

Will try to create one

Logs

No response

System Info

Happends only in Chrome browsers

Severity

blocking an upgrade

@Prinzhorn
Copy link
Contributor

from version 3.43.0 to the actual version 3.53.1

Sounds like #7032 (https://github.com/sveltejs/svelte/search?q=Maximum+call+stack+size+exceeded&type=issues), which fits your version range. You can verify by checking that it breaks between 3.44.2 and 3.44.3. If it does, then it's probably a duplicate.

@yannkost
Copy link
Author

@Prinzhorn yeah I just tested it, indeed this breaks between 3.44.2 and 3.44.3, sadly a dealbreaker for me as I can't update svelte like this... (and not use the latest version of the vite-svelte plugin...) so #7032 is indeed the problem/solution, hope this get's fixed fast. The solution seems to be ready for over a year already?

@Conduitry
Copy link
Member

Closing as duplicate of #7032.

@Conduitry Conduitry closed this as not planned Won't fix, can't repro, duplicate, stale Nov 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants