Skip to content

[fix] Max call stack exceeded when large number of components are flushed #7397

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
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions src/runtime/internal/scheduler.ts
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,9 @@ export function add_flush_callback(fn) {
// function, guarantees this behavior.
const seen_callbacks = new Set();
let flushidx = 0; // Do *not* move this inside the flush() function
let flushing = false;
export function flush() {
if (flushing) return;
const saved_component = current_component;

do {
Expand Down Expand Up @@ -91,6 +93,7 @@ export function flush() {
flush_callbacks.pop()();
}

flushing = false;
update_scheduled = false;
seen_callbacks.clear();
set_current_component(saved_component);
Expand Down