Hi all,
I've seen many discussion threads related to the "Resetting VI" dialog, and I've read at least one KB on it.
Some context:
I've been asked to help debug an application that someone else wrote.
- Standard LabVIEW, no LVOOP or Actor Framework
- We're running LabVIEW 2012, calling a rather esoteric and complex module of LabVIEW code from TestStand
- We sporadically get a MS Visual C++ Runtime Error dialog that says LabVIEW.exe has requested the Runtime to terminate it in an unusual way
I've seen the "Resetting VI" dialog in the past, but in this case it reads:
"Resetting VI: foo.vi.ACBRProxyCaller.[Hex]" (It's not really foo.vi - but for simplicity's sake)
I'm trying to figure out where to focus my efforts in isolating the problem.
First question:
Does this mean that LabVEW is waiting for foo.vi (the caller) to reset, or does the message mean that LabVIEW is waiting for the VI called by the ACBR node?
Second question:
Is the "Resetting VI" dialog usually indicative of the exact problem area, or could something else in the code be causing the crash, and LabVIEW just happens to be executing foo.vi because it takes the most time to execute?
I realize I'm asking generic questions and not giving a lot of information. Part of the reason for that is that this is a large and complex application that is challenging for me to decipher as a newcomer, and another reason is the proprietary nature of the application.
Any advice or direction?
Cheers,
Jim