serious BUG in converting gifs?

Post any defects you find in the released or beta versions of the ImageMagick software here. Include the ImageMagick version, OS, and any command-line required to reproduce the problem. Got a patch for a bug? Post it here.
Post Reply
joe7

serious BUG in converting gifs?

Post by joe7 »

Hi,

I've experienced a critical problem when converting images.

With _some_ gif images, the convert process just _never_ ends, it's 'working' and working, but never ends.
CPU usage is at ~98%, and it's swapping like crazy, 1GB temp file / process!

It's a very serious problem, as in my case it's triggered by image upload process, so think of it happening with 5 files at the same time.
Results=> Load ~60, whole host is ~down, temp dir full-> other processes fail.

I'm using debian/stable,
im version is 6.2.4
command used: "/usr/bin/convert" "-coalesce" "filename.gif" "-size" "150x150" "-geometry" "150x150" "-strip" "-deconstruct" "/tmp/whatever" 2>/tmp/someMoreTemp

Is it fixed in any newer version by any chance?
rmagick
Posts: 245
Joined: 2006-03-16T17:30:48-07:00
Location: Durham, NC, USA

Re: serious BUG in converting gifs?

Post by rmagick »

Is this a 64-bit machine by any chance?
joe7

Re: serious BUG in converting gifs?

Post by joe7 »

rmagick wrote:Is this a 64-bit machine by any chance?
it's an Intel Core2 Quad,
but met with the same bug on Intel Pentium 4 2.0Ghz too, non 64bit
rmagick
Posts: 245
Joined: 2006-03-16T17:30:48-07:00
Location: Durham, NC, USA

Re: serious BUG in converting gifs?

Post by rmagick »

I've noticed that IM's color reduction algorithm for GIF uses a lot of memory on 64-bit machines, but if you're seeing the same conditions on a 32-bit machine then this isn't the same issue.
joe7

Re: serious BUG in converting gifs?

Post by joe7 »

rmagick wrote:I've noticed that IM's color reduction algorithm for GIF uses a lot of memory on 64-bit machines, but if you're seeing the same conditions on a 32-bit machine then this isn't the same issue.
it's definitely NOT the same bug.
The problem is NOT just the memory usage:
- It's doing some infinite loops, converting a 20k size GIF was going for _4 hours_ before we killed the process.
- Also, temp file usage was hitting some limit at ~1GB of size, that's the only reason it didn't grow any further. (temp file size was the same for 3 different gifs, all over 1GB)
Post Reply