On Thu, Sep 11, 2008 at 10:58:15PM +0200, THE LoW wrote: > > [#31 0% Download] Tileset (12,2103,1345) around > 52.40,4.88 [#31 0% Download] Trying > ROMA [#31 0% tile] Rendering... > > This (above) is what the console output is looking like since... at > least 5 hours. > > "28279: inkscape -z -w 256 -h 256 > --export-area=0.000000:0.000000:878.910000:878.904445 > --export-png=/tmp/12_2103_1345_tVBsm/split-z12-1345.png > /tmp/12_2103_1345_tVBsm/output-z12.svg" > > has about 1:28.76 CPU time until now but doesn't do anything further. > > pmap -d 28279 shows > Address Kbytes Mode Offset Device Mapping > [...] > 0000000000e9b000 3807048 rw--- 0000000000e9b000 000:00000 [ anon ] > [...] > > Yep, that might also explain the swapping a few hours ago as this > machine has only 2gb of ram ;)
This is one complex tile. If you only have 2GB of RAM I recommend tuning down the MaxComplexity setting on your machine. Given that the tileset that failed has a size of File size: 12.4 MB I recomment setting it to something around 10000000 (and lower if you still see freezes). This will refuse tilesets that have a bgger byte size than the setting. There is a patch to implement auto-tuning of the maxcomplexity setting, but that hasn't been incorporated yet. spaetz _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
