tool · inferred from evidence
Docket
A broker component in Prefect associated with the in-memory messaging path.
- Prefect 3 server memory grows until OOM with default in-memory messaging
The Prefect 3 server leak came from the in-memory event messaging path used when no Redis is configured: unbounded internal queues plus a fakeredis Lua-runtime leak under the default `memory://` Docket broker. Fix: upgrade Prefect to 3.6.16