Professional OPC
Development Tools

logos

Online Forums

Technical support is provided through Support Forums below. Anybody can view them; you need to Register/Login to our site (see links in upper right corner) in order to Post questions. You do not have to be a licensed user of our product.

Please read Rules for forum posts before reporting your issue or asking a question. OPC Labs team is actively monitoring the forums, and replies as soon as possible. Various technical information can also be found in our Knowledge Base. For your convenience, we have also assembled a Frequently Asked Questions page.

Do not use the Contact page for technical issues.

Crash with memory corruption

More
09 Sep 2021 09:28 #10193 by Gulyk
Replied by Gulyk on topic Crash with memory corruption
I've tried my test project with the newest binaries from 2021.2 and it stopped crashing.

Please Log in or Create an account to join the conversation.

More
08 Sep 2021 13:47 #10191 by support
Hello,
thank you for the reporting the issue.

Several times, when we have seen "weird" crashes, they were related to a 3rd party library that we use. Please follow the instructions given on kb.opclabs.com/How_to_disable_prerequisites_boxing to see if the problem goes away.

If it does not go away, please check if it happens with the current QuickOPC version. (Sorry, we do not fix older versions).

If the problem is reproducible with the recent QuickOPC version, we will investigate it.

Best regards

Please Log in or Create an account to join the conversation.

More
08 Sep 2021 13:42 #10190 by Gulyk
Replied by Gulyk on topic Crash with memory corruption
Please remove .zip extension from attachments before unpacking.

File Attachment:

File Name: OPCCrash.zip.001.zip
File Size:40,960 KB

File Attachment:

File Name: OPCCrash.zip.002.zip
File Size:27,557 KB
Attachments:

Please Log in or Create an account to join the conversation.

More
08 Sep 2021 13:24 #10189 by Gulyk
Hi Support,

We have encountered a very interesting crash in our software using QuickOPC 2018.2
I have reproduced it in a very simple project which is in the attachments.
I kept compiled binaries, so that you do not have to recompile them.

The idea behind the crash
1. Native x86 application creates OPC UA client via mixed mode assembly.
2. Native application loads some COM component.
3. Native application tries to load some native x86 dll (a completely empty one in our case)

We get in debugger

Windows has triggered a breakpoint in Runner.exe.

This may be due to a corruption of the heap, which indicates a bug in Runner.exe or any of the DLLs it has loaded.


In the output log

'Runner.exe': Loaded 'E:\Development\DevTest\OPCCrash\Debug\TestDll.dll', Symbols loaded.
HEAP[Runner.exe]: Heap block at 0CEA71B0 modified at 0CEA7288 past requested size of d0
Windows has triggered a breakpoint in Runner.exe.


Solution was created in VS2012.
When converted to VS2019 it gave different error message, but crash was in place.

Please Log in or Create an account to join the conversation.

Moderators: support
Time to create page: 0.050 seconds