Widelands uses loads of RAM

[SirVer]

This is a followup to bug 796269.

Widelands uses a lot of RAM on big Maps. Some of this is understandable -> Many fields == many objects == lotsa RAM. Still, > 1.6 gigs seems like a lot. This is a reminder bug report to at least look at a memory profile in more detail and maybe do something about the situation.

Valgrind is too slow to be used with widelands really, I will try with google's gperf soonish.

[SirVer (sirver)]

Yep, never happened. At this point in time I do not care that much and untarged and unassign. Perhaps one day...

[Martin Quinson (mquinson)]

I just ran about 5 game-hours of replay on a 512x512 map within the massif heap profiler (it's one of the valgrind tools, actually).

This trace can be visualized with http://packages.ubuntu.com/fr/precise/massif-visualizer

The widelands version used: bzr6874.

[SirVer (sirver)]

Setting to incomplete for bug sweeping.

[Launchpad Janitor (janitor)]

[Expired for widelands because there has been no activity for 60 days.]

[SirVer (sirver)]

This is not a priority right now and I believe the problem to be either solved or solve itself through the increase of RAM in machines, setting to invalid.