Note that there are some explanatory texts on larger screens.

plurals
  1. POVB.NET app giving memory exception 0xc0000005 in ntdll.dll
    primarykey
    data
    text
    <p>I am having some issues with a memory access exception in a VB.NET application that I am working on. I was hoping to get some insight here as none of the research I've done has helped me track down the problem.</p> <p><strong>Background:</strong></p> <p>I am converting a number of applications from VB6 to .NET 4.0. At the request of the client, I am doing a straight conversion and only refactoring when necessary to avoid injecting other issues into the code as I convert. Most apps are being compiled in Any CPU mode, though a few have to be compiled as x86 because of reliance on 32-bit PLC software or older hardware drivers. My development machine is Windows 7 64-bit.</p> <p><strong>Issue:</strong></p> <p>After successfully converting two apps, the third application is crashing at random places in the code. The exception isn't caught and I have to look at the Looking at the event log I am seeing Exception code: 0xc0000005 on ntdll.dll, which I believe is a memory access exception. Since the application doesn't always crash in the same place, it is making it tough to track down. I have noticed that a lot of the errors occur during calls to ADODB (not always in the same place or on the same call), but it has also crashed on calls to form.ShowDialog(). </p> <p>The form where ShowDialog is being called writes some log information to the DB using ADODB. Though I haven't been able to confirm, I am guessing the exception within the form.ShowDialog() is happening during one of these ADODB calls. The crashing on the ADODB calls is happening in assemblies that are successfully being used in the other two apps that were converted and it doesn't consistently crash in the same place.</p> <p>In my research on this I have seen that bad interop can cause this issue. Wondering if the ADODB COM calls are somehow causing the issue in this app even though these calls are fine in the other apps.</p> <p>Some of the places I've observed calls that are apparently throwing this exception to the event log:</p> <ul> <li>newing an ADODB.recordset</li> <li>Creating a new parameter within a command.append</li> <li>connection.open calls</li> </ul> <p>Would anyone have any ideas how I can narrow this down to possibly trace the issue to its root cause? I appreciate any help or insight you can provide.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload