Why do I get image.gd.inc error when I have Imagemagick installed?
droolpal - March 31, 2009 - 16:14
| Project: | ImageAPI |
| Version: | 6.x-1.5 |
| Component: | ImageAPI Imagick |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
I get an out of memory error (image.gd.inc on line 190) when trying to edit an image node.
Why is this happening when I only have the Imagemagick module installed? Why do I get a GD error? I specifically chose Imagemagick because of the better memory use.
#1
It depends on where the resizing is done. If it's not using the ImageAPI then it'll fall back to core's toolkit and use that. The Image module has a file named image.imagemagick.inc that's an ImageMagick toolkit for core that you can place in your /includes directory.
#2
Fixed.
My PHP memory limit was 32M. I added image.imagemagick.inc to /includes, then enabled the Imagemagick as my toolkit. This fixed the problem! The problem image did not throw the out of memory error any more.
I also upped the PHP memory limit in settings.php to 128M, now all editing feels faster, the whole site feels faster (in admin mode)
#3
Automatically closed -- issue fixed for 2 weeks with no activity.