Windows Forms application has been throwing OutOfMemoryException although there is enough virtual memory in the process. When you have OutOfMemoryException usually callstack is not helpful unless of course you have blocked finalizer thread or some deadlock preventing objects from being gced but in this scenario whenever OutOfMemoryException is thrown it will always point to the same call stack.
at System.Drawing.Image.FromFile(String filename, Boolean useEmbeddedColorManagement)
at System.Drawing.Image.FromFile(String filename)
Let’s look at System.Drawing.Image implementation using Reflector. Just read the documentation below
Creates an Image from the specified file using embedded color management information in that file.
|OutOfMemoryException||The file does not have a valid image format.-or- GDI+ does not support the pixel format of the file.|
|FileNotFoundException||The specified file does not exist.|
My first reaction to this is why? Why would you throw OutOfMemoryException if the file is corrupted or GDIPlus doesn’t support the pixel format.
I really don’t know why does System.Drawing library choose to throw OutOfMemoryException exception? This is only going to add to your worries.