Is there a reason Image.FromFile throws an OutOfMemoryException for an invalid image format?

by

No, it is history. GDI+ was written quite a while before .NET ever came around. The SDK wrapper for it was written in C++. Exceptions are iffy in C++, not everybody buys into them. Google doesn’t for example. So to keep it compatible it reports problems with error codes. That just never scales well, library programmers make it a goal to intentionally limit the number of possible error codes, it lessen the burden on the client programmer having to report them.

GDI+ has this problem in spades, it defines only 20 error codes. That is not much for such a large chunk of code with so many external dependencies. Which in itself is a problem, there are a gazillion ways to mess up an image file. No way that a library’s error reporting can be fine-grained enough to cover them all. The fact that these error codes were picked long before .NET defined standard Exception derived types certainly didn’t help.

The Status::OutOfMemory error code got overloaded to mean different things. Sometimes it really does mean out of memory, it can’t allocate enough space to store the bitmap bits. Sadly, an image file format problem is reported by the same error code. The friction here is that it cannot possibly decide if the width * height * pixels it read from the image file is a problem because there isn’t enough storage available for the bitmap. Or if the data in the image file is junk. It assumes that image file is not junk, fair call, that’s another program’s problem. So OOM is what it reports.

For completeness, these are the error codes:

enum Status
{
    Ok = 0,
    GenericError = 1,
    InvalidParameter = 2,
    OutOfMemory = 3,
    ObjectBusy = 4,
    InsufficientBuffer = 5,
    NotImplemented = 6,
    Win32Error = 7,
    WrongState = 8,
    Aborted = 9,
    FileNotFound = 10,
    ValueOverflow = 11,
    AccessDenied = 12,
    UnknownImageFormat = 13,
    FontFamilyNotFound = 14,
    FontStyleNotFound = 15,
    NotTrueTypeFont = 16,
    UnsupportedGdiplusVersion = 17,
    GdiplusNotInitialized = 18,
    PropertyNotFound = 19,
    PropertyNotSupported = 20,
#if (GDIPVER >= 0x0110)
    ProfileNotFound = 21,
#endif //(GDIPVER >= 0x0110)
};

More Related Contents:

  1. Is there a difference between “throw” and “throw ex”?
  2. WPF global exception handler [duplicate]
  3. Globally catch exceptions in a WPF application?
  4. .NET – What’s the best way to implement a “catch all exceptions handler”
  5. What happens if a finally block throws an exception?
  6. Is this a bad practice to catch a non-specific exception such as System.Exception? Why?
  7. What is ApplicationException for in .NET?
  8. Show line number in exception handling
  9. Could not load file or assembly … An attempt was made to load a program with an incorrect format (System.BadImageFormatException)
  10. C++ display stack trace on exception
  11. Exception messages in English?
  12. Puzzling Enumerable.Cast InvalidCastException
  13. Can you catch a native exception in C# code?
  14. Silent failures in C#, seemingly unhandled exceptions that does not crash the program
  15. How to use ELMAH to manually log errors
  16. Does the use of the “Async” suffix in a method name depend on whether the ‘async’ modifier is used?
  17. How can I catch a 404?
  18. Unhandled exceptions in BackgroundWorker
  19. User Activity Logging, Telemetry (and Variables in Global Exception Handlers)
  20. InvalidProgramException / Common Language Runtime detected an invalid program
  21. Why is TargetInvocationException treated as uncaught by the IDE?
  22. How to implement one “catch’em all” exception handler with resume?
  23. The parameterized query ….. expects the parameter ‘@units’, which was not supplied
  24. How do I determine the HResult for a System.IO.IOException?
  25. Reflection MethodInfo.Invoke() catch exceptions from inside the method
  26. C# Only part of a ReadProcessMemory or WriteProcessMemory request was completed during Process.Kill()
  27. How to handle WCF exceptions (consolidated list with code)
  28. Finding the cause of System.AccessViolationException
  29. Dynamically changing Textbox’s AutoComplete List causes AccessViolationException, any advice?
  30. What are the causes and solutions of exception code c0000005 in mscorwks.dll?

Leave a Comment