How to find reason for Generic GDI+ error when saving an image?
Solution 1
While I still did not find out the reason what exactly caused the error when saving the image, I found a workaround to apply:
const string i1Path = @"c:\my\i1.jpg";
const string i2Path = @"c:\my\i2.jpg";
var i = Image.FromFile(i1Path);
var i2 = new Bitmap(i);
i2.Save(i2Path, ImageFormat.Jpeg);
I.e. by copying the image internally into a Bitmap
instance and saving this image instead of the original image, the error disappeared.
I'm assuming that by copying it, the erroneous parts the caused the original Save
call to fail are being removed an/or normalized, thus enabling the save operation to succeed.
Interestingly, the so stored image has a smaller file on disk (16 kB) than its original source (26 kB).
Solution 2
First of all make sure, that the desired folder has Read/Write permissions. Changing the permissions solved this problem for me.
Solution 3
Solution is here, you must dispose image object to release the memory on the server.
Try use using
statement. Make sure destination directory on server exists too.
Solution 4
The reason may be that the image is loaded lazily and the loading process is not yet finished when you try to save it.
Following what's said in this blog post (assuming you're German by the picture you linked in your question) provides a possible solution. Also this SO question's accepted answer indicates this is due to the fact the image file you're trying to save to is locked.
EDIT
For Ulysses Alves, from the linked blog entry: If you load an image using Image.FromFile()
it remains locked until it is disposed of. This prevents calls to Save()
.
pictureBox1.Image = Image.FromFile("C:\\test\\test1.jpg");
pictureBox1.Image.Save("C:\\test\\test2.jpg");
The above code throws an error.
To make it work, you need to copy the image. The following code works:
pictureBox1.Image = Image.FromFile("C:\\test\\test1.jpg");
Image copy = pictureBox1.Image;
copy.Save("C:\\test\\test2.jpg")
Solution 5
I found this question because I also faced the similar error and the file was actually created with zero length (if you don't see any file, first check the permissions to write into folder as other answers suggest). Although my code was slightly different (I use stream
to read the image from memory, not from file), I think my answer may be helpful to anyone facing similar problem.
It may looks counter-intuitive, but you can't really dispose memory stream until you finish with image.
NOT WORKING:
Image patternImage;
using (var ms = new MemoryStream(patternBytes)) {
patternImage = new Bitmap(ms);
}
patternImage.Save(patternFile, ImageFormat.Jpeg);
Just don't dispose the stream until you done with image.
WORKS:
using (var ms = new MemoryStream(patternBytes)) {
patternImage = new Bitmap(ms);
patternImage.Save(patternFile, ImageFormat.Jpeg);
}
What is misleading:
- Error message doesn't really tell you anything
- You can see the image properties, like width and height, but can't save it
Uwe Keim
German developer. Some of my apps: SharePoint Systemhaus Göppingen (zwischen Stuttgart und Ulm) Eigene Homepage erstellen Test Management Software Windows 10 Ereignisanzeige Very proud father of Felix (2012) and Ina (2014). Loves running, climbing and Indian food. Code Project member #234.
Updated on July 09, 2022Comments
-
Uwe Keim almost 2 years
Having a code that works for ages when loading and storing images, I discovered that I have one single image that breaks this code:
const string i1Path = @"c:\my\i1.jpg"; const string i2Path = @"c:\my\i2.jpg"; var i = Image.FromFile(i1Path); i.Save(i2Path, ImageFormat.Jpeg);
The exception is:
System.Runtime.InteropServices.ExternalException occurred
A generic error occurred in GDI+.
at System.Drawing.Image.Save(String filename, ImageCodecInfo encoder, EncoderParameters encoderParams)
at System.Drawing.Image.Save(String filename, ImageFormat format)
at ...As far as I can see, there is nothing special about the image. It is approx 250 pixels in size and can be opened in e.g. Windows Image Viewer or Paint.NET:
(Since the image above, after being uploaded to Stack Overflow does not produce the error anymore, I've put the original image here)
What I discovered is that upon calling the
Save
method, the destination image file is being created with zero bytes.I am really clueless on what causes the error.
My questions:
- Can you think of any special thing that would hinder .NET from saving the image?
- Is there any way (beside panicing) to narrow down these kind of errors?
-
Thorsten Dittmar about 11 yearsI don't really get why this answer is being downvoted ... maybe someone could explain?
-
Uwe Keim about 10 yearsThis sounds like a really bad answer to me.
-
user426364 almost 10 yearsThis worked for me as well. I had to force garbage collection afterwards, on account of the 'out of memory exception' that was caused.
-
Darren Wainwright about 9 yearsWorked for me too - no idea why. Only had the issue with jpg images (png etc were fine)
-
Michael Blake over 8 years"Make sure destination directory on server exists" was my issue
-
Jesse Chisholm over 8 yearsI had this issue with .bmp, .jpg, and .png but I wasn't loading a file, I was creating it in memory and trying to save it.
CAUSE:
the original bitmap is tied to the stream it loaded from (FileStream
orMemoryStream
). The cloned bitmap it not tied to a stream, as it copied the pixel bytes. It might also have worked toFreeze
the original bitmap before saving it. -
Jesse Chisholm over 8 years@UweKeim - a
using
on a temporaryIDisposable
object just ensures the GC is called for it as soon as it is safe to do so. -
Jesse Chisholm over 8 yearsI can see where that would change when/where you got the exception if you did not have permission to create that file. :) :) But it would be weird if this resolves the other issues in the OP.
bitmap.Freeze(); bitmap.Save(...);
orvar other = new Bitmap(bitmap); other.Save(...);
Both of these ensure that the bitmap being saved is not bound to a stream beforeSave
is called. -
Jesse Chisholm over 8 yearsSince the down voters didn't leave a comment, we may never know. :)
-
GWR about 8 years"Make sure destination directory on server exists" was my issue as well
-
daveD over 7 years"Make sure destination directory on server exists" was my issue as well. So easy to overlook.
-
Artur Kędzior about 7 yearsThat's like 90% of the cases :-)
-
Ulysses Alves over 6 yearsI couldn't find anything related with this subject in the linked post. Could you please provide us a code example in your answer?
-
Sarvjeet Verma over 5 yearsI had a similar kind of issue and this solution worked for me as well. Thanks.
-
Eakan Gopalakrishnan about 5 yearsis it mentioned in the documentation about reading an image and converting it into a bitmap before it is saved?
-
Frank Tzanabetis about 4 yearsMy guess is that the line Image copy = pictureBox1.Image; is not creating a copy, but merely creating a new reference.
-
Abdelsalam Hamdi over 3 yearsI got this error for the second time, some how the first time I used the same solution as u. but the second time it's not working
-
CookieGamer733 over 2 yearsi have an issue of the picture quality dropping rapidly, how do i fix this