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
Using Fibers causes epic crash #46
Comments
This is the bare minimum required to make fibers work within the go runtime.
This is the bare minimum required to make fibers work within the go runtime.
This is the bare minimum required to make fibers work within the go runtime.
@dunglas the following Docker file (props @cdaguerre in #374) appears to "fix" fibers. At least for this reproducer with manual testing. It needs more testing:
🥳 🤞 🤞 still testing... |
Great news! Don't hesitate to open a PR with this changes, so we can see if this fix the issue for all architectures. |
I'll do some proper testing by Monday (by updating the fiber branch), but I haven't seen a crash yet via manual testing. |
@withinboredom I had issues with fibers so I could also test this on my Cloud Run service but not really sure where can I get docker image to use with this fix. |
It doesn't fix it, per se, more-or-less just reduces the probability of a crash. Edit to add: the best way to prevent a crash is to just not output anything at all inside a fiber. |
Minimal code to reproduce:
With some slight modifications, it can also be reproduced in worker mode.
The text was updated successfully, but these errors were encountered: