Labview crash related to Virtual Bench 8012

[RPBCN]

My application consists of a Labview User Interface that calls a Teststand sequence.
The UI is very similar to what gets installed by default with TestStand.
In the TS sequence there are calls to VIs. Some of them are to the Virtual Bench 8012 driver.
It works well.
But when I exit the Operator Interface Labview crashes. I did debug a little bit and the crash
occurs when trying to close the Teststand Engine.
If in the Teststand sequence I skip the calls to the VB8012 driver then the Labview crash does not happen.
I am using LV2013 but TestStand2010.

[ZachHindes]

Hello RPBCN,

I loaded up the crash dumps, but it didn't give me much useful information.  Can you tell me a little bit about how you're calling into the VB8012 driver from Test Stand?  Are you using LabVIEW 32-bit or 64-bit?  Any particular operations you're doing?  What about the Test Stand call configuration?  I am going to attempt to reproduce this here the best I can.

Thanks!

[RPBCN]

Hello Zach,

Thank you for your reply.

I am using Labview 32 bits in a Windows XP machine.

The TestStand calls are made through Labview VIs. I have developed these VIs from the examples that come with the VirtualBench installer. They are in fact very similar.

To verify the problem was related to VirtualBench I left the test sequence with a single call that sets the Power Supply in the Process Setup part of the sequence. If this call is made I get the error I mention at the end, if I skip this call no error.

Regards,

Raimon Pousa

[ZachHindes]

I'm not having any success reproducing the issue.  Here is my adapter configuration:

Here is my step settings when I call my VI:

Here is my (very simple) VI:

[ZachHindes]

Nevermind, I am able to reproduce this, I didn't read your description closely enough.  When I close TestStand after executing a sequence that uses VirtualBench it does crash.  If I configure the LabVIEW Adapter to use the Development System it does not do this.  I am looking into it now.

[RPBCN]

Hello Zach,

Similar to you, I don't get the error if I have the Adapter in Development mode and I execute the sequence from TestStand.

But I have a Labview user interface that calls the TestStand sequence. This User Interface I have it as an executable and as a Labview VI. When I run it as a VI I set the Adapter to Development. and the error also happens.

Regards,

Raimon Pousa

[ZachHindes]

I have filed CAR 480093 on the issue here at NI.  We are looking into it.  I apologize for the inconvenience.