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

Svelte 5: Spread Operator "Maximum call stack size exceeded" #11532

Closed
fznhq opened this issue May 10, 2024 · 3 comments · Fixed by #11560
Closed

Svelte 5: Spread Operator "Maximum call stack size exceeded" #11532

fznhq opened this issue May 10, 2024 · 3 comments · Fixed by #11560
Milestone

Comments

@fznhq
Copy link

fznhq commented May 10, 2024

Describe the bug

Happen at: svelte/src/internal/client/runtime.js

collected_effects.push(...effects);

Reproduction

Logs

No response

System Info

svelte@5.0.0-next.126

Severity

annoyance

@dummdidumm
Copy link
Member

Possibly the same reason as #4694 - but we can't tell if you don't provide any form of reproduction or more context. Please do that.

@dummdidumm dummdidumm added the awaiting submitter needs a reproduction, or clarification label May 10, 2024
@fznhq
Copy link
Author

fznhq commented May 10, 2024

Sorry for unclear issue, now I can recreate the problem, it happens in chrome (only test in firefox and chrome), I don't know the exact problem, but when using use: more than one too much, it will get the error

Reproduction

https://svelte-5-preview.vercel.app/#H4sIAAAAAAAACmWO0WrDMAxFf0VoLwmEpnvN0kC_Yx7D2Mpq5kjGdlKKyb8PZ5Q9TKCHq3sk3YKz85RweC_IeiEc8BoCdpgfoYq0kc-EHSZZo6mTMZnoQp4Uq-wpg9VZwwWY7nCNUT-a13Ot9q0CteeVTXbCwCKhYbHUQjnMXMVJ2HhnvuECT7JpoYARTuLp5OWrUXggClvY6-aueOz_cnB5IW1uv1F0gs8DGq3bYE001L-TuUVZaOyt26b_LsUo8WmWvl7bscNFrJsdWRxyXGn_2H8AzitBzC8BAAA=

@dummdidumm dummdidumm removed the awaiting submitter needs a reproduction, or clarification label May 10, 2024
@dummdidumm dummdidumm added this to the 5.0 milestone May 10, 2024
@fznhq
Copy link
Author

fznhq commented May 10, 2024

The more I look, it's not about using multiple use:, it's about using too many use:, when I log the effects it registers how many use: being used, in this case, 2 use: times 100k elements, so the effects has a total 200k array, so it will spread 200k array into collected_effects

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

Successfully merging a pull request may close this issue.

2 participants