On Wednesday 22 March 2006 23:16, Curtis L. Olson wrote:
> 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 ...
>
I've been test running current CVS FlightGear for about three days straight
now, using my personal worldwide traffic database, using a wide variety of
different aircraft types and repaints. I'm seeing periodic increases and
decreases in memory use, as indicated by my KDE system performance applet.
I'm not sure how many aircraft are periodically loaded/unloaded, but I guess
quite a few. I presume that if there was a memory leak, my copy of FlightGear
would have trashed by now.
Cheers,
Durk
---
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
