Note that virtual size usually means quite little. It's just reserved address space that may or may not be actually used. Physical memory is typically what is actually used (and it gets more complicated since processes share memory etc). On MacOS for me wesnoth uses virtual memory of ~390GB right after start for example.Before I try to narrow this down any further: has anyone noticed version 1.18.2 leaking (a lot of) memory?
Today I noticed it was using over 14 gigabytes (and still growing):
That is not to say that there are no memory leaks of course. Ravana mentioned one issue and there are likely more. When keeping wesnoth running for a while (maybe in the lobby? been a while since I tried to figure it out) on MacOS at least physical memory use does rise more and more. Unfortunately it's not so easy to find out what the cause is...
Statistics: Posted by Soliton — Yesterday, 10:19 pm