From: <ric...@gm...> - 2015-02-25 10:05:46
|
Before finalizing 3.4.1, you might want to consider this: http://forum.flightgear.org/viewtopic.php?f=17&t=25473 <http://forum.flightgear.org/viewtopic.php?f=17&t=25473> I’m trying to set up a git bisect to track down the offending commit but running into some problems getting a version between 3.2 and 3.4 to run after compiling. I suspect it’s because I’m not succeeding in getting the simgear commit to match the flightgear commit. Richard |
From: <ric...@gm...> - 2015-02-25 22:00:53
|
Having done some more testing, which is documented on the forum, I can confirm that the route manager has a fairly nasty bug that results in memory consumption increasing throughout a flight. The rate at which it increases appears to increase with the number of waypoints, with a flight of 20 waypoints experiencing an increase of over 2GB per hour in my tests. The longer the flight, the more waypoints it tends to have and the more unsustainable the growth becomes. Hooray has been able to replicate the issue with minimal startup profile, rendering disabled, etc. The analysis starts here: http://forum.flightgear.org/viewtopic.php?f=17&t=25473#p233093 <http://forum.flightgear.org/viewtopic.php?f=17&t=25473#p233093> I’ve identified the commit that introduced the problem by bisecting: https://gitorious.org/fg/flightgear/commit/7317aff22d393a5aaef6b5e84571fb86a465c002 <https://gitorious.org/fg/flightgear/commit/7317aff22d393a5aaef6b5e84571fb86a465c002> Looks like one for James. I’ll be happy to re-test if you can find the problem and submit to flightgear next. Regards, Richard |
From: James T. <zak...@ma...> - 2015-02-25 23:00:19
|
> On 25 Feb 2015, at 22:00, ric...@gm... wrote: > > Looks like one for James. I’ll be happy to re-test if you can find the problem and submit to flightgear next. Good catch. I’ve pushed commit: e1def2219323046f5348e1ba9b3839ae42da7efe If you can test a build which includes this change, hopefully the memory use is back to normal. Kind regards, James |
From: <ric...@gm...> - 2015-02-26 10:03:40
|
Thanks James, that has fixed the issue in next. I’m assuming this will go into 3.4.1. Will it also be backported into 3.4.0? Richard > On 25 Feb 2015, at 22:59, James Turner <zak...@ma...> wrote: > > >> On 25 Feb 2015, at 22:00, ric...@gm... wrote: >> >> Looks like one for James. I’ll be happy to re-test if you can find the problem and submit to flightgear next. > > Good catch. I’ve pushed commit: > > e1def2219323046f5348e1ba9b3839ae42da7efe > > If you can test a build which includes this change, hopefully the memory use is back to normal. > > Kind regards, > James > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for all > things parallel software development, from weekly thought leadership blogs to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > Flightgear-devel mailing list > Fli...@li... > https://lists.sourceforge.net/lists/listinfo/flightgear-devel |
From: Rebecca N. P. <reb...@zo...> - 2015-02-26 10:07:50
|
> I’m assuming this [bug fix] will go into 3.4.1. Will it also be backported into 3.4.0? That's a meaningless question: the release branch is 3.4 (though git does call it "release/3.4.0"), .0 and .1 are the individual releases from it. |
From: <ric...@gm...> - 2015-02-26 10:30:24
|
If people press the link on this page: http://www.flightgear.org/download/ <http://www.flightgear.org/download/>, where it says, "Download Flightgear v3.4.0”, do they get this fix? If they press it at some time in the future (when presumably it will say, “Download Flightgear v3.4.1”) will they get the fix? I assume yes. > On 26 Feb 2015, at 10:07, Rebecca N. Palmer <reb...@zo...> wrote: > >> I’m assuming this [bug fix] will go into 3.4.1. Will it also be backported into 3.4.0? > That's a meaningless question: the release branch is 3.4 (though git > does call it "release/3.4.0"), .0 and .1 are the individual releases > from it. > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for all > things parallel software development, from weekly thought leadership blogs to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > Flightgear-devel mailing list > Fli...@li... > https://lists.sourceforge.net/lists/listinfo/flightgear-devel |
From: James T. <zak...@ma...> - 2015-02-26 17:31:40
|
> On 26 Feb 2015, at 10:30, ric...@gm... wrote: > > If people press the link on this page: http://www.flightgear.org/download/ <http://www.flightgear.org/download/>, where it says, "Download Flightgear v3.4.0”, do they get this fix? No. > > If they press it at some time in the future (when presumably it will say, “Download Flightgear v3.4.1”) will they get the fix? I assume yes. > Yes. Kind regards, James |