-
Notifications
You must be signed in to change notification settings - Fork 5
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
Too many inner loops causes a crash #3
Comments
Hi, I can reproduce this problem. I'll take a look! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi there. Thank you for all of your efforts with
fiber_scheduler
and the thought and planning that you've put into positioning it as a great default. I'm getting up to speed with Ruby 3 non-blocking fibers and have benefitted from your related writing.I was playing around with using the
fiber_scheduler
gem and comparing it to other schedulers. I am using a non-block context (Fiber.set_scheduler
). In an effort to have some test code do something that would take a little longer to complete, I added a1_000.times
loop wrapper and found that doing so causes a crash.1_000.times
wrapper or lower the loop number to92
, the code works without crashing.fiber_scheduler
withasync
andFiberScheduler.new
withAsync::Scheduler.new
, the code works without crashing.#alive?
ends up getting called on the wrong object, causing the crash. The object that method gets called on can change between runs.Code to reproduce:
Error output:
The text was updated successfully, but these errors were encountered: