-
Notifications
You must be signed in to change notification settings - Fork 4.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Non-deterministic 'AccessViolationException' under specific conditions when using 'System.Data.OleDb' in an x64 process #46187
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to this area: @roji, @ajcvickers Issue Details@roji As discussed yesterday in our call with @ajcvickers and the others, here the information about the The It contains the specific conditions under which the issue appears and also contains the original reproduction code. I updated the code (simplified it further) and also added projects for ODBC using ADO.NET and for directly using OLE DB via C++. Both of those added projects work as expected, so this issue is either a The original post from CirrusRedOrg/EntityFrameworkCore.Jet#43 (comment):
|
Thanks @lauxjpn. We'll get back to this when people come back for the new year. |
I'll get the same exception, when I perform the same steps I do in the (working) C++ project, but in .NET. So when I manually manage all the COM interfaces of OLE DB in C#, I'll get an I'll update the reproduction project with the new project. |
Moving this to Future for now to follow up with the Access team, as per offline discussion with @lauxjpn. |
We are still getting lots of crashes in different Access Runtime versions and processor architectures. (Recent discussion in CirrusRedOrg/EntityFrameworkCore.Jet#152.) |
@roji As discussed yesterday in our call with @ajcvickers and the others, here the information about the
AccessViolationException
issue I was talking about.The
AccessViolationException
issue has been previously discussed in detail in CirrusRedOrg/EntityFrameworkCore.Jet#43 (comment) (and I also referenced it before in #33899 (comment)).It contains the specific conditions under which the issue appears and also contains the original reproduction code.
I updated the code (simplified it further) and also added projects for ODBC using ADO.NET and for directly using OLE DB via C++.
Both of those added projects work as expected, so this issue is either a
System.Data.OleDb
issue after all, or it is an OLE DB layer issue, but depends on specific operations that are being performed by ADO.NET, but not by myWorking_Jet_OleDb_x64_Native
C++ project.The original post from CirrusRedOrg/EntityFrameworkCore.Jet#43 (comment):
The text was updated successfully, but these errors were encountered: