View Issue Details

IDProjectCategoryView StatusLast Update
0000674FSSCPgameplaypublic2006-11-01 04:50
Reporterngtm1r Assigned Totaylor  
PrioritynormalSeveritycrashReproducibilityrandom
Status resolvedResolutionfixed 
Summary0000674: The Cthon Crash Bug
DescriptionSince long before I joined the FS community, and since before the SCP, people have had problems with the mission "Memento Mori" from Derelict. Namely, the SD Cthon (Demon-class) jumps in, the game runs a few more seconds, and then it crashes to desktop. No one has yet been able to assign a specific set of circumstances to it. I ran the mission seven times, the first six it crashed, the last it did not, and there was no difference each time I could detect. Others have made similar complaints; some have never encountered the problem.

In short: Intermittent fault.

However, for some vague good news, at least up to 3.6.7 the bug is still present (when it decides to show up), so you're looking for some piece of code that hasn't been altered significantly from retail.
Additional InformationThis bug may or may not be related to a somewhat similar one in a mission I built once (attached), which also had a Demon jump in, and then a crash a few seconds later...but not always.

My best guess on the subject is there's a number or number range in there somewhere. Killing more of the enemy more quickly seems to help (and hence reducing the numbers of various things in the mission), but isn't always effective
TagsNo tags attached.

Activities

2006-01-02 10:55

 

C1M1.fs2 (51,504 bytes)

taylor

2006-01-02 20:52

administrator   ~0004104

I tried the attached mission without issue. Played it 4 times in a CVS build and 5 times in 3.6.7. Never crashed.

I'll try the Derelict mission when I get the time later this week.

thesource2

2006-01-13 12:41

reporter   ~0004226

Yes, looks like SD Demon arrival crashes fs2_open after 0000008:0000030 seconds. This happens almost always.
NOTE: there is no such problem in Goober's built, so possible solution is hidden there.

taylor

2006-01-13 14:00

administrator   ~0004228

I've played through the Derelict mission about 10 times now and it hasn't so much as slowed down on me. I'll try and do some more testing this weekend but this will likely get left to someone who can recreate the bug.

thesource2

2006-01-13 15:01

reporter   ~0004232

Taylor, if you have P4 class processor, try to test on P3. I have faced already many problems in some latest software connected with this.

taylor

2006-01-13 15:16

administrator   ~0004235

I run either an Athlon64 (Linux x86_64) or a G4 (OS X, Linux PPC), neither are Windows so I can't use the particular builds with the problem, only CVS builds I make myself.

phreak

2006-01-14 01:13

developer   ~0004257

Doesn't crash here.

Can you run a debug build and see what it says if it crashes once the cthon appears?

2006-01-14 08:42

 

fs.log (66,548 bytes)

thesource2

2006-01-14 08:43

reporter   ~0004268

Here's the log

2006-01-14 08:47

 

thesource2

2006-01-14 08:47

reporter   ~0004270

Also take this crash report.

phreak

2006-01-14 09:35

developer   ~0004273

Last edited: 2006-01-14 09:36

Can you do the same with this build: http://fs2source.warpcore.org/exes/phreak/fs2_open_d_cthon.zip

I have a map file for it, which means i can trace back the errors that occured from the RPT file you posted.

edited on: 01-14-06 04:36

thesource2

2006-01-14 10:15

reporter   ~0004276

Wheeeee! I fixed this. I just removed the bug in this mission: fire-beam function referred to non-beam turret (not on Cthon, but on criuser, still it solved the problem).
By the way I finished the Derelict campaign and during this fixed TONES of bugs there. Attaching fixed version of Derelict (only missions and campaign file, you still need tables from Derelict developer)

2006-01-14 10:18

 

Derelict_fixed.zip (559,558 bytes)

taylor

2006-01-14 11:45

administrator   ~0004278

Umm, the fire-beam is known, I had encountered it in the same mission. That was before the Cthon jumped in though so I assumed it was a different bug. And I should have put that fix in CVS too (checks... yet sexp code fix is in CVS). There actually should have been a comment here now that I think back, I found that particular bug a couple of days after my first bugnote. The fire-beam thing should be fixed in any build released after the 2nd.

But as I said I only got that bug several minutes *before* the Cthon arrived so I didn't associate it as the same problem. If that was the only issue then I suppose I fixed it without noticing. Please try a current CVS build, without the fixed mission, and make sure that it is actually fixed.

thesource2

2006-01-14 11:53

reporter   ~0004280

Current built (not debug) works fine with fire-beam - no error accures, just beam is not fired. Debug build gives warning window, but allows to continue without crash. Howewer, if fire-beam is executed in this mission with errors, game crashes
after Cthon arrives. I just replaced erronious turret to correct one, and no crash occured with Cthon. I suspect that error in execution of fire-beam causes minor errors in memory usage or allocation which are not fatal until something specific happens (like arrival of Cthon, check maybe crash accures when Cthon tries to fire one of it's beams, I don't know).

taylor

2006-01-14 12:19

administrator   ~0004282

The fire-beam bug was that it overwrote a variable that it used to determine what ship/turret was invalid. This allowed it to try and use a NULL string to tell you about such error, which would then crash.

I agree that the missions need to be fixed, but the code bug has been squashed so it shouldn't be a SCP issue now.

thesource2

2006-01-14 14:59

reporter   ~0004286

However the fact remains: if I fix fire-beam problem, crash disappears.
I don't know how they are connected (maybe there is something specific in this mission that makes first thing affect second one).

taylor

2006-01-14 15:28

administrator   ~0004287

But the crash only happens when not using a build with the code fix, correct?

thesource2

2006-01-14 15:42

reporter   ~0004288

I use 20060109 built and crash happens there. Isn't it the latest available built?
If not then you changed place where you hold your builds. If so give me the link please.

Goober5000

2006-01-28 20:41

administrator   ~0004534

Go to Hard Light Productions and look for the Source Code Project forum. Then look in the Recent Builds forum and find the stickied CVS Builds thread. It is regularly updated with the most recent CVS builds.

thesource2

2006-01-29 09:10

reporter   ~0004545

Oh, thank you very much for information. But it's a bit rusty already actually :)

Goober5000

2006-02-06 14:18

administrator   ~0004673

Can we close this?

thesource2

2006-02-06 14:47

reporter   ~0004674

It is for you to decide. As I said, I have removed the problem from mission by fixing fire-beam event. But by doing this I have only hide the problem, not resolve it. If incorrect turret is specified in fire-beam, it must not cause future crashes, so you are advised to look into this.

Goober5000

2006-02-06 15:49

administrator   ~0004675

You never answered taylor's question. Does the crash happen in the most recent CVS build?

ngtm1r

2006-02-11 02:03

reporter   ~0004713

I am pleased to confirm the apparent fixing of the bug; seven playthroughs and the mission does not crash.

Goober5000

2006-02-11 04:10

administrator   ~0004714

Great. Confirmation is what I was looking for. Thanks. :)

Issue History

Date Modified Username Field Change
2006-01-02 10:55 ngtm1r New Issue
2006-01-02 10:55 ngtm1r File Added: C1M1.fs2
2006-01-02 20:52 taylor Note Added: 0004104
2006-01-13 12:41 thesource2 Note Added: 0004226
2006-01-13 14:00 taylor Note Added: 0004228
2006-01-13 15:01 thesource2 Note Added: 0004232
2006-01-13 15:16 taylor Note Added: 0004235
2006-01-14 01:13 phreak Note Added: 0004257
2006-01-14 08:42 thesource2 File Added: fs.log
2006-01-14 08:43 thesource2 Note Added: 0004268
2006-01-14 08:47 thesource2 File Added: fs2_open_d-20060109.RPT
2006-01-14 08:47 thesource2 Note Added: 0004270
2006-01-14 09:35 phreak Note Added: 0004273
2006-01-14 09:36 phreak Note Edited: 0004273
2006-01-14 10:15 thesource2 Note Added: 0004276
2006-01-14 10:18 thesource2 File Added: Derelict_fixed.zip
2006-01-14 11:45 taylor Note Added: 0004278
2006-01-14 11:46 taylor Status new => assigned
2006-01-14 11:46 taylor Assigned To => taylor
2006-01-14 11:53 thesource2 Note Added: 0004280
2006-01-14 12:19 taylor Note Added: 0004282
2006-01-14 14:59 thesource2 Note Added: 0004286
2006-01-14 15:28 taylor Note Added: 0004287
2006-01-14 15:42 thesource2 Note Added: 0004288
2006-01-28 20:41 Goober5000 Note Added: 0004534
2006-01-29 09:10 thesource2 Note Added: 0004545
2006-02-06 14:18 Goober5000 Note Added: 0004673
2006-02-06 14:47 thesource2 Note Added: 0004674
2006-02-06 15:49 Goober5000 Note Added: 0004675
2006-02-11 02:03 ngtm1r Note Added: 0004713
2006-02-11 04:10 Goober5000 Note Added: 0004714
2006-02-11 04:10 Goober5000 Status assigned => resolved
2006-11-01 04:50 taylor Resolution open => fixed