buffer overrun
Posted: Sun Aug 19, 2007 4:36 pm
Not sure whether this should be here on in technical support. Move as necessary.
I was given an old level to complete by another mapmaker in the community who has since disappeared. When this map loads ingame, I get the following message:
"a buffer overrun has been detected which has corrupted the program's internal state. The program cannot safely continue execution and must now be terminated."
Followed by a crash to the desktop, as you might expect.
I have no idea what this means. I've never seen anything like it before. Can anyone tell me what might be causing the issue?
One final note: when I got the level, it was crashing for a different reason (another hard crash to desktop). I looked through the map, and found some deleted monsters in TUNIs. Once those were fixed, The map almost loaded, but crashed back to the main menu. I determined this was the result of no map description string list being present, and fixed that. That's when the buffer overrun started. I assume that the issue was always there, and the other crash problems were keeping me from getting far enough for the buffer overrun to occur. But in case those fixes I made might be relevant, I'm letting them be known.
A-Red
I was given an old level to complete by another mapmaker in the community who has since disappeared. When this map loads ingame, I get the following message:
"a buffer overrun has been detected which has corrupted the program's internal state. The program cannot safely continue execution and must now be terminated."
Followed by a crash to the desktop, as you might expect.
I have no idea what this means. I've never seen anything like it before. Can anyone tell me what might be causing the issue?
One final note: when I got the level, it was crashing for a different reason (another hard crash to desktop). I looked through the map, and found some deleted monsters in TUNIs. Once those were fixed, The map almost loaded, but crashed back to the main menu. I determined this was the result of no map description string list being present, and fixed that. That's when the buffer overrun started. I assume that the issue was always there, and the other crash problems were keeping me from getting far enough for the buffer overrun to occur. But in case those fixes I made might be relevant, I'm letting them be known.
A-Red