Random 'Caught Signal 11'/'Bad cgame trap' Crashes (Linux/Nvidia)

[aaron5367]

I'm running Arch Linux on my desktop. Ever since switching off of Windows I've had random 'caught bad cgame trap '<random series of numbers here>' . I've tried using the client from trem-servers, which just kicks me out of the server and gives me the cgame trap error. Using a custom compiled client the game crashes completely. The odd thing about this is that it only happens on kor-tremx (so far, I think). I'm the only one who gets this random error (and I'm far from the only player on there).

I've already tried erasing all of my tremx-kor files. I've also tried reinstalling a few times, to no avail. Here is a partial condump of it happening with the compiled client:

Code: [Select]

default^7 entered the game
^1I S^4ee ^1Y^4ou^7 was pulse rifled by ^2|^5oBsT^2|^1GER^7
^1S^3e^1x^3y ^6J^3o^6s^3h^7 was sawn by ^uVisser Three^7
default^7 joined the humans
[H] ^2{^7A^2}^7S^2nug^7g^2{^7ACR^2}^7: ^2omfg
^1S^3e^1x^3y ^6J^3o^6s^3h^7 was machinegunned by default^7
Received signal 11, exiting...
----- CL_Shutdown -----
Closing SDL audio device...
SDL audio device shut down.
RE_Shutdown( 1 )
-----------------------

Seemingly, I don't have to do anything to provoke this. Sometimes it happens when I'm on spectators, sometimes it happens when I'm following someone, and sometimes it happens ingame. I'm posting up a full condump of my loading output (as requested by Amanieu). This is with the Trem-servers.com executable.

http://pastebin.com/f22789f2b

and my autogen.cfg:

http://pastebin.com/f4bdeb1d0

[Bissig]

Bad RAM? Overheating GPU/CPU? So many things that could fail.

[Taiyo.uk]

Does this only happen in Tremulous?
Do other 3D games cause similar crashes?

Best rule out software issues before blaming the hardware.

[Zero]

If you switched off windows and you are having that type of problem, would it possibly be a corrupt file or a missing file, causing it to do that?

[benmachine]

Signal 11 is a segmentation fault, which usually means a bug in the program. There's a small chance it can be bad RAM but in the overwhelming majority of cases it's a code screwup. Are you x86_64 by any chance?
The bad cgame trap message is when your cgame makes a system call (i.e. asks something of the client) that doesn't exist. Either your client or your cgame is buggy, or they're just incompatible with each other. It might be helpful if you found what number it printed.
P.S. the cgame message is "Bad cgame system trap". It's easier to work out what causes your errors if you quote them exactly.

[aaron5367]

No, I'm x86... I'll run a ram test or two, but I don't think that's the problem either. Sorry abut the misquote, I'll start gathering some numbers starting now.

---

It's possible Zero, but I've removed my autogen.cfg and started with a clean one, as well as a new GUID.

---

Yes, I have no problems with this in Windows, or when I play games that are very graphically dependent.

---

I don't think it's any of those listed Bissig, I've never had issues like these before, and Tremulous isn't the only thing I do on my computer.

[Zero]

Store all your important files on a flash drive or CD, then re-install your linux software on top of your current one, unless its too painstaking and time wasting...

[aaron5367]

The weird part about this, that I don't believe I've mentioned, is that these crashes only happen on Tremx...

Edit: I've found the problem, I think. I'm going to bed tonight with 500,000 RAM errors (and counting still). I'm using memtest86. Thanks for the help!

[Zero]

The weird part about this, that I don't believe I've mentioned, is that these crashes only happen on Tremx...

Tremx is the beginning of all problems. (for me especially)