[bfobar]

I Mantis reported this but I would like to post about it to maybe get some ideas on things to try to isolate the problem I'm having:

Situation: Crash to Desktop after warpout.

I was trying to play through the user made campaigns Deus Ex Machina, Aeos Affair, and Destiny of Peace, and I cannot get through the first missions of AA and DEM, or mission 2 or DoP because of frequent crashes to desktop. There's no error message besides a "FS2 encountered an error and needs to close." The crash seems to occur whenever I try to jump out at the end of the mission after completing all objectives, (at least in both AA and DoP that I've been playing around with) and occurs right before the game should be switching to the debriefing screen.

I'm running in openGL mode with the following command lines:
-----snip from the laucher.ini file-----
[launcher]
exe_filepath = C:\FreeSpace2\fs2_open_d-P420060202.exe;
game_flags = -ambient_factor 90 -spec -glow -jpgtga -nomotiondebris -2d_poof -missile_lighting -dualscanlines -targetinfo -orbradar -rearm_timer -nobeampierce -ship_choice_3d -3dwarp -warp_flash -snd_preload -env -alpha_env -fps ;
active_mod = DEM;
--------------- end snip --------

I tried:

1.) 02/02/06 and 01/31/06 CVS builds -- regular and debug.

2.) disabling all mediavps and command line flags in the launcher to run as close to a retail version of FSO as possible.

It still crashes every time and I need some ideas on what to look at next. Any input would be much appreciated.

[Wanderer]

If you have file named errorlog.txt in your freespace directory post the first few lines from the last error report on that txt file, beginning something like:

Code: [Select]

fs2_open_r-20060202 caused an Integer Divide by Zero in module atioglxx.dll at 001b:691cdfe6.
Exception handler called in Freespace 2 Main Thread.
Also create debug_filter.cfg (just create a new textfile and rename it to that) to your freespace directory. Then run the debug build to the 'crashs point'. Dont open the new file (fs.log) with notepad (use wordpad) and post the say last ten lines from that file.

[bfobar]

------------------------errorlog.txt-----------------------------------

fs2_open_d-P420060202 caused an Access Violation in module fs2_open_d-P420060202.exe at 001b:00b6d768.
Exception handler called in Freespace 2 Main Thread.

-----------------------------------------------------------------------

-----------------------fs.log------------------------------------------

Got event GS_EVENT_PLAYER_WARPOUT_DONE_STAGE1 (44) in state GS_STATE_GAME_PLAY (2)
Hit target speed.  Starting warp effect and moving to stage 2!
Got event GS_EVENT_PLAYER_WARPOUT_DONE_STAGE2 (45) in state GS_STATE_GAME_PLAY (2)
Hit warp effect.  Moving to stage 3!
Got event GS_EVENT_PLAYER_WARPOUT_DONE (46) in state GS_STATE_GAME_PLAY (2)
Player warped out.  Going to debriefing!
Got event GS_EVENT_DEBRIEF (33) in state GS_STATE_GAME_PLAY (2)
OpenAL ERROR: "Invalid Operation" in c:\fs2_open\code\sound\ds.cpp, line 3057
OpenAL ERROR: "Invalid Operation" in c:\fs2_open\code\sound\ds.cpp, line 2045
OpenAL ERROR: "Invalid Operation" in c:\fs2_open\code\sound\ds.cpp, line 2045
OpenAL ERROR: "Invalid Operation" in c:\fs2_open\code\sound\ds.cpp, line 2045
OpenAL ERROR: "Invalid Operation" in c:\fs2_open\code\sound\ds.cpp, line 2045
OpenAL ERROR: "Invalid Operation" in c:\fs2_open\code\sound\ds.cpp, line 2045
OpenAL ERROR: "Invalid Operation" in c:\fs2_open\code\sound\ds.cpp, line 2045
OpenAL ERROR: "Invalid Operation" in c:\fs2_open\code\sound\ds.cpp, line 2045
OpenAL ERROR: "Invalid Operation" in c:\fs2_open\code\sound\ds.cpp, line 2045
OpenAL ERROR: "Invalid Operation" in c:\fs2_open\code\sound\ds.cpp, line 2045
Unloading in mission messages

---------------------------------------------------------------------------------------




hmmmmmm.... looks like an OpenAL error. I re-installed the openAL by clicking the link in WMCoolman's stickied thread in this subforum, but that doesn't change anything-- problem still occurs.

[bfobar]

Taylor suggested that it may be like the talking head crash bug, so I turned those off (thanks for the ideas taylor, btw). The problem still occurs with no change in crash behavior yet. I'm logging all this in Mantis too so hopefully that helps.

[WMCoolmon]

Line 3057 is where the OpenAL code is stopping all channels; 2045 is where it's deleting sound buffers.

[taylor]

The OpenAL errors shouldn't be anything fatal.  Every OpenAL command is actually part of an error check and tends to spit out a lot of debug info that may not actually be needed/wanted, or even useful.  Newer code is still in the works which will be better suited to how OpenAL works rather than as something to opperate how DirectSound works.  Hopefully that will cut down on the OpenAL errors (fatal or not) which everyone is getting.

[bfobar]

Well whatever it is, it occurs on my 1/31/2006, 2/2/2006, and 2/12/2006 CVS versions, but not on my 1/25/06 or earlier.

[taylor]

Well whatever it is, it occurs on my 1/31/2006, 2/2/2006, and 2/12/2006 CVS versions, but not on my 1/25/06 or earlier.

Thanks for narrowing it down some.  I'll go through the various CVS commits and try to track the problem down tomorrow.  There were quite a few changes between those dates though so I don't know how long it will take to find the problem (couple minutes, couple hours or couple days).

[bfobar]

On further downloading of older CVS builds, it seems that the problem I'm having was introduced with the 1/26/06 cvs build. I also think that ShivanOps has the same bug with his description of the Jump-to-desktop problem.

[taylor]

Cutting down the date range that the bug was introduced does greatly speed up finding it.
Easily found the problem with a quick look at a diff and updated the bug report with the info.