QUOTE (fnord12 @ May 7 2008, 11:18 AM)

Unfortunately, i really have no way to reproduce the problem. I guess i could have them sit there while i create a bunch of blog posts and hope it happens.
Look at System Information in System Overview and make sure that Image::Magick says it's installed and ok. If not, you might have the same issue I ran into... bug in gcc-4.2.x and libgomp.so.1 and imagemagick. I had to rebuild imagemagic with --disable-openmp to fix it for now. It was actually making the imagemagick process go nuts and use up all the system ram.. until the kernel killed it off. I saw the same 500 errors in apache logs matching these problems. Haven't had a single 500 since then.
Oh, you can also test this by just running:
CODE
perl -MImage::Magick -e 1
If it takes any time, or especially gives any library errors, you're having the same issue. If it drops right back to a command prompt, you're fine.