Here's an update: I added 2GB of swapspace and finally got inkscape to output an error instead of just locking up. I will output the error at the end of this message. The machine has 1.5GB of physical RAM and 2.5GB of swapspace. Inkscape was using about 3.2GB total when it crashed. It was working on tile 147,100.
Here's the error message: [#2 0% jobinit] Doing tileset 147,100 (area around 36.029222,27.421875) [#2 0% lowzoom] Rendering... ERROR The following command produced an error message: LC_ALL=C nice -n10 "inkscape" -z -w 256 -h 256 --export-area=0.000000:0.000000:14062.500000:14060.517420 --export-png="/tmp//5651.png_part" "/tmp/output-5651-z8.svg" > /tmp//5651.stdout Debug output follows: | | GLib-ERROR **: gmem.c:135: failed to allocate 3008976 bytes | aborting... | | Emergency save activated! | Emergency save completed. Inkscape will close now. | If you can reproduce this crash, please file a bug at www.inkscape.org | with a detailed description of the steps leading to the crash, so we can fix it. | | ** (process:5992): Message (recursed): Error: Inkscape encountered an internal error and will close now. | | aborting... | Aborted (core dumped) Additional info about the Error(s): [#2 0% lowzoom] LC_ALL=C nice -n10 "inkscape" -z -w 256 -h 256 --export-area=0.000000:0.000000:14062.500000:14060.517420 --export-png="/tmp//5651.png_part" "/tmp/output-5651-z8.svg" > /tmp//5651.stdout failed [#2 7% lowzoom] Splitting /tmp//5651.png_part (2 x 1)... Can't use an undefined value as a symbol reference at /usr/lib/perl5/GD/Image.pm line 175. Jeremy Original Message ----------------------- Ah yes, that does seem to be the case. The machine has 1.5GB of physical RAM and has 512MB of swap. Both are being used 100% for about 2 mins while rendering and then the machine either locks, or spews out a nasty error message. I guess I'll need more RAM if I want to render lowzoom, eh? Jeremy ----- Original Message ----- From: "Dirk-Lüder Kreie" <[EMAIL PROTECTED]> To: "Milenko" <[EMAIL PROTECTED]> Cc: <[email protected]> Sent: Tuesday, October 16, 2007 7:20 AM Subject: Re: [Tilesathome] Lowzoom crashes > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Milenko schrieb: >> There's one tile I forgot as well - 147, 96. This fails with a long >> inkscape error message about ways and segments and then ends with a >> "killed" message. >> > > I would think it just runs out of memory. > > - -- > > Dirk-Lüder "Deelkar" Kreie > Bremen - 53.0952°N 8.8652°E > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.7 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFHFJ5lFUbODdpRVDwRAlvRAKCbGYnHlBeee4owUswlkRPITNXqzgCfU4ce > PdR6J7Wh43uZ67SagObNXZU> =WPch > -----END PGP SIGNATURE----- > _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/tilesathome
_______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/tilesathome
