Check for memory leaks #5280
Description
It seems like there's a weird, yet interesting behavior with the latest version, as I haven't noticed it with previous versions.
When I open multiple view tables, I have noticed a small delay loading the data, whereas in the past was rather instant more or less.
The interesting part is that when I close the view table window(s), the program does not reclaim the freed memory from closed windows; it only adds on the existing memory load it already had upon initial execution of the program.
In other words, let's say the program started with 120 MB of use and I open a rather mediocre view table; it will add on to the existing memory consumption the amount of data it had originally loaded; fair enough, you would say, it makes sense.
Alright...but why isn't releasing its memory when I close it? You could argue it's keeping it in cache.
Fine, this scenario makes sense.
But here's the issue: why does it consume memory anew to load the same data it hypothetically cached from previous loading?
If I repeat the process a couple of times, it jumps from, let's say 40% of my total memory consumption, to 50%-52% and grows exponentially.
A possible leak somewhere?