QGIS » QGIS Application

I cannot confirm, just tried on WinXP, f42443c9 (SVN r15701).

Can you provide more specifics on what are you doing, what data are you using (if any) and QGIS revision.

I successfully created an A4 600 dpi map (11Mb in png, 3 Mb in vector pdf) on Kubuntu 10.10 (64 bits).

However, I tried an A0 at 600 dpi in png, it failed. First I was asked:

To create image 28086x19866 requires about 1673 MB of memory. Proceed?

I clicked yes (my PC has 4GB of RAM). Then there was the message:

Creation of image with 28086x19866 pixels failed. Export aborted.

No crash for me however. My test dataset is pure vector: OSM data for Milano and surrounding, stored on postgis thanks to osm2postgresql, using rule-based render.

I was able to export the above in A0 but in vector pdf (20 Mega bytes). If you can export in vector pdf, you can convert later on in raster, as a workaround (for instance, gimp does this, but command line solutions might be less memory hungry).

I made a tougher test: export 20% of OSM data for Italy on a 11 meter by 8 meter (sic) pdf vector map. It crashed after a few minutes (Kubuntu 10.10 64 bits, qgis trunk 1.7.0 5b1e7999 (SVN r15719)).

It seems that the size limit for getting the bug is OS or machine specific. @gislab: what if you try to export a very large file?

Replying to [comment:2 mayeulk]:

To create image 28086x19866 requires about 1673 MB of memory. Proceed?
I clicked yes (my PC has 4GB of RAM). Then there was the message:
Creation of image with 28086x19866 pixels failed. Export aborted.

It failed with the same message on WinXP, fbd10b55 (SVN r15741).
It might be running into some system limitations, the file that is being created would have 600 millions pixels.

I'm running QGIS f8e10a33 (SVN r15725), Fedora 14, 2GB RAM, and I get the same messages as mayeulk and gislab, if I try to export in A0 at 600 dpi in png format.

If I choose a higher resolution (800 dpi), then I directly get the Export aborted message, without any crash.

Was away for a bit, here are the answers to all of the great questions and discussion that have been going on... At the time of reporting, I was running 15622. I have since updated to 15740 and it appears to be resolved as far as I can tell.

My data is all basic shapefiles, census county boundaries, plus a few million point features, and the standard map elements: scale bar, title, north arrow, legend, notes.

Another symptom of the crash was that my composer window would go blank (As you can see in the attached photo). I would have to shut down qgis, don't save the file, and reopen in order to get my saved composer layout back.

I tested on Ubuntu machine 32 bit 4gb of ram, qgis trunk.

I added a 3gb raster image and created a A0 layout, streching the image almost at full layout extent.

I can produce a PDF at 300dpi and 400 dpi. At 500dpi QGIS crashes silently with a seg fault.

I get the same problem ("bad allocation" exception) under Windows XP with both 1.6.0 and trunk a954488.

I created a A0 layout and succesfully printed via the pdfFactory driver to a valid PDF at 300 dpi. I then enabled a layer to add text... and it generated the exception. Export to PDF and SVG fail with the same exception. Export to image reported "Creation of image 14043x9933 pixels failed. Export aborted."

QGIS has to be restarted to allow Print Composer to run again.

Reducing the resolution to 200 dpi word printing directly (took over 10 minutes!) Exporting as a PNG worked at this resolution. Exporting as a PDF didn't crash QGIS, but then crashed Adobe Reader X. Exporting to SVG generated the "bad allocation" exception.

is it the same ticket in #4821?
this error affects export both pdf and tif, depending on resolution.
in my case with A3, 500 dpi is the limit and by the way often qgis crashes or the resulting file has some errors.

no, i can't.
as it is a very blocking problem (it' s necessary to share information not only to handle), do you think/know if there is any "workaround" solutin to this (windows) bug?

stefano campus wrote:

no, i can't.
as it is a very blocking problem (it' s necessary to share information not only to handle), do you think/know if there is any "workaround" solutin to this (windows) bug?

are you on XP? or a later windows version? 32 or 64bit?

win7 professional 32bit 4GB RAM