Comment 31 for bug 796269

Me too I am a bit confused by the loads of memory used by widelands. I tried checking with valgrind where how much memory was used, but it runs too slow to give a good impression. I will try with google perf tools soon, maybe on the wihack.

This bug report is for the moment somewhere in between

* Fix committed (that's what I set it too, because it looks good) for the massive CPU reduction I introduced in the last few commits. They make a big difference with the playability of big maps and reduces the CPU usage to 10-30% on normal maps (4 players) on my computer
* Won't fix/Invalid: the crash with bad alloc likely occures due to constraints put up by Windows 32. This is not of big concern to me as it will fix itself over time (as 32 bit gets less common and more memory becomes mainstream). In ~2 years using 2 Gigs of RAM will not be an issue for a single program.
* Confirmed. Widelands memory consumption needs some followup investigation. See bug 885579.