another silent crash

[Gwai]

I keep having silent crashes from TOME. In other words, I click to some other program and do work. Then, when I go back to TOME, it just closes. If it was previously saved, the save will still be there, but if it wasn't, the character is just gone. Never see anything much in the log. Here's the end of the log this time:


[LOG] Copperhead snake hits Alaeha for #aaaaaa#13.00 physical damage#LAST#.
201 frames in 10.027 seconds = 20.0459 FPS
223 frames in 10.045 seconds = 22.2001 FPS
226 frames in 10.046 seconds = 22.4965 FPS
191 frames in 10.025 seconds = 19.0524 FPS
193 frames in 10.101 seconds = 19.107 FPS
194 frames in 10.015 seconds = 19.3709 FPS
223 frames in 10.021 seconds = 22.2533 FPS
216 frames in 10.001 seconds = 21.5978 FPS
211 frames in 10.054 seconds = 20.9867 FPS
212 frames in 10.004 seconds = 21.1915 FPS
208 frames in 10.031 seconds = 20.7357 FPS
203 frames in 10.033 seconds = 20.2332 FPS
224 frames in 10.016 seconds = 22.3642 FPS
214 frames in 10.021 seconds = 21.3552 FPS
214 frames in 10.022 seconds = 21.353 FPS
218 frames in 10.021 seconds = 21.7543 FPS
214 frames in 10.017 seconds = 21.3637 FPS
211 frames in 10.058 seconds = 20.9783 FPS
220 frames in 10.011 seconds = 21.9758 FPS
213 frames in 10.024 seconds = 21.249 FPS
218 frames in 10.018 seconds = 21.7608 FPS
219 frames in 10.027 seconds = 21.841 FPS
211 frames in 10.029 seconds = 21.039 FPS
208 frames in 10.057 seconds = 20.6821 FPS
218 frames in 10.012 seconds = 21.7739 FPS
221 frames in 10.052 seconds = 21.9857 FPS
213 frames in 10.063 seconds = 21.1667 FPS
218 frames in 10.044 seconds = 21.7045 FPS
221 frames in 10.041 seconds = 22.0098 FPS
224 frames in 10.051 seconds = 22.2863 FPS
227 frames in 10.048 seconds = 22.5916 FPS
220 frames in 10.027 seconds = 21.9408 FPS
221 frames in 10.017 seconds = 22.0625 FPS
228 frames in 10.048 seconds = 22.6911 FPS
228 frames in 10.023 seconds = 22.7477 FPS
218 frames in 10.051 seconds = 21.6894 FPS
219 frames in 10.024 seconds = 21.8476 FPS
220 frames in 10.041 seconds = 21.9102 FPS
220 frames in 10.048 seconds = 21.8949 FPS
217 frames in 10.028 seconds = 21.6394 FPS
224 frames in 10.024 seconds = 22.3464 FPS
217 frames in 10.012 seconds = 21.674 FPS
217 frames in 10.017 seconds = 21.6632 FPS
224 frames in 10.024 seconds = 22.3464 FPS
220 frames in 10.019 seconds = 21.9583 FPS
215 frames in 10.046 seconds = 21.4016 FPS
219 frames in 10.023 seconds = 21.8497 FPS
220 frames in 10.028 seconds = 21.9386 FPS
220 frames in 10.012 seconds = 21.9736 FPS
224 frames in 10.052 seconds = 22.2841 FPS
227 frames in 10.024 seconds = 22.6457 FPS
217 frames in 10.023 seconds = 21.6502 FPS
223 frames in 10.02 seconds = 22.2555 FPS
222 frames in 10.042 seconds = 22.1072 FPS
219 frames in 10.058 seconds = 21.7737 FPS
226 frames in 10.012 seconds = 22.5729 FPS
225 frames in 10.018 seconds = 22.4596 FPS
222 frames in 10.026 seconds = 22.1424 FPS
211 frames in 10.05 seconds = 20.995 FPS
198 frames in 10.019 seconds = 19.7625 FPS
199 frames in 10.02 seconds = 19.8603 FPS
200 frames in 10.003 seconds = 19.994 FPS
209 frames in 10.017 seconds = 20.8645 FPS
212 frames in 10.048 seconds = 21.0987 FPS
216 frames in 10.049 seconds = 21.4947 FPS
215 frames in 10.053 seconds = 21.3867 FPS
214 frames in 10.056 seconds = 21.2808 FPS
216 frames in 10.042 seconds = 21.5097 FPS
214 frames in 10.025 seconds = 21.3466 FPS
217 frames in 10.049 seconds = 21.5942 FPS
214 frames in 10.014 seconds = 21.3701 FPS
219 frames in 10.025 seconds = 21.8454 FPS
219 frames in 10.047 seconds = 21.7976 FPS
224 frames in 10.017 seconds = 22.362 FPS
220 frames in 10.052 seconds = 21.8862 FPS
211 frames in 10.03 seconds = 21.0369 FPS
215 frames in 10.046 seconds = 21.4016 FPS
209 frames in 10.02 seconds = 20.8583 FPS
216 frames in 10.019 seconds = 21.559 FPS
209 frames in 10.023 seconds = 20.852 FPS
206 frames in 10.04 seconds = 20.5179 FPS
214 frames in 10.021 seconds = 21.3552 FPS
217 frames in 10.022 seconds = 21.6524 FPS
211 frames in 10.024 seconds = 21.0495 FPS
217 frames in 10.021 seconds = 21.6545 FPS
214 frames in 10.011 seconds = 21.3765 FPS
223 frames in 10.023 seconds = 22.2488 FPS
215 frames in 10.049 seconds = 21.3952 FPS
214 frames in 10.019 seconds = 21.3594 FPS
220 frames in 10.025 seconds = 21.9451 FPS
214 frames in 10.047 seconds = 21.2999 FPS
216 frames in 10.051 seconds = 21.4904 FPS
223 frames in 10.022 seconds = 22.251 FPS
216 frames in 10.019 seconds = 21.559 FPS
213 frames in 10.021 seconds = 21.2554 FPS
212 frames in 10.017 seconds = 21.164 FPS
205 frames in 10.024 seconds = 20.4509 FPS
27 ticks in 966.845 seconds = 0.0279259 TPS
220 frames in 10.016 seconds = 21.9649 FPS
202 frames in 10.017 seconds = 20.1657 FPS
196 frames in 10.016 seconds = 19.5687 FPS
28 frames in 15.237 seconds = 1.83763 FPS
2 frames in 10.916 seconds = 0.183217 FPS
2 frames in 10.727 seconds = 0.186445 FPS
2 frames in 10.797 seconds = 0.185237 FPS
2 frames in 11.484 seconds = 0.174155 FPS
2 frames in 10.949 seconds = 0.182665 FPS
2 frames in 11.304 seconds = 0.176929 FPS
4 frames in 14.624 seconds = 0.273523 FPS
2 frames in 12.006 seconds = 0.166583 FPS
2 frames in 10.816 seconds = 0.184911 FPS
207 frames in 10.021 seconds = 20.6566 FPS
222 frames in 10.044 seconds = 22.1027 FPS

[darkgod]

You'll have to run it in gdb and give me a stacktrace then

[Gwai]

Ha, got it to actually crash when I was actually running through gdb. Is this what you need?


Starting program: C:\Users\Rachel\Desktop\Tome4\Beta10/t-engine.exe
[New Thread 3256.0x5bc]
[New Thread 3256.0x1110]
[New Thread 3256.0x92c]
[New Thread 3256.0x588]
[New Thread 3256.0x360]
[New Thread 3256.0x12a4]
[New Thread 3256.0xa78]
[New Thread 3256.0x344]
[New Thread 3256.0x1388]
[New Thread 3256.0x114c]
[New Thread 3256.0x10d8]
[New Thread 3256.0x870]
[New Thread 3256.0xd44]

Program received signal SIGSEGV, Segmentation fault.
0x105618b8 in ig4icd32!DrvCreateLayerContext ()
from C:\Windows\SysWOW64\ig4icd32.dll

[darkgod]

When it crashes you need to type "bt" in the gdb command prompt, this will display the call stack, give it to me

[Gwai]

I don't think it did what you wanted it to, because this time when I managed to crash TOME, I crashed all of Windows, but just in case, pasted below. And the bit after #0 is what happened when I hit bt.

(You gotta be special to get two game-ending bugs in one game without cheating )

Starting program: C:\Users\Rachel\Desktop\Tome4\Beta10/t-engine.exe
[New Thread 4968.0x8e8]
[New Thread 4968.0xbfc]
[New Thread 4968.0xb84]
[New Thread 4968.0xa48]
[New Thread 4968.0x1040]
[New Thread 4968.0x1028]
[New Thread 4968.0x804]
[New Thread 4968.0x10dc]
[New Thread 4968.0x11b0]
[New Thread 4968.0x120c]
[New Thread 4968.0xff0]
[New Thread 4968.0x13b4]
[New Thread 4968.0x10c0]
[New Thread 4968.0x1384]

Program received signal SIGSEGV, Segmentation fault.
0x105618b8 in ig4icd32!DrvCreateLayerContext ()
from C:\Windows\SysWOW64\ig4icd32.dll
#0 0x105618b8 in ig4icd32!DrvCreateLayerContext ()
from C:\Windows\SysWOW64\ig4icd32.dll
#1 0x108faacc in ig4icd32!DrvCreateLayerContext ()
from C:\Windows\SysWOW64\ig4icd32.dll
#2 0x00847a70 in ?? ()
Cannot access memory at address 0x1212d004

[darkgod]

WOh .. hum .. woh :/

[Gwai]

When I crash a game I CRASH a game

[Gwai]

And I had it crash again while running from gdb. Same error exactly though this time Windows didn't itself crash. Not sure I can get a better stack trace on this, unfortunately.

[darkgod]

Weird .. can you try with the nojit exe I posted ? http://te4.org/dl/tmp/t-engine-beta10-noluajit.exe

[Gwai]

I think the error is the same:

Starting program: C:\Users\Rachel\Desktop\Tome4\Beta10/t-engine-beta10-noluajit.exe
[New Thread 3404.0x9d4]
[New Thread 3404.0x1368]
[New Thread 3404.0xe1c]
[New Thread 3404.0x7e0]
[New Thread 3404.0x12ac]
[New Thread 3404.0x12cc]
[New Thread 3404.0x910]
[New Thread 3404.0x7e4]
[New Thread 3404.0x1228]
[New Thread 3404.0x440]
[New Thread 3404.0xe0c]
[New Thread 3404.0xc84]
[New Thread 3404.0x480]
[New Thread 3404.0x1094]
[New Thread 3404.0x900]
[New Thread 3404.0x1384]
[New Thread 3404.0x42c]
[New Thread 3404.0xfe4]
[New Thread 3404.0xb48]
[New Thread 3404.0x12c4]
[New Thread 3404.0x50c]
[New Thread 3404.0x1178]
[New Thread 3404.0x80c]

Program received signal SIGSEGV, Segmentation fault.
0x105618b8 in ig4icd32!DrvCreateLayerContext ()
from C:\Windows\SysWOW64\ig4icd32.dll
#0 0x105618b8 in ig4icd32!DrvCreateLayerContext ()
from C:\Windows\SysWOW64\ig4icd32.dll
#1 0x108faacc in ig4icd32!DrvCreateLayerContext ()
from C:\Windows\SysWOW64\ig4icd32.dll
#2 0x00c37b48 in ?? ()
Cannot access memory at address 0x616cd004
A debugging session is active.

Inferior 1 [process 3404] will be killed.

Quit anyway? (y or n)

[darkgod]

And that did not happen in beta9 ??

[Gwai]

I thought I saw it once or twice, but never that I could be sure of (did I close TOME or did it just close itself?) I also just didn't play as much tome during the period of 9 because my life was crazier. Being laid off gives a gal more time