LabView crashes while VI is loading: linalg, Solve Lin Equation

[LabDevUW]

Hi,

I am having problems with a VI using LabView 2011. While I was modifying the block-diagram, Labview suddenly crashed giving: Exception: Access violation (0xC0000005) at EIP=0x00CBFBDA. When I try to reopen

the VI, Labview crashes again at loading. 

It seems the crash occurs always when the library linalg: solve lin equations is loading. Other VIs seem to work fine. 

Is this a known problem?

Best regards

[Ben-N]

Hi LabDevUW,

I went to take a look at your VI, and I got the exact same crash with the same error.  I looked a little more into what might be causing this, and so far I've gotten determined that the errors are "unknown errors" at "unknown locations".  It sounds to me like you have a bug.

I'm going to be taking this VI to our R&D department and see what we can do to help get this sorted out for you.  Our R&D department may be able to recover this VI for you, but that will really depend on what the errors are and where they are occurring in the code.  Even if we are able to restore the VI, there may be some broken configurations, i.e. you may need to reformat your front panel as things might be shuffled around.

Give me a little time to look into this and to get our R&D department on this and I will get back to you with some updates.  Thanks for being patient!

[Ben-N]

Hi LabDevUW,

Thanks for your patience with me.  I was able to get in touch with our LabVIEW Experts and this VI has been passed to our R&D Department.  Addtionally, a Corrective Action Report has been generated for this specific issue.  For your reference, this is CAR #346884.

As I mentioned previously, our R&D department may be able to recover this VI, but this is not a guaranteed thing.  Additionally, even if we they are able to recover the VI, it may take a fair amount of time.  Do you have a backup of this VI from a previous version?  One thing to look into in the future if you do not have a backup is source control, but this obviously doesn't help you in this instance.

[JleeUSN]

Were you guys able to resolve this issue?

I am experiencing the same error.

Thank you for your time.

[Ben-N]

Hi JleeUSN,

Our R&D department is still working on this issue.  If you can post the VI that is giving you this error, I will be glad to include this VI in the CAR filed to our R&D department.  As I mentioned, I'm not sure if we will be able to recover the program, but I'm more than willing to get the program into the appropriate hands.  If you can post that VI, please do so at your convenience.

[JleeUSN]

I was able to trace my problem down to a sub VI.

I changed the call setup so that all of the sub VIs were not loaded with the main VI and that allowed the main to load and execute.

If we are able to solve it I will post our findings.

[Jeff-P]

CAR 3468842 discussed in this thread has been fixed in LabVIEW 2013. For a more complete list of bugs fixed in LabVIEW 2013, check the LabVIEW 2013 Bug Fixes. You can download an evaluation copy of LabVIEW 2013 at http://www.ni.com/trylabview/ or if you have an earlier version of LabVIEW installed and an active SSP subscription, you will be able to download the latest version of LabVIEW through NI Update Service.

Jeff Peacock

Product Support Engineer | LabVIEW R&D | National Instruments