20,741
edits
Troubleshooting crashes: Difference between revisions
Jump to navigation
Jump to search
m
→Tracking RAM utilization: http://forum.flightgear.org/viewtopic.php?f=8&p=214113#p214076
m (→Tracking RAM utilization: http://forum.flightgear.org/viewtopic.php?f=8&p=214113#p214076) |
|||
| Line 148: | Line 148: | ||
=== Reporting incompatible default settings === | === Reporting incompatible default settings === | ||
Once you have located and identified settings that seem to cause reproducible issues with your hardware, it would be a good idea to report these settings using the issue tracker, so that these can hopefully be made optional in the upcoming release: http://flightgear-bugs.googlecode.com/ | Once you have located and identified settings that seem to cause reproducible issues with your hardware, it would be a good idea to report these settings using the issue tracker, so that these can hopefully be made optional in the upcoming release: http://flightgear-bugs.googlecode.com/ | ||
=== Tracking RAM utilization === | |||
[[File:Fg-3.2-minimal-settings.png|400px|Screen shot showing FlightGear 3.2 using the minimal startup profile with frame spacing and frame counter displayed.]] | |||
{{WIP}} | |||
{{FGCquote | |||
|My measurements (below) suggest that terrain mesh (as loaded at "bare" <br/> | |||
LOD) is the dominant memory user, with only small contributions from the <br/> | |||
aircraft, terrain textures, and random objects/trees/buildings. | |||
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32445574/ | |||
|title=<nowiki>Re: [Flightgear-devel] Memory consumption reduction</nowiki> | |||
|author=<nowiki>Rebecca N. Palmer</nowiki> | |||
|date=<nowiki>2014-06-11</nowiki> | |||
}} | |||
}} | |||
{{FGCquote | |||
|In Ubuntu 64-bit, measured using System Monitor after it stabilizes (~1min)<br/> | |||
Except as stated, c172p stationary on KSFO 28R, night, Terrasync <br/> | |||
scenery, default settings (regional textures, LOD range 1500/9000/30000)<br/> | |||
baseline: 2.3-2.4GB<br/> | |||
Changing shader effects level or enabling/disabling random <br/> | |||
objects/trees/buildings: no significant change<br/> | |||
Global texture set: 2.2GB<br/> | |||
DDS texture set: 2.2GB<br/> | |||
Global texture set, no Textures.high: 2.1GB (and some missing effects <br/> | |||
textures, as they don't have the "try Textures.high first, then <br/> | |||
Textures" fallback mechanism)<br/> | |||
LOD range 1500/9000/10000: 1.4GB<br/> | |||
LOD range 1500/2000/30000: 2.3GB<br/> | |||
LOD range 500/9000/30000: 2.3GB<br/> | |||
1.0 scenery (from flightgear-data 3.0 due to above issue): 1.1GB<br/> | |||
Ocean location: 0.75GB<br/> | |||
F-14: 2.1GB<br/> | |||
777-200: 2.6GB<br/> | |||
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32445574/ | |||
|title=<nowiki>Re: [Flightgear-devel] Memory consumption reduction</nowiki> | |||
|author=<nowiki>Rebecca N. Palmer</nowiki> | |||
|date=<nowiki>2014-06-11</nowiki> | |||
}} | |||
}} | |||
[[File:Fg-3.2-RAM-utilization-in-minimal-mode.png|right|500px|htop showing FlightGear 3.2 RAM utilization when in minimal startup mode]] | |||
== Further assistance == | == Further assistance == | ||