We are using some VB6 (please don't ask) code to make a call to a DLL (which is also our own code) that uses the Entity Framework in .NET 4.0.30319.1 - and SOMETIMES this results in System.Data.Entity.ni.dll coughing up a c0000005 (a buffer overrun).
I know that, usually, this is caused by a C++ string being incorrectly terminated (as in: not terminated with a NULL), but I am hesitant to believe that this would be a general bug in the System.Data.Entity code. It only happens at one customer, and it only happens once in a blue moon or so. And I'm not even sure of that - the application event log that I got didn't even go that far back, so I am seeing only proof of one actual instance. And yes, I have asked if the problem can be reproduced... :-|
My question is: could there be an error condition in a database record that could throw System.Data.Entity a curveball, resulting in a c0000005? Is there anything specific that I should be looking for?
Any help would be greatly appreciated!