If anything goes wrong in System.Graphics.Drawing, an OutOfMemoryException is what you get. Not very informative, to say the least, and most often outright misleading.

It strikes me as a fairly lazy implementation of that particular library. That, or a library developer accidentally wrote code that overrides most other exceptions, in which case it's a QA problem.