(Umbraco 7.5.11)

ImageProcessor appears to work perfectly in our development setup. In our production setup it doesn't render gif images as expected in the back-end or in served pages. For example, Browsing the production server using a url similar to the following...

https:/ /prodserver/media/6600/sample.gif?anchor=center&mode=crop&width=500&height=200

...generates the following ysod.

Server Error in '/' Application.

Property is not supported.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 

Exception Details: System.ArgumentException: Property is not supported.

Source Error: 

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace: 
[ArgumentException: Property is not supported.]
   System.Drawing.Image.SetPropertyItem(PropertyItem propitem) +88
   ImageProcessor.ImageFactory.Save(Stream stream) +173
   ImageProcessor.Web.HttpModules.<ProcessImageAsync>d__34.MoveNext() +2430
   System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) +93
   System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +52
   System.Web.TaskAsyncHelper.EndTask(IAsyncResult ar) +60
   System.Web.AsyncEventExecutionStep.OnAsyncEventCompletion(IAsyncResult ar) +9699833

This only happens with gif images. Removing the web.config ImageProcessor configuration elements clears the error.

Issuing the same request in the development environment...

http:/ /devserver/media/6600/sample.gif?anchor=center&mode=crop&width=500&height=200

...returns the image as expected.

(The environments are hosted in-house on different but similarly configured servers, the development setup is 64 bit using http, the production environment is 32 bit using https.)

Can anyone shed any light as to why this is happening.

Thanks,

A

Update: Setting 'preserveExifMetaData' to false in processing.config has fixed the issue. What is the signigicance of this?