I have a declaration in a control (using c#)

private PdfImageCollection oPDFImgColl;

Later in my code when the user does a "manual scan" , I instantiate the object with

oPDFImgColl = new PdfImageCollection();

When I do so , the application hangs and some time later I get this error message ...

The instruction "0x7c910cb0" referenced memory at "0x000401b4". The memory could not be "read".

Click on OK to terminate the program
Click on CANCEL to debug the program

Which is your standard issue corrupt memory message. Now I have written another application

using the atalasoft acquisition control and the EXACT same code (barring it was in vb) and it worked

and has worked for some months now with no issue. Yet this error occurs every single time and only

when I instantiate the PDFImageCollection it seems. Could anyone explain or elaborate on how or why this may be different from my previous app ? I fail to see how from one app to the next the same code could behave differently ...

Memory corruption issues are sneaky.  They can appear or disappear depending on the current memory layout.  Chances are, your actual issue happened much earlier in program flow and only manifests when you construct this particular object at that particular time in your program execution.  I'm 100% sure that the problem is not in the PdfImageCollection constructor.

Can you give us an idea of what is happening in your application and what it uses to see if we can determine if their is an issue we need to address?