Page 1 of 1

crash 1 over 2 times when i launch spring.exe

Posted: 27 Mar 2012, 01:32
by albator

Re: crash 1 over 2 times when i launch spring.exe

Posted: 27 Mar 2012, 01:41
by Beherith

Code: Select all

Error: :Unable to find detailed version in infolog

Maybe this stacktrace is from an self-compiled spring, or is the stack-trace to old?
This script only can handle >=0.82
Does stacktrace translator not worth with MT?

Re: crash 1 over 2 times when i launch spring.exe

Posted: 27 Mar 2012, 13:10
by abma
seems to be a bug in the translator script.

http://springrts.com/mantis/view.php?id=2754

Re: crash 1 over 2 times when i launch spring.exe

Posted: 27 Mar 2012, 13:17
by abma
work-arrounded by editing the file:

http://pastebin.com/FYWzey5M

try to disable bumpwater, that should fix the crash.

Re: crash 1 over 2 times when i launch spring.exe

Posted: 28 Mar 2012, 00:56
by albator
How so ? I use basic water.

Re: crash 1 over 2 times when i launch spring.exe

Posted: 28 Mar 2012, 01:02
by abma
meh, then the workaround didn't work, sorry.

does spring non mt, crash, too?

Re: crash 1 over 2 times when i launch spring.exe

Posted: 29 Mar 2012, 18:31
by albator
dunno, i did not bother testing it since that is either spring MT nor not spring

Re: crash 1 over 2 times when i launch spring.exe

Posted: 30 Mar 2012, 17:55
by zerver
Please use this one instead, and if still crash, infolog please.

http://springfiles.com/spring/game-inst ... executable

Re: crash 1 over 2 times when i launch spring.exe

Posted: 31 Mar 2012, 21:23
by albator
Tx zerver.

It crashed less, still it crashes when i exit the game on purpose.
ATI related.... but I use same config still years


http://pastebin.com/1MxBNWKW

Re: crash 1 over 2 times when i launch spring.exe

Posted: 01 Apr 2012, 13:49
by albator
A new error msg, just when the game starts, with new MT

http://pastebin.com/wg1BwDnh

Re: crash 1 over 2 times when i launch spring.exe

Posted: 07 Apr 2012, 03:27
by zerver
Yes, first one is ATI and the second one SIGABRT "abnormal termination" with incomplete stacktrace, so impossible to figure out the underlying cause.