-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
./libev/ev.c:4043: ev_run: Assertion `("libev: ev_loop recursion during release detected", loop_done != EVBREAK_RECURSE' #2905
Comments
Do you have more output? Usually a stack dump would have more lines of output. |
Also I would recommend just not using fork worker mode if that fixes the issue for you. |
Is this coming from |
@bisrael do you have any more info about this issue? |
Searched for part of the error message here and found digital-fabric/polyphony#6 Is something similar happening in Puma when KILL are sent to workers? (when workers are culled or phased out) |
This failed CI run MRI: macos-13 2.7 logged Uploaded the logs from that run as they will eventually disappear: MRI macos-13 2.7.zip |
Describe the bug
puma: cluster worker 3: 19 [app]: ../libev/ev.c:4043: ev_run: Assertion
("libev: ev_loop recursion during release detected", loop_done != EVBREAK_RECURSE)' failed.`And then it seems possibly have broken the worker and after some time the Puma server stops accepting connections.
Puma config:
To Reproduce
This just starts to happen after some time of running the application server.
In the above config, it happens with:
PUMA_ENABLE_FORK_WORKER_MODE=1
PUMA_DISABLE_NAKAYOSHI_FORK=0
PUMA_MAX_WORKERS=22
PUMA_RESTART_WORKERS_AFTER_REQUESTS=300
PUMA_RESTART_WORKERS_AFTER_REQUESTS_JITTER=50
Specifically if you change PUMA_ENABLE_FORK_WORKER_MODE=0 the error ceases.
The worker count fits on a Private-L dyno for Heroku (14gb ram) for our somewhat bloated app.
Expected behavior
I expect this error to not be raised.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: