Memory Leaks with Ninject and Rebus

[colin-higgins]

Rebus is async (task) based.
Relying on threads in task based code is bad, very bad.
Any task continuation can continue on a new thread. This can lead to nasty crazy side effects.
You can configure Ninject to manage your dependencies on a per thread basis. That means instance per thread.
If a thread is never let go in the expected sense, those dependencies might stick around.

Relevant links:
https://blogs.msdn.microsoft.com/davidklinems/2005/11/16/three-common-causes-of-memory-leaks-in-managed-applications/