[Tilesathome] Windows Client on dual core / windows ", " problem

Ed Loach ed at loach.me.uk
Tue Oct 7 18:40:43 BST 2008


Christian wrote:

> I did not verify if it's really fixed in unstable.

I just tried unstable. I had to add Java to my Virtual machine. And
I can't test it. Every request fails at the Inkscape call line with
an error I reported on this list previously that I get occasionally
which I thought is down to MaxTilesetComplexity. Except on unstable
on the German XP Pro virtual machine I get it every time. 1144,1366
doesn't look a particularly complex tile. The stable client was
running quite happily with 128MB RAM (at least for the first
request), but the failures below are after I've increased the memory
of the virtual machine to 1GB.

[#5   0% tile-z12] Rasterizing failed with runtime exception:
Inkscape returned non-zero status code 768 at SVG/Rasterize/Engine
/Inkscape.pm line 154.

[#5   0% tile-z12] Putting job (12,2402,1839) back due to 'Exception
in RenderSVG: Inkscape returned non-zero status code 768'
Use of uninitialized value in string eq at tilesGen.pl line 662.
[#5   0% tile-z12] Exception in RenderSVG: Inkscape returned
non-zero status code 768
[#6   0% upload] Tileset (12,1144,1366) around 51.26,-79.41
[#6   0% tile-z12] Generating SVG file
[#6   0% tile-z12] Rasterizing failed with runtime exception:
Inkscape returned non-zero status code 768 at SVG/Rasterize/Engine
/Inkscape.pm line 154.

[#6   0% tile-z12] Putting job (12,1144,1366) back due to 'Exception
in RenderSVG: Inkscape returned non-zero status code 768'
Use of uninitialized value in string eq at tilesGen.pl line 662.
[#6   0% tile-z12] Exception in RenderSVG: Inkscape returned
non-zero status code 768
[#7   0% upload] Tileset (12,3401,1990) around 5.05,118.96

So I can't test whether the problem is resolved in Unstable either.
I'll now retry unstable under my normal running conditions to see if
it is something that has changed today. It's not the same Heap
problem in this bug:
https://bugs.launchpad.net/inkscape/+bug/168914
the error reported is in the C++ runtime library.

I'm glad that Olf's got something that works at the moment though.

Ed






More information about the Tilesathome mailing list