> The inkscape issue seems to be a limitation > of windows - > even on machines with 4GB of RAM, inkscape will crash at about > 1.3 - 1.4GB > of RAM usage.
I get that occasionally which is why I was trying to set MaxTilesetComplexity in the first place. There seem to be two issues. One is the bug which throws up the GCC too many heaps dialog, and another I get is when something nasty happens and throws up a C++ related dialog box. Both somewhere in Inkscape. > I'm not sure if there's a way around this > limitation (is it > present in 64-bit windows?), I'm using 64-bit Windows Vista (and 4GB RAM), but can't find a 64-bit Inkscape build so guess that is why it doesn't seem to make a difference. > The crashing is a big issue - I > have to check > the clients constantly since inkscape throws up a dialog box > when it crashes > (even though it's running in command line!), which stops the > client from > rendering. I don't get it crashing very often. I do have 4GB RAM and have set MaxTilesetComplexity to about 12,500,000 (though this goes down and down while the request loop processes and settled somewhere about 8,000,000 even without any crashes or Inkscape problems - if it gets too low I just create a stopfile, do an svn up, to check I'm up to date and kick the loop off again). Is there a setting which lets you do simpler tiles in one go and more complex ones in stripes? Or is that a bit too advanced for the client at present? Ed _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
