Is this issue resolved in the new version? It was not mentioned in the release notes, or perhaps I missed.

Thanks for your explanation. Is there some kind of roadmap when QuickOPC 2018.2 will be released?
I saw a new Nuget Package was released today, where can we find the release Notes for the new package?

kb.opclabs.com/What%27s_New

There are only notes for the big releases.

Best Regards

Hello,

it seemed to help with the crash. Our application is running longer than 25sec in Debug mode. Could you please give some more detailed information on this application configuration?

Best regards

Hello,

There are some reasons for not enabling “native code debugging”.
1.)
Somewhere in OPC-UA code, an exception is thrown. It should be clarified, what is the reason for that.
2.)
“Native code debugging” slows down the debugging experience in two ways: the debugger itself runs slower and more (potentially unimportant) exceptions will show up, which slows down the developer.
3.)
This doesn’t seem to solve the problem in our main application, it just seems to work in your example code. Through enabling “native code debugging”, the program does not abort abnormally. But the exception itself would still occur. Using this option, we still have other strange behavior in our application. So it may be possible, that the strange exception leads to other problems when using the x64-debugger. But this is something, we still have to examine. I will try to find out, if the strange behavior still exists, if we don’t load the OPC-UA libraries. (So we find out, if this behavior depends on the exception in OPC-UA lib or not).

Best regards

Hello,

we also do have some similiar problem, which seems to have the same root cause. But we were able to collect some more information and a way to reproduce the error behaviour with OPC-UA example-code.
This may become a long post. I will try to collect and present all information we were able to gather until now.

Our system environment is Win 7, VisualStudio 2015 Professional.

1.) What we see in our application
We also have a crash in our application after approx. 25 seconds with the following error message in an error window:I was able to find out, that this exception seems to occur inGetting a helpful call stack is not possible. The call stack is just one line in depth and seems to be in ntdll

2.) What we found out until now
The crash seems to occur only when our program is started through the debugger and running in 64bit mode. As we added some libraries, that only support 64bit, our application starts automatically in 64bit mode. When we start the application without a debugger attached (e.g. through clicking on the exe in windows explorer), the application runs without any problems. We then could attach the debugger to the application without any problems.
So it seems, that the crash is associated to debugging a 64bit application.

3.) How to reproduce
You can reproduce a similiar behaviour on your site with the OPC-UA examples:
- Open solution "QuickOpcCSharpExamples"
- Set "ConsoleLiveMapping" as startup project (we simply chose the first project for tests)
- open project properties of "ConsoleLiveMapping", open "Build" tab and set "Platform target:" to "x64" for the current build configuration (Debug/AnyCPU)
- Debug the project (F5), wait until program ends (you may lower the waiting time to 1 sec), Press Enter after program finished. Now you should get an error window (see attached file "ErroWindow")

- Output window shows:- So at least the error message in output window is similiar and the way, how the program ends is similiar

I also was able to reproduce this test in a new virtual machine with Win7 and VisualStudio 2015 Professional.

I used the following debugger settings (Tools->Options->Debugging):

We also tried to do some tests with other settings. Here are our results:
- Activate "Enable native code debugging" in "Project->Properties->Debug" => no problem
- Set "Platform target" to "Any CPU" in "Project->Properties->Build", Disable "native code debugging" => application shows the "crash"
- Set Build settings to "Any CPU" and enable "Prefer 32-bit" => no problem

4.) Conclusion
We are assuming, that the described behaviour may come from some "incompatibilities" due to debugging 64bit applications. But we are not able to track down the problem, since we do not have (and also don't want to have ) access to the sources of the OPC-UA libraries.
I don't think, that there is some interaction with firewalls or antivirus software, since I was able to reproduce the problem on a "clean, new" virtual machine installation (although Windows firewall and other Windows protection software was not disabled)

Could you please try to reproduce the problem? And, if you succeded, could you please try to track down the root cause of the problem, since currently we are not able to debug our software in an appropriate way.

Thank you in advance.