High memory consumption of WebView on MacOS when there is many uncommitted files and leakiness

[Byron]

When there are a lot of uncommitted changes…

…and when scrolling through all of them, the memory consumption will rise constantly into multi-gigabyte territory.

A small project starts out like this:

Entering a project with ~6800 of changes brings it to 900MB: .

Scrolling through to the end of the files list brings it up to 2.25GB .

Switching back to a small project that has only 541 DOM nodes (as opposed to 131k for the previous state) does not release the memory (which is unexpected).

[Byron]

@estib-vega I think we have a problem with memory consumption in general. While writing this I switched back and forth between a large and a small project, and ended up at 8GB of real memory consumption within a couple of minutes.

The memory isn't released when switching to another project, even though I think that closing and reopening just the window would work as it would kill the process that holds the memory.

It could be that am mixing up Memory and Real Memory and that these 8GB are 'just' 2.7GB in the memory banks, but the issue remains: it uses too much and doesn't free it.

The backend has similar issues, interestingly, and is up to 923MB despite doing nothing and holding no cached information.

Should probably keep an eye out for that.

CC @krlvi