On Tue, 2012-01-17 at 17:49 +0000, Martin Spott wrote: > Surprisingly there seems to be another limit with really large areas. > Supplying the flags "--xdist=19 --ydist=18" (around a center at > "--lon=9.875 --lat=49.375", but there's no difference with "--lon=10 > --lat=49") seem to work nicely (test is still running, but looks good > so far), but just swapping the numbers for xdist and ydist or > selecting > any bigger number for either of them results in "fgfs-construct" > pretending to having finished successfully, but writing not more than > approx. 30 MByte of terrain tiles to the disk. > >
Martin, this sounds like the memory leak that I reported a few months ago that no one else could see. If you watch the memory use during the build I suspect that as each tile is processed it memory allocation will remain thus by the time you get to the end there is no more memory and the process fails. Jason Cox ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
