River’s received some recent fixes with the aim of stabilizing it for production readiness:

• Memory leak caused by allocating a new random source on every job execution.
• Memory leak caused by not always cancelling the context used to enable jobs to be cancelled remotely.
• Problem in riverpgxv5’s Listener where it wouldn’t unset an internal connection if Close returned an error, making the listener not reusable.

We’ve ran some open ended tests with continuous job insertion and work over long periods. Its memory use is stable, so we think those were the only leaks in there (at least for now).