I haven't had a chance to look at this (and I may not have a chance any
time soon) but someone has reported to me that they believe that the .ac
loader is leaking memory in terms of texture loading. In other words,
an OBJECT_STATIC is loaded and unloaded as we would want when a tile is
loaded or unloaded, but the associated textures are not unloaded.
This person is working on creating 3d visual objects for many DAFIF
objects, airspaces, approaches, waypoints, etc. His automated tools can
create a huge number of objects and he is finding that even though the
.ac files seem to be unloaded, there is still a big memory leak as we
fly, and he thinks it is that textures are not being freed. The more
objects he includes, the shorter distances he can fly before his machine
gives up and spits FlightGear into the bit bucket.
There is something not right, the analysis may not yet be 100% right on,
but we do appear to have a major leak someplace ...
Curt.
--
Curtis Olson http://www.flightgear.org/~curt
HumanFIRST Program http://www.humanfirst.umn.edu/
FlightGear Project http://www.flightgear.org
Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
