This isn't so much a technical question, as a question of good 

practices.



One of our developers ran into a first chance exception while calling 

CoUninitialize(). The exception was a 0xC0000005 in MSADCE.DLL.



Now, I went to MS's web site and the only thing I found on this was a 

piece of sample source code that said: "Note, under some circumstance 

when CoUninitialize is called, you may see a first-chance exxception in 

MSADCE.DLL: which is 0xC0000005: Access Violation. This is only a 

first-chance exception and can be safely ignored."



No, I don't know about you, but if I see a first-chance exception in my 

own code, I tend to assume it's a bug and I fix it. If it's not a bug, 

but something I want to allow (for some ungodly reason), I would 

certainly document it.



How reliable is a piece of source code that you get off of Microsoft's 

site for something like this. Can we really "safely ignore" this?



Thanks.



Pete