-
Notifications
You must be signed in to change notification settings - Fork 46
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
Calling task is running, but scheduled to be resumed!? #58
Comments
Could it be that there was an earlier assertion error, or something silimar, such as a range error, happening before the mentioned error? That should have terminated the application immediately, unless Otherwise, do you see a chance for extracting a reproduction case from this? I could try to just fire worker tasks and create timers inside to see whether that is enough to trigger it, but otherwise it looks hard to diagnose, since this is very likely caused by something that has happened in a previous task that ran on the same fiber. |
Narrowed it down to a
|
Thanks a lot! I'll try to find some time to debug this next week. |
Previously the task was only removed if switchTo was called from another task. Now it also gets removed when switchTo (e.g. due to a runTask() call) gets called form outside of a task.
Previously the task was only removed if switchTo was called from another task. Now it also gets removed when switchTo (e.g. due to a runTask() call) gets called form outside of a task.
Previously the task was only removed if switchTo was called from another task. Now it also gets removed when switchTo (e.g. due to a runTask() call) gets called form outside of a task.
Previously the task was only removed if switchTo was called from another task. Now it also gets removed when switchTo (e.g. due to a runTask() call) gets called form outside of a task.
very nice |
I'm facing a problem while trying to create a new task inside a task (with
setTimer
insiderunWorkerTaskH
) , it throws an assert errorCalling task is running, but scheduled to be resumed!?
onAny idea what causes this? It happens randomly when creating a lot of worker tasks which call
setTimer
and when all worker tasks are queued, but always when they are running, at some point.
The text was updated successfully, but these errors were encountered: