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 with malloc but not yet used, which means that there is no > physical RAM used for it > * mmap'ed files > * shared memory > and I'm sure some more which I'm not thinking of. > > According to VIRT, amarok uses > 730MB on my system which is a quite > ridiculous number. > > If you're interested in memory usage of a process, a _start_ is the RES > column. It's far nearer to the "truth" even though it does not count swap > usage of the process. But if FG causes swapping, you don't need top to tell > you :) That'd be obvious.
Uhhh, the bloated versions of FG do cause swapping. And yes, it is plenty obvious. It's hard to shoot an approach in the up-to-date version of FG because if FG is running acrobat is swapped out and I can't look at the approach plate. And it's hard to cut-and-paste measurements into email because the mailer is swapped out. All indications are that FG is using a high percentage of its VIRT. Older versions still run just fine. Ridiculing the bug report will not make the bug go away. ------------------------------------------------------------------------------ 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
