Game Development Community

crashes a plenty in latest code

by Jim McLuckie · in Torque Game Engine · 01/08/2002 (10:21 pm) · 6 replies

I have the latest code updated from the CVS. when I compile it as debug, it runs just fine...no problems at all. When I compile it as release, I'm constantly getting "the memory could not be written" and "the memory could not be read" crashes. I'm using WinXP Pro. If you need more info, I could provide that.

#1
01/09/2002 (1:07 pm)
It could be that you have not enough memory on C.
I had the same problem.
#2
01/09/2002 (6:45 pm)
that's not it, because it's talking about the RAM...
#3
01/10/2002 (8:11 am)
Windows uses hard drive space for virtual memory. If you are low on space on your drive, you could get problems like that. It would seem like you would run into the same problems under debug mode though, so I don't know if that is really the problem.

Josh
#4
01/10/2002 (8:50 am)
I've just tested the release build and it is crashing on my machine, though my debug build does not. In my case it's crashing in the ATI driver. I'll trace through it today. Debugging the release builds is a pain in the butt :(

(ps. I'm using the latest head revision in CVS)
#5
01/10/2002 (10:42 am)
Turns out a fairly critical set of bug fixes to version 1.6 of the interior/itfdump.asm file had been un-rolled by accident in version 1.7. This will cause random crashes in the rendering code, usually in the OpenGL drivers themselves, and usually only in the release version of the build.

I've re-instated the fixes in version 1.8 (just checked it in). If you have version 1.7 of this file, I strongly recommend that you update.

(If your using Release 1.1.0, update to Dev_Stable. You can also just update the one file)
#6
01/10/2002 (10:59 am)
Tim, thanks a ton :) I'm loving the killer support behind this engine. Oh, and for the record, I have a Radeon as well. I'll test out the new version and let you know how it goes.