#258 FlightGear GIT crash to desktop at certain locations

[Anonymous]

Originally created by: gijsrooy

From forumite Upkeep:

*What steps will reproduce the problem?*
1. Using any aircraft ( tried several but mainly Seneca II), I load up the FlightGear Wizard to start from CYIK and CYLT and just before the loading is complete the program crashes to desktop
2. Flying towards BIRK or BIKF from Greenland or the UK approx 10 miles from these airports, the program freezes for a moment and there is a crash to desktop. The same happened when approaching CYFB and BGKK from the south

*What is the expected output?
1. I expect the FG Wizard to load normally and the cockpit view at the correct airport to load up as normal.
2. When the program crashes before BIRK etc, it has run normally for around 2 or 3 hours or so.

*What do you see instead?*
1. Crash to desktop just before it loads up
2. Sudden crash to desktop just before I reach destination airport

*Any output in the console (black window)?*
1. I cannot identify anything different in the console when compared with loading up another airport with the same aircraft, ie no additional comments
2. There is nothing additional in the console when the program crashes just before reaching the destination airport.

*What version of the product are you using (when using GIT version, please
mention date or Hudson build number)?*
The problems mentioned above occur when I use the GIT version Build 162. With 2.0.0 release version the above problems do not happen

*What operating system and graphics card?*
Windows 7 Home.
Graphics Chipset
Adapter Type ATI display adapter (0x9616), ATI Technologies Inc. compatible
Adapter Description ATI Radeon 3000 Graphics
Adapter RAM 1.00 GB

*Please provide any additional information below or as attachment (Avoid
expiring external links, such as to imageshack/pastebin/...).*
Problem 1: CYIK etc. When I first encountered this problem I was able to actually get CYIK loaded with cockpit view but as soon as I pressed ‘H’ to get HUD, there was a crash to desktop. If I avoided loading the HUD, and merely pressed ‘V’ to get a different view, there was a crash to desktop.
Then when I repeated this later, I noticed that just before the airport loaded the HUD was loading anyway (ie, as part of the main loading process and not following the typing of ‘H’). I do not know why this was different, ie why the HUD was appearing as part of the loading up process. The HUD began to appear indicating that FG was just about to finish loading, then there was a crash to desktop.
I have downloaded the relevant scenery again and re-installed. No difference. Atlas is working normally.

Problem 2 (BIRK etc): I can’t add much more to this except that it appears to happen roughly the same distance from the airport, ie around 10 miles. Again, there is nothing in the console.

[Anonymous]

Originally posted by: bre... (code.google.com)@gmail.com

Trying to reproduce the problem I noticed a GPS issue (on shutdown) which seemed unrelated at firt. I now see this actually was problem #1. Caused by a missing waypoint issue which crashed the sim as soon as waypoints are accessed (e.g. when activating the HUD display).
Fixed by:
http://www.gitorious.org/fg/flightgear/commit/f32656b2a5b567a0725e5ef2e2c254bd4f090185

Try the latest fgfs, i.e. Hudson #183 (or newer) for Win7:
http://flightgear.simpits.org:8080/job/FlightGear-next-Win64/183/

Possibly also fixes #2 - but I was unable to reproduce this so far.

Labels: -Scenery -SimGear Sim GPS
Status: Testing

[Anonymous]

Originally posted by: gijsrooy

Upkeep: "I have quickly tried problem 1 (crash when opening CYIK) and I can confirm that the problem has been fixed. I also completed an UK to BIRK flight with no problems at all, so I can confirm problem 2 is solved as well. Thanks to Torsten!"

Status: Fixed

[Anonymous]

Originally posted by: bre... (code.google.com)@gmail.com

(No comment was entered for this change.)

Status: Temp

[Anonymous]

Originally posted by: bre... (code.google.com)@gmail.com

(No comment was entered for this change.)

Status: Fixed