Exception: Access violation (0xC0000005) at EIP = 0x0126ECB7

[Johnny3D]

Hi,

My application uses Call Library Nodes to link to DLL written in C for my company's producuts. Whenever I close the LabVIEW application, either in VI or EXE, the following crash report would appear.

I have attached complete LabVIEW solution here.

Thanks in advance.

[mikeporter]

Often this sort of crash on exit results from bad memory allocation for strings or arrays. I can't look at your code as I am on my phone, but look for calls that are outputting as array or string and make sure the left side of the node has an array of sufficient size to hold the expected output.

Also what version of LabVIEW are you using? The error message says 2015, but your archive says 2013.

Mike...

[Johnny3D]

I have both 2015 and 2013 versions and both experienced the same crash.

[B_Strange]

I wish you the best of luck with this one. I followed many rabbit trails searching for my "Access violation (0xC0000005)" error. If you have an active SSP, I'd recommend opening a ticket. The applications engineers at NI are quick to respond and very helpful. For what it's worth, the conclusion of my investigation--probably since I was unable to reprouce the problem on demand--was to upgrade to the latest LabVIEW version (my application was built using 2011). For what it's worth, they said my issue pointed to a bug that was patched in a subsequent version.

[Bob_Schor]

Have you sent this to NI, as suggested by the Crash Reporter?  These things are notoriously difficult to debug -- I had a bunch of them with LabVIEW 2011, but NI found/fixed the bug in LabVIEW 2012.  Have you tried running NI Update to see if there's an update to the Version of LabVIEW (2015?) you are currently running?

Plus a suggestion -- put your Project into LabVIEW Project.  I wouldn't write a routine with more than one VI without LabVIEW Project ...

Bob Schor