If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

My first guess would be that the http request for the image is failing for some reason (maybe timing out?). If you save that image to your web host and then access it via the file system (instead of http), do you still have that problem?

"Please give us a simple answer, so that we don't have to think, because if we think, we might find answers that don't fit the way we want the world to be."
~ Terry Pratchett in Nation

btw it works 100% of the time if the script doesn't have imagick::blurImage() in it

My scripts never had a problem with that method before. Do you think it's a bug in ImageMagic? However if that's the case, I'm confused, because my host says they haven't updated ImageMagick since last year.

Last edited by evenstar7139; 01-14-2013 at 10:49 AM.

The better I get at programming, the more I appreciate arrays.Handy dandy things they are.

Tried that, nothing changed. When it fails I get a 500 internal server error and nothing else.

Something I noticed, though: When it's going to work, the script finishes quickly; when it's not, it spins its wheels for a few seconds and then I get the 500 error.

Anyhoo, do you think my host is at fault? Is there anything they could have done to cause this? I asked them about it and they're swearing up and down it's not them, and that it's my code, but I dunno...I have scripts whose code I haven't touched in a month that worked fine until a couple days ago =\

The better I get at programming, the more I appreciate arrays.Handy dandy things they are.

Outside of grepping the server logs to see what they say, I'm wondering if it could be some sort of file locking problem. You could try sticking in an $image->destroy(); once you're done with that object, just in case. (I'm at the straw-grasping stage here, so I'm not horribly optimistic.)

"Please give us a simple answer, so that we don't have to think, because if we think, we might find answers that don't fit the way we want the world to be."
~ Terry Pratchett in Nation

It would be different than the php-errors.log or whatever it's called. This would be the web server (Apache, IIS, whatever) http error log, which you may or may not have access to depending on your hosting plan.

"Please give us a simple answer, so that we don't have to think, because if we think, we might find answers that don't fit the way we want the world to be."
~ Terry Pratchett in Nation

...anywhere else in the script? If so, in each case, you'll probably have to follow it up with the same setResourceLimit() on each new such object. Otherwise we'll "talk" tomorrow (already past my bedtime)

"Please give us a simple answer, so that we don't have to think, because if we think, we might find answers that don't fit the way we want the world to be."
~ Terry Pratchett in Nation