Image.Save(..) throws a GDI+ exception because the memory stream is closed
Asked Answered
D

17

123

i've got some binary data which i want to save as an image. When i try to save the image, it throws an exception if the memory stream used to create the image, was closed before the save. The reason i do this is because i'm dynamically creating images and as such .. i need to use a memory stream.

this is the code:

[TestMethod]
public void TestMethod1()
{
    // Grab the binary data.
    byte[] data = File.ReadAllBytes("Chick.jpg");

    // Read in the data but do not close, before using the stream.
    Stream originalBinaryDataStream = new MemoryStream(data);
    Bitmap image = new Bitmap(originalBinaryDataStream);
    image.Save(@"c:\test.jpg");
    originalBinaryDataStream.Dispose();

    // Now lets use a nice dispose, etc...
    Bitmap2 image2;
    using (Stream originalBinaryDataStream2 = new MemoryStream(data))
    {
        image2 = new Bitmap(originalBinaryDataStream2);
    }

    image2.Save(@"C:\temp\pewpew.jpg"); // This throws the GDI+ exception.
}

Does anyone have any suggestions to how i could save an image with the stream closed? I cannot rely on the developers to remember to close the stream after the image is saved. In fact, the developer would have NO IDEA that the image was generated using a memory stream (because it happens in some other code, elsewhere).

I'm really confused :(

Dunant answered 3/12, 2008 at 7:4 Comment(2)
I got this comment from @HansPassant in another question. You'll get this exception whenever the codec has trouble writing the file. A good debugging statement to add is System.IO.File.WriteAllText(path, "test") before the Save() call, it verifies the basic ability to create the file. You'll now get a good exception that tells you what you did wrong.Forensic
You should image2.Save inside using block. I think the originalBinaryDataStream2 was automatically disposed at the end of the using. And that would throw the exception.Statistics
M
192

As it's a MemoryStream, you really don't need to close the stream - nothing bad will happen if you don't, although obviously it's good practice to dispose anything that's disposable anyway. (See this question for more on this.)

However, you should be disposing the Bitmap - and that will close the stream for you. Basically once you give the Bitmap constructor a stream, it "owns" the stream and you shouldn't close it. As the docs for that constructor say:

You must keep the stream open for the lifetime of the Bitmap.

I can't find any docs promising to close the stream when you dispose the bitmap, but you should be able to verify that fairly easily.

Melli answered 3/12, 2008 at 7:12 Comment(4)
awesome! that's a great reply Jon. Makes perfect sence (and I missed the bit about the stream in the docs). Two Thumbs Up! I'll report back when i've given it a go :)Dunant
Any comments of how to go about this if we want to obey rule CA2000? (msdn.microsoft.com/en-us/library/ms182289.aspx)Boyce
@Patrick: It's simply not applicable - you've transferred ownership of the resource, basically. The closest you could come would be to create a "NonClosingStream" wrapper which ignores the Dispose call. I think I may have one in MiscUtil - not sure...Melli
Thanks for info @Jon. For me, for some strange reason it was working even with the dispose() in local dev environment but didnt work in production.Chindwin
F
108

A generic error occurred in GDI+. May also result from incorrect save path! Took me half a day to notice that. So make sure that you have double checked the path to save the image as well.

Faydra answered 3/4, 2012 at 21:14 Comment(2)
I'm glad I saw this, my path was C\Users\mason\Desktop\pic.png. Missing colon! I would have spent forever before I noticed that.Hyperdulia
Incorrect also means that a folder you want to save the image to does not exist.Bessiebessy
S
14

Perhaps it is worth mentioning that if the C:\Temp directory does not exist, it will also throw this exception even if your stream is still existent.

Steddman answered 25/10, 2011 at 22:6 Comment(1)
+1 This exception seems to occur in a variety of scenarios. Invalid path is one I've encountered today.Noguchi
D
4

Copy the Bitmap. You have to keep the stream open for the lifetime of the bitmap.

When drawing an image: System.Runtime.InteropServices.ExternalException: A generic error occurred in GDI

    public static Image ToImage(this byte[] bytes)
    {
        using (var stream = new MemoryStream(bytes))
        using (var image = Image.FromStream(stream, false, true))
        {
            return new Bitmap(image);
        }
    }

    [Test]
    public void ShouldCreateImageThatCanBeSavedWithoutOpenStream()
    {
        var imageBytes = File.ReadAllBytes("bitmap.bmp");

        var image = imageBytes.ToImage();

        image.Save("output.bmp");
    }
Dripdry answered 31/3, 2010 at 18:55 Comment(2)
This doesn't work exactly; in your code in ToImage(), local "image" will correctly have a .RawFormat of whatever the original file was (jpeg or png, etc), whereas the return value of ToImage() will unexpectedly have .RawFormat MemoryBmp.Boyce
Not sure how the RawFormat matters much, though. If you want to use that, retrieve it from the object somewhere along the way, but in general, save as whatever type you actually want to have.Christychristye
S
4

I had the same problem but actually the cause was that the application didn't have permission to save files on C. When I changed to "D:\.." the picture has been saved.

Swarey answered 11/3, 2014 at 21:24 Comment(0)
S
3

You can try to create another copy of bitmap:

using (var memoryStream = new MemoryStream())
{
    // write to memory stream here

    memoryStream.Position = 0;
    using (var bitmap = new Bitmap(memoryStream))
    {
        var bitmap2 = new Bitmap(bitmap);
        return bitmap2;
    }
}
Steel answered 19/11, 2013 at 10:59 Comment(0)
A
2

This error occurred to me when I was trying from Citrix. The image folder was set to C:\ in the server, for which I do not have privilege. Once the image folder was moved to a shared drive, the error was gone.

Agna answered 15/1, 2015 at 19:40 Comment(0)
E
1

A generic error occurred in GDI+. It can occur because of image storing paths issues,I got this error because my storing path is too long, I fixed this by first storing the image in a shortest path and move it to the correct location with long path handling techniques.

Engleman answered 7/2, 2014 at 8:7 Comment(0)
K
1

I was getting this error, because the automated test I was executing, was trying to store snapshots into a folder that didn't exist. After I created the folder, the error resolved

Keyte answered 7/2, 2017 at 15:16 Comment(0)
T
0

One strange solution which made my code to work. Open the image in paint and save it as a new file with same format(.jpg). Now try with this new file and it works. It clearly explains you that the file might be corrupted in someway. This can help only if your code has every other bugs fixed

Tranquilizer answered 19/2, 2014 at 10:33 Comment(0)
M
0

It has also appeared with me when I was trying to save an image into path

C:\Program Files (x86)\some_directory

and the .exe wasn't executed to run as administrator, I hope this may help someone who has same issue too.

Medicate answered 27/3, 2017 at 15:31 Comment(0)
C
0

For me the code below crashed with A generic error occurred in GDI+on the line which Saves to a MemoryStream. The code was running on a web server and I resolved it by stopping and starting the Application Pool that was running the site.

Must have been some internal error in GDI+

    private static string GetThumbnailImageAsBase64String(string path)
    {
        if (path == null || !File.Exists(path))
        {
            var log = ContainerResolver.Container.GetInstance<ILog>();
            log.Info($"No file was found at path: {path}");
            return null;
        }

        var width = LibraryItemFileSettings.Instance.ThumbnailImageWidth;

        using (var image = Image.FromFile(path))
        {
            using (var thumbnail = image.GetThumbnailImage(width, width * image.Height / image.Width, null, IntPtr.Zero))
            {
                using (var memoryStream = new MemoryStream())
                {
                    thumbnail.Save(memoryStream, ImageFormat.Png); // <= crash here 
                    var bytes = new byte[memoryStream.Length];
                    memoryStream.Position = 0;
                    memoryStream.Read(bytes, 0, bytes.Length);
                    return Convert.ToBase64String(bytes, 0, bytes.Length);
                }
            }
        }
    }
Charmainecharmane answered 22/12, 2017 at 12:27 Comment(0)
C
0

I came across this error when I was trying a simple image editing in a WPF app.

Setting an Image element's Source to the bitmap prevents file saving. Even setting Source=null doesn't seem to release the file.

Now I just never use the image as the Source of Image element, so I can overwrite after editing!

EDIT

After hearing about the CacheOption property(Thanks to @Nyerguds) I found the solution: So instead of using the Bitmap constructor I must set the Uri after setting CacheOption BitmapCacheOption.OnLoad.(Image1 below is the Wpf Image element)

Instead of

Image1.Source = new BitmapImage(new Uri(filepath));

Use:

var image = new BitmapImage();
image.BeginInit();
image.CreateOptions = BitmapCreateOptions.IgnoreImageCache;
image.CacheOption = BitmapCacheOption.OnLoad;
image.UriSource = new Uri(filepath);
image.EndInit();
Image1.Source = image;

See this: WPF Image Caching

Cannonry answered 16/3, 2018 at 8:25 Comment(2)
WPF images have a specific parameter BitmapCacheOption.OnLoad to disconnect them from the loading source.Christychristye
Thank you @Nyerguds, until your comment I failed to ask right questionsCannonry
T
0

Try this code:

static void Main(string[] args)
{
    byte[] data = null;
    string fullPath = @"c:\testimage.jpg";

    using (MemoryStream ms = new MemoryStream())
    using (Bitmap tmp = (Bitmap)Bitmap.FromFile(fullPath))
    using (Bitmap bm = new Bitmap(tmp))
    {
        bm.SetResolution(96, 96);
        using (EncoderParameters eps = new EncoderParameters(1))
        {   
            eps.Param[0] = new EncoderParameter(System.Drawing.Imaging.Encoder.Quality, 100L);
            bm.Save(ms, GetEncoderInfo("image/jpeg"), eps);
        }

        data = ms.ToArray();
    }

    File.WriteAllBytes(fullPath, data);
}

private static ImageCodecInfo GetEncoderInfo(string mimeType)
{
        ImageCodecInfo[] encoders = ImageCodecInfo.GetImageEncoders();

        for (int j = 0; j < encoders.Length; ++j)
        {
            if (String.Equals(encoders[j].MimeType, mimeType, StringComparison.InvariantCultureIgnoreCase))
                return encoders[j];
        }
    return null;
}
Tica answered 30/7, 2018 at 16:24 Comment(0)
C
0

I used imageprocessor to resize images and one day I got "A generic error occurred in GDI+" exception.

After looked up a while I tried to recycle the application pool and bingo it works. So I note it here, hope it help ;)

Cheers

Chelseachelsey answered 12/2, 2020 at 8:10 Comment(0)
H
0

I was getting this error today on a server when the same code worked fine locally and on our DEV server but not on PRODUCTION. Rebooting the server resolved it.

Hinman answered 25/9, 2020 at 5:39 Comment(1)
Microsoft strongly discourages using the whole System.Drawing namespace on servers, because it's extremely easy to overflow the amount of GDI+ objects when multiple users connect at the same time.Christychristye
O
0
public static byte[] SetImageToByte(Image img)
    {
        ImageConverter converter = new ImageConverter();
        return (byte[])converter.ConvertTo(img, typeof(byte[]));
    }
public static Bitmap SetByteToImage(byte[] blob)
    {
        MemoryStream mStream = new MemoryStream();
        byte[] pData = blob;
        mStream.Write(pData, 0, Convert.ToInt32(pData.Length));
        Bitmap bm = new Bitmap(mStream, false);
        mStream.Dispose();
        return bm;
    }
Obe answered 22/3, 2021 at 4:17 Comment(1)
Welcome to StackOverflow! Please consider adding some explaination text to go with the code. A good place to start: why do it this way and not another?Loritalorn

© 2022 - 2024 — McMap. All rights reserved.