I have had my Drupal installation in production for 1,5 years without any problems. After I decided to install ImageBrowser that requires ImageCache the IIS service has started to crash. I have investigated further and it seems that IIS crash at every three images that ImageCache has to resize for me.

I have tried to increase the amont of memory PHP is allowed to use (in php.ini) to 512MB, but that made no difference.

Please advice.

Comments

tr’s picture

tr commented
Project: Drupal core » Image Browser
Version: 6.15 » 6.x-2.x-dev
Component: other » Code

I think this is more appropriate for the Image Browser queue, no indication here that it's a core bug.

peter törnstrand’s picture

peter törnstrand commented
Project: Image Browser » ImageCache

Well, why TR assigned it over to Image Browser module is beyond me. It's clearly an ImageCache issue.

tr’s picture

tr commented

It wasn't clear to me that Image Cache was definitely the cause of the problem, but I was sure that the issue didn't belong in the Drupal queue. I figured you would move it again if necessary...

@andersh: If you can change your presets so Image Cache isn't scaling your images, you can tell for sure whether it's the Image Cache scaling that's causing the crash, or something else related to Image Browser and/or Image Cache.

andersh’s picture

andersh commented

Image Browser does in reality nothing other then produce some links and tags that goes into the database. It calls on imageCache to do the serverside work.. I have no "test-system", and I asume that if I change the presets all my images goes bad? If the client crashed I would put it in the queue for ImageBrowser (is uses some ajax stuff), but the one doing the serverside job is ImageCache, and it's the server that crashes.

Can you confirm that I can change the presets without published images going down?

fizk’s picture

fizk commented
Priority: Critical » Normal
Status: Active » Closed (cannot reproduce)