You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently i've seen more and more applications abuse Mojo::IOLoop::one_tick to recurse back into the event loop and emulate blocking behaviour while waiting for events. This does of course not really work as soon as there is any real load on the server and will make applications crash in very unexpected ways.
Therefore i believe we should just not allow Mojo::Reactor::Poll::one_tick and Mojo::Reactor::EV::one_tick to recurse, and instead die right away if it is ever attempted.
The text was updated successfully, but these errors were encountered:
Recently i've seen more and more applications abuse
Mojo::IOLoop::one_tick
to recurse back into the event loop and emulate blocking behaviour while waiting for events. This does of course not really work as soon as there is any real load on the server and will make applications crash in very unexpected ways.Therefore i believe we should just not allow
Mojo::Reactor::Poll::one_tick
andMojo::Reactor::EV::one_tick
to recurse, and instead die right away if it is ever attempted.The text was updated successfully, but these errors were encountered: