constant crashing (Of program)

[Clive2670]

Flightgear 2017.2.1 constantly crashes about 15 minutes in. I have tried the usual %appdata% delete navdata file but this didn't work. Anyone help please? Could it be that I've "compressed" my drive thus the program has been compressed?

[Thorsten]

Memory usage?

[Clive2670]

Memory usage?

Hi Thorsten, Nothing out of the ordinary, I have 6Gb RAM and the program is consuming around 1.5 to 2.5 Gb depending on if I'm in the sky and very little rendering is required or on the ground where quite a bit is needed.

[Thorsten]

Strange... anything special you're doing at that time?

Any change of getting a backtrace? Anything interesting in the log file? For any aircraft or just a particular one?

[Johan G]

I just fly the 777 variant mainly the LR. Not sure how much of log file you want to see, It is thousands of lines long! here is the sample of the the program start:

Code: Select all

ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "C:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/B"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "C:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/C"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "C:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/D"
nasal:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalModelData.cxx:93:New model with attached script(s) (branch = 000001E457EB5F90, path = /'range animation node')
nasal:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalModelData.cxx:93:New model with attached script(s) (branch = 000001E4802195F0, path = /'range animation node')
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "C:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/E"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "C:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/F"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "C:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/G"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "C:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/H"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "C:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/I"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "C:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/J"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "C:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/K"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "C:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/KEQA"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "C:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/L"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "C:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/M"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "C:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/N"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "C:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/O"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "C:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/P"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "C:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/Q"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "C:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/R"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "C:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/S"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "C:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/T"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "C:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/U"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "C:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/V"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "C:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/W"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "C:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/misc"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:393:parsing traffic schedules took:7353msec
nasal:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalModelData.cxx:93:New model with attached script(s) (branch = 000001E482F29780, path = /'')
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\apt_signs.cxx:439:OBJECT_SIGN: unsupported glyph 'x'
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\apt_signs.cxx:439:OBJECT_SIGN: unsupported glyph 'x'
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\apt_signs.cxx:427:OBJECT_SIGN: ignoring unknown command `@ur'
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\apt_signs.cxx:427:OBJECT_SIGN: ignoring unknown command `@dr'
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\apt_signs.cxx:427:OBJECT_SIGN: ignoring unknown command `@ur'
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\apt_signs.cxx:427:OBJECT_SIGN: ignoring unknown command `@ur'
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\apt_signs.cxx:427:OBJECT_SIGN: ignoring unknown command `@ur'
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\apt_signs.cxx:427:OBJECT_SIGN: ignoring unknown command `@ur'
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2941779.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "C:/Program Files/FlightGear 2017.1.3/data/Scenery/New TerraMaster Scenery 1/Objects/w010n50/w001n51/2941779.stg"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "C:/Program Files/FlightGear 2017.1.3/data/Scenery/New TerraMaster Scenery 1/Terrain/w010n50/w001n51/2941779.stg"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2958152.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "C:/Program Files/FlightGear 2017.1.3/data/Scenery/New TerraMaster Scenery 1/Objects/e000n50/e000n51/2958152.stg"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "C:/Program Files/FlightGear 2017.1.3/data/Scenery/New TerraMaster Scenery 1/Terrain/e000n50/e000n51/2958152.stg"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2941762.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "C:/Program Files/FlightGear 2017.1.3/data/Scenery/New TerraMaster Scenery 1/Objects/w010n50/w001n51/2941762.stg"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "C:/Program Files/FlightGear 2017.1.3/data/Scenery/New TerraMaster Scenery 1/Terrain/w010n50/w001n51/2941762.stg"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2941778.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "C:/Program Files/FlightGear 2017.1.3/data/Scenery/New TerraMaster Scenery 1/Objects/w010n50/w001n51/2941778.stg"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "C:/Program Files/FlightGear 2017.1.3/data/Scenery/New TerraMaster Scenery 1/Terrain/w010n50/w001n51/2941778.stg"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2958144.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "C:/Program Files/FlightGear 2017.1.3/data/Scenery/New TerraMaster Scenery 1/Objects/e000n50/e000n51/2958144.stg"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "C:/Program Files/FlightGear 2017.1.3/data/Scenery/New TerraMaster Scenery 1/Terrain/e000n50/e000n51
/2958144.stg"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:585:finishing AI-Traffic init
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:504:FGTileMgr: at lon = -0.213267deg, lat = 51.146deg, elev = 66.3378m, scheduling needed for:-1:3, 51:1, visibility=100000
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:293:scheduling needed tiles for -1:3, 51:1, tile-width-m:17419.4, tile-height-m:13914.9

This line reoccurs hundreds of times as well:

Code: Select all

aircraft:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Model\modelmgr.cxx:74:Adding model [unnamed]


These lines is the most prolific lines in the log:

Code: Select all

nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:storms update requested! (timer issue when closing the dialog?)
flight:4:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\groundcache.cxx:394:prepare_ground_cache(): trying to build cache without any scenery below the aircraft


This line is the last entry in the log:

Code: Select all

nasal:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalModelData.cxx:93:New model with attached script(s) (branch = 000001E4942937C0, path = /'')


Hope this might help?

[Clive2670]

Thorsten, FYI, I have reverted back to 2017.1.3 just for now, to test if the same problem crops up on that version and will report back if that runs ok

[wkitty42]

@Clive2670: so you're flying the 777-200LR when this happens? is it always from the same airport to the same destination using the same flightplan? it could be that you have a bad or corrupted stg file in your scenery... if you can give details or even try the flight in 2017.2.1 with the UFO and see if it still crashes the program...

[Clive2670]

Hi wkitty42: sadly no I'm not using a flightplan, it will happen when I just "fly", I always tend to start from EGKK, But this problem always presents it's self during a flight at any point 15 minutes in upto hours in, just looking at my log above could it be the following line that is pointing to an issue? "flight:4:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\groundcache.cxx:394:prepare_ground_cache(): trying to build cache without any scenery below the aircraft" Would it be worth deleting all scenery from my terramaster scenery file and re-downloading it, if you think there is maybe an issue with a corrupt .stg file in the scenery file? Look forward to your idea's

[wkitty42]

Hi wkitty42: sadly no I'm not using a flightplan, it will happen when I just "fly", I always tend to start from EGKK, But this problem always presents it's self during a flight at any point 15 minutes in upto hours in,

ugh... that's gonna make it hard to reproduce do you still get the same problem with the UFO?? are you in any particular area each time it happens? lat x long x heading when it happens would help in tracking this down... you are using the latest release of FGFS?

[edit] i forgot to ask, multiplayer or solo? [/edit]

just looking at my log above could it be the following line that is pointing to an issue? "flight:4:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\groundcache.cxx:394:prepare_ground_cache(): trying to build cache without any scenery below the aircraft"

that gives a hint, though... either you are flying faster than the scenery can be loaded or there's something else going on... i remember something in the dev list about some problem with no scenery under the craft... supposedly, as has been done in the past, the sim may log a complaint but it should not be a showstopper and cause a crash...

Would it be worth deleting all scenery from my terramaster scenery file and re-downloading it, if you think there is maybe an issue with a corrupt .stg file in the scenery file? Look forward to your idea's

nononononono... don't delete your scenery... if there's a problem in a stg, we need to find out which stg and get it fixed on the server...

[Clive2670]

wkitty42, I'll leave scenery intact!!!! But if I'm flying "randomly" not to anywhere specific, it prove a issue finding the culprit when it comes to the rogue .stg file(s) causing the problem wouldn't it? What I'll do is copy the current log to the clipboard on my PC delete it from the flightgear file on the %appdata% re-launch a flight and if it crashes again I will compare the new log file with the one on the clipboard and see if I can "spot the difference" and post my findings here, this won't be until tomorrow though. Thanks for your help!

[wkitty42]

not a problem... i was just flying all around over there... took off from EGKK and made a square flight over to portsmouth and then north over EGLL and out over the eye of london... just messing around... flew at altitudes from 2000 to 5000 feet... even took a quick buzz all the way over to LFPO and back... landed at EGKK and set a flight plan to KATL which is in progress now... i can't say that i've had any problems other than very low frame rates in some areas which i attribute to the new scenery capabilities... i even made an effort to outfly the scenery loading... in the UFO @ 3500kts, it is fairly easy for the most part... no problems so far... am approaching derby on my flight...

[Clive2670]

wkitty42: Update, I am now using razorcortex https://www.razerzone.com/gb-en/cortex to shut down any system "stuff" that isn't required when I'm on flightgear, this frees up a minimum of 850Mb of RAM, I also shut down Windows defender which I've found has a tendancy to keep my hard disk running between 95 and 99% all the time, when turned off the disk usage drops to 0 to 2% when idle and increases to a mear 12% when running flightgear and it seems like flightgear is now happy again. I will say that I am thinking about returning to my PCs default O/S Windows 8.1 from Windows 10 as the above issues have been highlighted as problems on the Windows forums.