Differences

This shows you the differences between two versions of the page.

--- doc:appunti:hardware:canoscan_9000f_mark_ii [2015/11/24 18:15] – [Invert and color balance] niccolo
+++ doc:appunti:hardware:canoscan_9000f_mark_ii [2017/12/04 10:00] – [ImageMagick convert, memory issue] niccolo
@@ Line 282: / Line 282: @@
   - Repeat the last two steps.
+===== ImageMagick convert, memory issue =====
+Executing **convert** on very large images can lead to memory exhausted issue. I experienced it converting a TIF scan into PNG (because I wish to avoid 24 bit Gimp limitation with TIF images):
+<code>
+convert very-big.tif very-big.png
+convert-im6.q16: DistributedPixelCache '127.0.0.1' @ error/distribute-cache.c/ConnectPixelCacheServer/244.
+convert-im6.q16: cache resources exhausted `very-big.png' @ error/cache.c/OpenPixelCache/3945.
+convert-im6.q16: No IDATs written into file `very-big.png' @ error/png.c/MagickPNGErrorHandler/1628.
+</code>
+It seems that ImageMagick is self-limiting the disk resource it will use, you can fix the configuration file **''/etc/ImageMagick-6/policy.xml''**, increasing the **1GiB** limit:
+<code xml>
+<policymap>
+  <policy domain="resource" name="memory" value="256MiB"/>
+  <policy domain="resource" name="map" value="512MiB"/>
+  <policy domain="resource" name="width" value="16KP"/>
+  <policy domain="resource" name="height" value="16KP"/>
+  <policy domain="resource" name="area" value="128MB"/>
+  <policy domain="resource" name="disk" value="1GiB"/>
+</policymap>
+</code>
+May be you can also increase the Memory resource, if you have enough:
+<code>
+convert -list resource
+Resource limits:
+  Width: 16KP
+  Height: 16KP
+  Area: 128MP
+  Memory: 256MiB
+  Map: 512MiB
+  Disk: 1GiB
+  File: 768
+  Thread: 2
+  Throttle: 0
+  Time: unlimited
+</code>
 ===== Web references =====