"Ampere K. Hardraade" writes: > Lately, my computer has been freezing on me unpredictably while I am using > FlightGear. (Note: I'm not saying FlightGear is to blame.) Normally, I just > cold boot the machine. Today however, after multiple freezes, I was too > angry to try again. I went away to do other things, and when I came back, > FlightGear seems to got killed by the kernel. When I relaunch FlightGear > later, I got a lot of this: > > Floating point interrupt (SIGFPE) > > Unfortunately, this was the only message I've got. > > I start FlightGear using the following command: > /usr/local/FlightGear/bin/fgfs > --fg-scenery=/usr/local/FlightGear/data/FlightGear/Scenery-0.9.8 > --aircraft=b1900d --airport=KSAC --bpp=24 --geometry=1280x600 --fov=69.9 > --multiplay=out,10,81.169.158.37,5002 --multiplay=in,10,192.168.0.194,5002 > --callsign=AMPERE --enable-real-weather-fetch --enable-clouds3d >
A real stab in the dark this, but I solved a lot of random freezes in opengl apps and internal compiler errors from gcc by clearing a layer of compacted dust from the cpu cooler (Athlon). Alternatively, does FG freeze when you start it without all the options above? Cheers - Dave _______________________________________________ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
