> It seems to be difficult to generalize about these things. Someone will say that a particular version of a browser leaks memory, or pegs the CPU, and someone else will say that the same version has no problems.
FWIW that's indeed my experience with qutebrowser as well. Everyone seems to have rather different experiences (or expectations?) when it comes to performance and RAM usage. Doesn't exactly make it easier to track issues down, unfortunately.
Yeah, I realize just saying “it leaks memory” is useless to you in tracking down why. It could be due to any of a dozen different things that QB interacts with. And the next level of investigation is something that I don’t really have the skills, nor, probably, the time, to undertake.
I'm not blaming you for that - those things are insanely hard to track down in a complex application spanning multiple programming languages and approaches to memory management... Unfortunately I have no idea where to start either :-/
FWIW that's indeed my experience with qutebrowser as well. Everyone seems to have rather different experiences (or expectations?) when it comes to performance and RAM usage. Doesn't exactly make it easier to track issues down, unfortunately.