Thank you, Harald for your quick reply ...
1. Easy fix - line endings
Glad you could confirm my CVS check out ... but the
suggested code fix takes care of it, which ever line
endings there are in zone.tab ;=))
2. Hard find - ABORT
Thank you for the Debug menu pointer ... I had not found
MSVC very good with exceptions, in the distant past,
but it has really improved ...
Trapping the exception, and returning to the debugger, the
Call Stack showed, in part, the simple answer ...
FlightGear.exe!_nh_malloc_dbg(unsigned int nSize=1, int nhFlag=3, int
nBlockUse=1235168, const char * szFileName=0x0012d9ec, int nLine=1242460)
Line 267 + 0x7
FlightGear.exe!_CxxThrowException(void * pExceptionObject=0x0012d8fc, const
_s__ThrowInfo * pThrowInfo=0x00e95db0) + 0x39
FlightGear.exe!std::_Nomemory() Line 10
FlightGear.exe!operator new(unsigned int size=73056) Line 15
...
FlightGear.exe!FGTileMgr::update(SGLocation * location=0x201ac898, double
visibility_meters=200000.00000000000) Line 437
And of course, passing the exception back to FG, I end up
at the lines in bootstrap.cxx -
} catch (...) {
cerr << "Unknown exception in the main loop. Aborting..." << endl;
perror("Possible cause");
}
The console last few lines showed, confirming the call stack -
FGTileMgr::update()
State == Running
Loading tile
C:/FG0981/FlightGear/data/Scenery/Terrain/e000n40/e001n47/2974291
token = OBJECT_BASE name = 2974291.btg
So these ABORTS were a SIMPLE case of OUT-OF-MEMORY, of a
certain type ... This is the very first time I have found
Windows wanting in the memory allocation area ... I
thought the virtual memory was virtually unlimited ;=))
well, depending only on settings, and HDD size ...
So, maybe I can increase the swap file size, and
certainly REDUCE my very unreasonable visibility,
200000 meters, or BOTH ...
Note, Windows is not completely out of memory,
since I was able to open Word, and commence writing
this, while still in the debugger ... with several
other windows open ... ???
Removing my unrealistic 200000 from my system.fgfsrc
file, thus allowing the default visibility, and I could
fly around, with fog, and sky-blend, all day ;=))
I took off from Orly, flew generally NNW, and ended up
at Lands End, with some help from Google Earth ...
followed the southern coast around to Manston,
then left into Heathrow, over London, then
took about a 160 track, hit the French coast at 49 48'N,
0 30'E, adjusted to 135 track, and back to Orly, after
some other adjustments ...
Over 2 hours of UFO flying ... sometimes at many times the
speed of sound ... stoping here and there to look around,
identify an airport, etc, and not a single ABORT ...
Checking my virtual memory options, I note it has
a maximum size of 1536MB, with 1534MB currently
allocated! ... since I have 30 plus GB left on the
drive, maybe I could increase the maximum ... and be
flying in clear air, with extreme visibility ...
but will experiment with that another day ;=))
Thank you ... thank you ... thank you
I have certainly learned a lesson about push the
parameters ... if you want clear air and long distant
vision, be careful about MEMORY ABORTS ;=)) I kind
of knew it had something to do with my system.fgfsrc
preferences ...
So, the problem is sort of solved ... back to
quiet flying ... thanks again
Regards,
Geoff.
EOF
_________________________________________________________________
REALESTATE: biggest buy/rent/share listings
http://ninemsn.realestate.com.au
_______________________________________________
Flightgear-devel mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
