Skip to content

runtime (js/wasm): avoid scheduler recursion #2178

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
wants to merge 1 commit into from

Conversation

niaow
Copy link
Member

@niaow niaow commented Oct 14, 2021

The wasm "log" test attaches a callback to a button and then triggers a click event.
The click event then calls back into the WASM module, spawning another copy of the scheduler loop.

This change detects this kind of nesting and will now spawn the event handler but not the scheduler.
A debug assertion has also been added to the scheduler to help track down similar issues in the future.

The wasm "log" test attaches a callback to a button and then triggers a click event.
The click event then calls back into the WASM module, spawning another copy of the scheduler loop.

This change detects this kind of nesting and will now spawn the event handler but not the scheduler.
A debug assertion has also been added to the scheduler to help track down similar issues in the future.
@niaow
Copy link
Member Author

niaow commented Oct 14, 2021

Nevermind, I seem to have messed up something between testing and committing. . .

@niaow niaow closed this Oct 14, 2021
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 this pull request may close these issues.

1 participant