It turns out that we are creating MerginProject objects way too much, and the cleanup of it may not be handled properly because of a cyclic reference between MerginProject and its internal GeoDiff context object.
It is going to be both safer and faster to create MerginProject for a particular working directory once and then keep it cached.
Fun fact: the leak is not showing up in "top" commend, only in docker's stats about memory...
Fixes #78
It turns out that we are creating MerginProject objects way too much, and the cleanup of it may not be handled properly because of a cyclic reference between MerginProject and its internal GeoDiff context object.
It is going to be both safer and faster to create MerginProject for a particular working directory once and then keep it cached.
Fun fact: the leak is not showing up in "top" commend, only in docker's stats about memory...