Crashes upon entering specifically the Archives

**superluser** · 09-09-2010, 02:36 PM

(09-09-2010, 06:21 AM)valczir Wrote: Had the same issue here and changing the file ownership worked fine. The installer really should be modified to create the game directory with ownership root:games. Apparently, write access is granted to group but not all, so setting the group to something that the gaming users are part of (in most cases, games) seems to solve it readily enough.

Had the same issue.

Fixed the same way (on Gentoo).

**Urkle** · 09-09-2010, 03:51 PM

are you getting the same error on the console?

Do you mind enabling core dumping and getting a stack trace?

Code: (Select All)

ulimit -c unlimited

./Amnesia.bin64

ls core.*

gdb ./Amnesia.bin64 core.####

Then once in GDB run this
thread apply all bt

and paste the contents here.

**zak** · 09-09-2010, 07:33 PM

Hi Urkle,
I tried this, installed gdb, set 'ulimit -c unlimited', ran Amnesia.bin64 and reproduced the error. Unfortunately no coredump was written. (Looked in homedir, .frictionalgames-dir and Amnesia-dir).
Setting write permissions just to /opt/Amnesia wasn't enough. (The coredump was not written there then, too.) I had to 'chmod a+rw -R' the whole directory tree. Then I could enter the Archives.

Now - after removing write permissions again - I cannot even reproduce the error (at least at the Archives-door). I saved again in the Entrance Hall, restarted and entered without any problems. Maybe this gives a clue?

If there's anything I can try, just tell me.

**Andre** · 09-11-2010, 06:07 PM

just had same problem - hope it will be fixed by a patch..

**Urkle** · 09-11-2010, 07:09 PM

I believe I have narrowed down what is causing the crash and made several fixes that will appear in a patch.

**Oblidor** · 09-13-2010, 09:22 AM

(09-11-2010, 07:09 PM)Urkle Wrote: I believe I have narrowed down what is causing the crash and made several fixes that will appear in a patch.

Good. I also have crash problems. The strange thing is that Amnesia seems to change the write permissions. I had installed it in a directory that I have all rights too. I set all files writeable and I ran the game as myself. After it started I saved and exited. Later when I wanted to play it again I only got crashes. Then I ran it with sudo and it worked. After exiting again it was crashing when I ran it as sudo or user. I then made all files writeable again and it worked. Then I came to the Archive and now it crashes whatever I do.

I'll wait for the patch Smile

I have the three other Penumbra games to play also, so I'll try out overture now Smile

Keep up the excellent work.

System: ubuntu 10.04, 64-bit, ATI Radeon 4870

**Urkle** · 09-13-2010, 02:46 PM

Really... strange.. I'll check how the cache files are being generated as I believe that is the cause of this mess.

**ladoga** · 09-13-2010, 04:10 PM

same problem here

Code: (Select All)

Amnesia.bin: /builddir/core2/sources/impl/tinyXml/tinyxml.cpp:1102: virtual void TiXmlDocument::Print(FILE*, int) const: Assertion `cfile' failed.

If I understood right, maybe cache files could be just generated in ~/.frictionalgames/Amnesia ?

I'll use permissions change to user as workaround for now.

**Oblidor** · 09-14-2010, 11:05 AM

(09-13-2010, 02:46 PM)Urkle Wrote: Really... strange.. I'll check how the cache files are being generated as I believe that is the cause of this mess.

After some more testing yesterday I'm not sure that Amnesia changes the permissions, but perhaps it does on cache files?

I have the problem that I cannot start the game two times in a row as a user. I have to switch back and forth between user and root.

Also I experienced that the game crashed as it was starting up (before profile selection) and when I started it again (right away without doing anything else) it worked fine. I find that strange.

About generating core files. Isn't it a problem that there is a directory called core? I don't get any core files after doing ulimit -c unlimited ...

**Urkle** · 09-14-2010, 01:03 PM

You'd need to do a chmod 777 Amnesia and then run the game.. it'll generate a core file.. It's been a LONG time since a core file was generated as "core" they are now generated as "core.####" where the # is the process ID.

There seems to be some oddities going on as the cache files are not supposed to be regenerated.