ToME: the Tales of Maj'Eyal

A year and half ago I quit playing around RC4 and 1.0 because the game loading and performance became a frustrating torture on my antique computer. Still using the mostly the same, slightly upgraded machine, I came back to 1.1.5 with decent and acceptable performance.

Until the upgrade to 1.2.0 today...

ToME has nearly tripled the (already huge) amount of memory it hogs.
Even exiting to main map for the first time on a new character takes up 300 MB of RAM, two t1 zones and a town checked add up to 600. It took over couple hours and 10+ zones to hit that yesterday.

Loading times have also become at least twice worse - I was used to slow switching between zone and world map, but it now takes close to a full minute every single time.

What the hell happened? Is this just the new tree tiles or are there other things in the engine affecting it?

And is there any chance of getting it back the way it is in 1.1.5 or am I being chased away by a simple version update once again?

You can test if it's the tree's falut by playing in ascii mode; see if it makes a difference please

ASCII mode still takes a lot more than it does in 1.1.5.

Direct comparison between versions (create new character, start at Scinilatting Caves, exit straight to world map)

ASCII:
1.1.5 - 90 MB in the caves, 115 MB to world map
1.2.0 - 125 MB at start in the cave, 160 MB to world map

Modern:
1.1.5 - 95 MB caves, 135 MB world map
1.2.0 - 130 MB caves, 270 MB world map

This makes me think that whatever's going on happens mostly when the world map is loaded.

I seem to have hit a memory leak yesterday after clearing two t1 dungeons. Upon going to the third from the worldmap, the game hung up (fortunately it was after saving).

So it's either worldmap or saving that's leaking memory.

Agree with Zir that it's the worldmap or saving, can't tell which. Game crashed 2x the other day when trying to manually save though, and don't think one of them was on the worldmap. My Tome pre-1.2 ran at about 250 MB with the occasional spike, now it starts about there but gets up to like 600 after extended play.

If this hasn't been resolved yet, I'll try to get some more concrete data while I'm playing later today.

I'm on it I'm on it