Yesterday I wrote: > Inkscape just crashed - something about too many heap sections. > I think this is a known Windows bug I've mentioned here before. > However the message in stderr is different - > > [#11 100% ] Tileset (12,1237,1512) around 42.52,-71.24 > [#11 0% maplint-z12] Splitting stripe 0... Can't use an > undefined value as a symbol reference at > d:/tilesathome/perl/lib/GD/Image.pm line 175. > > So I mention it in case the Inkscape error is a bit misleading, > and the above is more important.
This morning I find the same: [#79 100% ] Tileset (12,1231,1517) around 42.20,-71.76 [#79 0% maplint-z12] Splitting stripe 0... Can't use an undefined value as a symbol reference at d:/tilesathome/perl/lib/GD/Image.pm line 175. What is different about this crash from previous Inkscape ones is that it now drops you out of loop mode rather than putting the tile back and continuing (well, apart from the problem with the Inkscape error dialog box pausing everything until you click to continue, but that I think is an issue with the Windows version as well). I've not tried rendering these tiles manually to see whether it is tile related. Do they contain a little used feature which is trying to use something strange as a symbol reference? Ed _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
