NI Home > Community > NI Discussion Forums

LabVIEW

Showing results for 
Search instead for 
Do you mean 
Reply
Trusted Enthusiast
P@Anand
Posts: 2,414
0 Kudos

Re: LabVIEW Access Violation Crashes


amezam wrote:

Hello P Anand,

 

Please see the post I did earlier to Stoove. Please let us know if it solved by cleaning the PC.

 

Best Regards,


Sorry for the Delay.

 

Clearing the PC didn't work well and still we were getting the same error.

 

We replaces the ActiveX server registery and also replaced the main python core files that we were accessing and till now we haven't got any Access violation error.

-----

The best solution is the one you find it by yourself
Member
Stoove
Posts: 9
0 Kudos

Re: LabVIEW Access Violation Crashes

Last week we finally found a solution to our version of this problem!

 

In our particular case, we found that the crashes were due to our use of the "Build Array" vi. It appears that some aspect of the manner and frequency with which we were calling it caused it to erroniously write to the memory. Although the NI engineer I spoke to didn't go into detail, it appears that it was not as stable in our case as alternate methods.

 

Our solution was to modify the method with which we built an array. Instead of building the array from rows of data at the time they are acquired, we now initialise the array to the final size and use the "Insert Into Array" vi to place data at the correct index. This is much less convenient but significantly more stable for us. Since the change, the number of Access Violations has been negligible in comparison to the frequency of use of the code.

 

I'd recommend taking a look at any fixes similar to this if nothing else is working.

 

Thanks to everyone who suggested fixes!

Trusted Enthusiast
P@Anand
Posts: 2,414
0 Kudos

Re: LabVIEW Access Violation Crashes

One more scenario for the Access violation problem (Original thread)

-----

The best solution is the one you find it by yourself
Trusted Enthusiast
Intaris
Posts: 3,270
0 Kudos

Re: LabVIEW Access Violation Crashes


Stoove wrote:

Last week we finally found a solution to our version of this problem!

 

In our particular case, we found that the crashes were due to our use of the "Build Array" vi. It appears that some aspect of the manner and frequency with which we were calling it caused it to erroniously write to the memory. Although the NI engineer I spoke to didn't go into detail, it appears that it was not as stable in our case as alternate methods.


 

Wow, that sounds like a potentially terrifying bug.... Build array not being watertight? Say it isn't so....

 

Shane.

Member
LV1981
Posts: 1
0 Kudos

Re: LabVIEW Access Violation Crashes

The same thing happened to me but it only worked for a few months and then I started seeing it in 2012 also.

Member
Tikka_CZ
Posts: 7
0 Kudos

Re: LabVIEW Access Violation Crashes

Hello, 

 

I am also experiencing this problem. But in a very specific situation. My LV programs work just fine. But I need to build applications. When I run these applications, they also work fine, but when I quit them (using red cross or menu File - exit) I get crash report - Access Violation. I tried this with LV 2012 SP1, LV 2013, on different computers, with antivirus turned off and I get still the same result.  EIP address remains the same, different for different computers. In my programs I use dll libraries for communication with external application - communication server.

 

Do you have any idea what can be causing this? Thanks for your advice.

Member
Prickly_Pear
Posts: 129
0 Kudos

Re: LabVIEW Access Violation Crashes

I looked up our previous service requests and one LabVIEW developer was able to solve this by creating the exe on another version of the Application Builder. If you have access to another version of LabVIEW Application Builder then it might be worth it to give it a try.

 

I'm not sure what could cause this. Perhaps it is some kind of corruption?

 

Jeremy P.

Applications Engineer
National Instruments
Member
allenjoe
Posts: 1
0 Kudos

Re: LabVIEW Access Violation Crashes

I get the following error : Exception: Access violation (0xC0000005) at EIP=0x776ED583. Help me out 

 

Member
John_Morrissey
Posts: 73
0 Kudos

Re: LabVIEW Access Violation Crashes

The fix for our issue was incorporated into LabVIEW 2012 SP1.  We have rarely if ever seen the problem since.

Member
Tikka_CZ
Posts: 7
0 Kudos

Re: LabVIEW Access Violation Crashes

In my case, there was a problem with call library function node. I set external library file location inside function properties and it caused this error. After changing it to setting by external string constant it worked. Don´t ask me why.... :-)