Objects get GC'ed "at some point after there's no longer any references to them", which could mean aeons after they "go out of scope"... but it can even happen within the method where the variable referencing the object was initially allocated.

Quote

Objects get GC'ed "at some point after there's no longer any references to them", which could mean aeons after they "go out of scope"... but it can even happen within the method where the variable referencing the object was initially allocated.

True.  Remember, too, though, that there is such as thing as memory pressure, which refers to the fact that the more objects there are in memory, the more often garbage collection occurs.  Not sure how much more often.

My current pains actually involve BitmapFrame classes, so unless that isn't used by WinForms either, you might be up for some pain yet. It is a tried and true disaster, yessir. For now, I'd be happy enough to be rid of the crashes.

Edit:

Does the Bitmap.FromFile() call (or whatever) happen to use the System.Windows.Media.Imaging namespace? I think that one is WPF specific, but if it does there might be a solution in there. (I've been hating that one more than plenty so far.)