Open lauxjpn opened 3 years ago
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 See info in area-owners.md if you want to be subscribed.
Author: | lauxjpn |
---|---|
Assignees: | - |
Labels: | `area-System.Data.OleDB`, `untriaged` |
Milestone: | - |
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 AccessViolationException
around iteration 50. No System.Data.OleDb
reference involved.
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. So this is still an issue and it would still be great to get in contact with whoever is currently maintaining Microsoft Access, so that those memory access violations get fixed.
(Recent discussion in https://github.com/bubibubi/EntityFrameworkCore.Jet/pull/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 https://github.com/bubibubi/EntityFrameworkCore.Jet/issues/43#issuecomment-602592245 (and I also referenced it before in https://github.com/dotnet/runtime/pull/33899#issuecomment-605464192).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 https://github.com/bubibubi/EntityFrameworkCore.Jet/issues/43#issuecomment-602592245: