Grimrock

I just installed the Steam version of Grimrock as part of the Humble Indie Bundle. I played for about 30 minutes, tried to save my game, and the game crashed to desktop with the error "not enough memory" (that's all it says in the error.log file).

I'm running MacOS 10.6.8 on a late 2010 Macbook Pro with 8GB memory and plenty of free disk space. No other open apps except Firefox, Steam, and Preview.app.

Played some more, I was able to save my game a number of times with no problem. After about 30-45 minutes I'd finished the first level, went downstairs and fought a couple of monsters. I went back upstairs to rest (and had a dream cutscene). I tried to save immediately afterwards, the save screen showed all the existing saves as "this save is corrupted" and when I tried to save to a new slot, it crashed to desktop with the same "not enough memory" message.

I ran the game again and my previous saves look okay. Maybe it's a memory leak that causes problems after some time?

...and trying to save after that first dream cutscene pretty much guarantees a crash

I'm out of the office but I'll try to reproduce the issue as the first thing when I come back. Does running with medium quality textures help? This should take much less memory.

I have sent an E-mail with console and error log earlier matching this bug. It happens far more frequently and quickly with the Steam version. The standalone version also has the same crash but would sometimes randomly crash with no error message mid action.

I have made it as far as the level with but the continued crashes have made further progress untenable.

I don't think it is a memory leak. It sounds more like an overflow with the game reading random memory chunks. There is no way for the game to "Run out of Memory" at approximately the same place. You have 8GB, I have 4GB with the crash happening at the same place. If it was a leak it would run on your machine for much longer and would slow down and make a mess of the swap file before crashing.

petri, thanks for the suggestion. With medium textures, I was able to play for about 45 minutes (saving frequently) with no problems. I'll keep an eye on it but that definitely seems to help.

Hope this turns out to be easily fixable, since the high quality textures look so darn pretty!

EDIT:
It seems that Steam just won't load games in general for me, and my issue is not Grimrock specific.

==========================================================
Original message:

I had the same problem, but now my game also refuses to start. I tried saving, the game crashed with that error message, but I am no longer able to run the game. Attempting to run it causes the icon to appear in the applications bar, it bounces a few times, then the program stops responding. It never opens a game window.

Using Steam Mac version. I tried deleting local content and re-downloading - didn't work.

MacBook Pro
OSX 10.6.8 Snow Leopard
4GB RAM

I've also been having this exact same issue with crashing on save with the out of memory error and I sent an email report on the 22nd.

I've also seen the corrupted save issue where all my saves are shown as corrupted, the first time I saw this I wiped my saves and started again (I was on level 1) but since then discovered that a restart makes all the saves show as ok and load again.

The crash on save issue has happened so frequently for me, 20+ times, I've had to save more frequently so I get more crashes but at least its less rage inducing than losing a massive chunk of time and progress. However I've actually given up playing the game, I love it but its too frustrating constantly crashing so I'm waiting for the issue to be fixed before continuing. I'm more than happy to help fix the issue If I can do anything.

I also found that the non steam version seemed a little more stable but still not enough for me to play.

I'm running:

3.4 GHz Intel Core i7 27" iMac
AMD Radeon HD 6970M 2048 MB
12 GB 1333 MHz DDR3
10.8.2 Mountain Lion

I've been running with everything on maximum, I've give the medium texture suggestion a try.