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.

Sign up for GitHub

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

Jump to bottom

Normal component calls can cause 'too long without yielding' error #30

Open
kcinnaJlol opened this issue Dec 3, 2021 · 1 comment
Open

Normal component calls can cause 'too long without yielding' error #30

kcinnaJlol opened this issue Dec 3, 2021 · 1 comment

Comments

@kcinnaJlol
Copy link

Calling a normal component function (see the docs under 'Direct Calls') should yield for a tick, yet they don't.
This means that when repeatedly calling a normal component function and not yielding via computer.pullsignal results in the program crashing with a too long without yielding error.
@kcinnaJlol
Copy link
Author

It appears that after some testing this issue only happens on 'fast' mode. (So in the config fast = true)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kcinnaJlol