If the memory leak is in the kernel, the operating system itself will likely fail.
If the program does not deallocate an object, a memory leak occurs.
In most cases, the additional performance available from well written C is not worth the possibly of security bugs and memory leaks.
Otherwise, the Session can not be garbage collected, which is a memory leak.
As a result of this, the bad effects caused by the memory leak will be limited to that subset.
And I'm back to absolutely robust long-term operation with no memory leak.
A call to must be made for every call to to avoid a memory leak.
If this is not done, memory leaks or other unintended behavior may result.
It would sort of be like creating a memory leak.
My first guess would be an addon, those can easily have memory leaks.