From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
06-25-2018 04:13 PM
I am building a fairly complex program to acquire measurements from several different instruments at once via serial connections. Recently, LabVIEW has been crashing nearly every time I run my VI, sometimes immediately and other times after a few minutes. Specifically, when I start the program and interact with the front panel (e.g. clicking on different controls), LabVIEW hangs and I have to forcibly close the program through Windows. Now the strange thing is, LabVIEW crashes in the development environment, but doesn't when I build the executable.
LabVIEW does not report an error before closing so there is no error log, but there is a minidump file in the LVInternalReports folder which is indicating some sort of access violation error (Exception code 0xC0000005). In addition to the minidump file, I've attached a Windows Error Report file. I've been wrestling with this all day and can't seem to figure it out. Any insight would be appreciated.
Solved! Go to Solution.
06-26-2018 10:26 AM
I think the cause has something to do with references or property nodes. I've replicated the error in a simple VI that I've attached.
06-26-2018 10:54 AM
Hi,
Can you give me more information on your setup? What instruments are you using? This crash can happen for various reasons.
06-26-2018 11:02 AM
06-26-2018 12:09 PM
It seems like it has something to do with the typedefs. I had no problem running the program when I disconnected the typedefs as well. I've uploaded the typdefs in this zip file. I was also able to reproduce the error in LabVIEW 2018 32-bit as well as 64-bit.
This program is essentially a small snippet of a much larger program where the cluster needs to be read from elsewhere in the block diagram, which is why I used a property node there. The error still persists when I wire the control directly.
06-26-2018 03:32 PM
After some more digging, I think I've figured out the simplest case for this error. If I have a disabled cluster control with a string element with a vertical scroll bar then my program will randomly hang and crash- see attached.
Unless this is something strange with my computer, I think this is a bug on NI's (or Microsoft's) side.
06-26-2018 04:50 PM - edited 06-26-2018 05:23 PM
Yes, I got it to crash at iteration 109 using LabVIEW 2018 (automatic crash report submitted). Looks like an obscure bug.
(I made an entry in the monthly bug thread)
06-26-2018 05:28 PM
Altenbach,
Do you happen to have the report ID for the crash report? if not, would it be too much trouble to send one more report in and let us know that ID?
Thanks!
06-26-2018 06:07 PM
(Sorry, posting by phone)
I did two reports a few minutes apart. They have my email and in the second I added a comment pointing to this thread.
I can get the ID later.
06-27-2018 12:10 AM