[OSM-talk] Osmarender 5

[Jon Bright]

Hi,

80n wrote:
> 
> This version contains many improvements to the rendering engine and lots 
> of improvements to the tiles at home rules files.

I upgraded my t at h installation earlier today.  The first 7 rendered 
tiles were fine, but the 8th got this error:

[#8   0% jobinit] Doing tileset 1172,1561 (area around 39.266215,-76.948242)
[#8 100% default] Finished 1172,1561 for layer default
[#8   0% maplint] Rendering...                        sh: line 1: 27824 
Aborted                 LC_ALL=C nice "inkscape" -w 256 -h 256 
--export-area=0.000000:0.000000:878.910000:878.742820 
--export-png="/tmp//14413.png_part" "/tmp/output-14413-z12.svg" 
 >/tmp//14413.stdout 2>/tmp//14413.stderr
ERROR
   The following command produced an error message:
   LC_ALL=C nice "inkscape" -w 256 -h 256 
--export-area=0.000000:0.000000:878.910000:878.742820 
--export-png="/tmp//14413.png_part" "/tmp/output-14413-z12.svg" > 
/tmp//14413.stdout
   Debug output follows:
   |
   | (inkscape:27824): Gdk-CRITICAL **: gdk_display_list_devices: 
assertion `GDK_IS_DISPLAY (display)' failed
   |
   | ** (inkscape:27824): WARNING **: GC Warning: Out of Memory! 
Returning NIL!
   |
   | terminate called after throwing an instance of 'std::bad_alloc'
   |   what():  std::bad_alloc
   |
   | Emergency save activated!
   | Emergency save completed. Inkscape will close now.


This was followed by several more errors on different tiles.  Since 
there's no sign that the machine itself was out of memory (and it's a 
2GB machine without that much running), I'm guessing that this was 
Inkscape artificially limiting itself.  If this is the case, how can I 
get Inkscape to increase this limit?  Indeed, should I increase that limit?

-- 
Jon Bright
Silicon Circus Ltd.
http://www.siliconcircus.com