John Denker wrote:
...
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
On 01/30/2009 03:44 AM, Tim Moore wrote:
Give the new version a try please.
All better now. Thanks.
VIRT = 460 peak, 440 steady state.
Readers who aren't closely following the context should note
that we are referring to the next branch of _simgear_.
Point of information: there are 2.6
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
On Wednesday, 28. January 2009, John Denker wrote:
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
On 01/28/2009 09:55 AM, Stefan Seifert wrote:
bloat is a hard word for something, which you did not even measure yet. The
VIRT column of top is basically useless for getting the memory usage. It's
just the virtual address space allocated to that process. That includes:
* memory allocated
John Denker wrote:
On 01/28/2009 09:55 AM, Stefan Seifert wrote:
bloat is a hard word for something, which you did not even measure yet.
The
VIRT column of top is basically useless for getting the memory usage. It's
just the virtual address space allocated to that process. That includes:
On Wednesday, 28. January 2009, John Denker wrote:
Ridiculing the bug report will not make the bug go away.
I did not want to ridicule the report in any way. Apologies if it came like
that. I just wanted to point out, that measuring memory usage unfortunately
is not as easy as it looks (no,
On 01/28/2009 10:20 AM, Tim Moore wrote:
Alternatively, try
starting with /sim/rendering/random-vegetation set to false.
Bingo.
That makes a huge difference. VIRT = 371 instead of 888.
I imagine there are a lot of trees around KASE...
Yes.
On Wed, Jan 28, 2009 at 11:31 AM, John Denker wrote:
On 01/28/2009 10:20 AM, Tim Moore wrote:
Alternatively, try
starting with /sim/rendering/random-vegetation set to false.
Bingo.
That makes a huge difference. VIRT = 371 instead of 888.
I imagine there are a lot of trees around
I noticed a change too after updating yesterday
I tried several times to fly online around KSFO , and after 10 - 15 minutes
, I came to a stop midair while the hard drive thrashed away ... I finally
had to kill X to get back some control over my system ...
It definately wasn't like this
syd adams wrote:
I noticed a change too after updating yesterday
I tried several times to fly online around KSFO , and after 10 - 15
minutes , I came to a stop midair while the hard drive thrashed away
... I finally had to kill X to get back some control over my system ...
It
Thanks Michael, I'll try it out ...
On Wed, Jan 28, 2009 at 6:04 PM, Michael D. Smith mdsmi...@highland.netwrote:
syd adams wrote:
I noticed a change too after updating yesterday
I tried several times to fly online around KSFO , and after 10 - 15
minutes , I came to a stop midair
12 matches
Mail list logo
