On 01/28/2009 02:25 AM, Erik Hofman wrote:
> I didn't check it myself yet, but every once in a while I have to do a
> 'make clean' before 'make install' for this sort of things (both for
> Simgear and FlightGear)
Good advice; thanks.
Alas after doing that, the memory bloat remains, as bad as ever.
I saw it peak at 905 megs at KASE before falling back to 888 megs.
While were in the neighborhood: I did a fresh cvs update and the
symptoms are the same, so we can't blame it on non-authoritative
sources.
All this is with OSG 2.7.7. Debian etch.
On 01/28/2009 01:18 AM, Tim Moore wrote:
>> I'm seeing about 10% less virtual memory usage with the current next branch
>> compared to the 1.9 release.
Puzzling.
>> What revisions of sg and fg were you running a few
>> weeks ago?
That last well-behaved version I can identify with confidence
is a pull from Pigeon's repository, with the following HEAD:
commit f489aed160cfa57bc8005cb4feb7105bc919b247
Author: Melchior Franz <mfr...@flightgear.org>
Date: Sun Jan 11 00:49:39 2009 +0000
hits are consumed by default (prevents actions in lower dialogs)
>> How were you running flightgear (aircraft, starting location, etc.)?
That's a sensible and relevant question. I observe problem to be
not particularly aircraft-sensitive (the default c172p will do) ...
but it is definitely location-sensitive.
KSFO ... 613 MB steady state
KASE ... 905 MB peak, 888 steady state
The bloat is 100% reproducible chez moi when there are no options
other than --airport. Sometimes "top" misses the peak, but the
steady state is bad enough.
Similarly the lack of bloat is 100% reproducible with older versions.
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
