Unknown memory leak

[deliciouslytyped]

Throwback to #139, I'm on 0.20.0 and there is some sort of memory leak. Three lazydocker processes each ended up using 30% of RAM. I don't now if it has to do with it, but I left the terminals in the "Press enter to return to lazydocker" screen after exiting shells.

[DovieW]

I'm noticing this as well on version 0.23.3

I'm still diagnosing the issue, but my developers are often having their dev machines crashing and I think it's because they are leaving lazydocker running for long stretches.

I can see now one instance of lazydocker is using 1GB of memory

[MikaelElkiaer]

Also experiencing this - killing my 32G RAM machine simply by running overnight. It's a big stack with lots of log output - which is why I suspect that log output is the reason for the high RAM usage.

[DovieW]

That makes sense, if lazydocker is keeping everything in memory. I have a container that has runaway logs sometimes accumlating multiple GBs. Maybe lazydocker can implement some kind of caching thing or something. Or just drop logs that go back a configurable number of lines maybe