LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Runnable code crashes LabVIEW on save or run

The crash report number is:

0a73619f-4e2c-4578-9ca0-d7bed416e1b0

0 Kudos
Message 11 of 14
(836 Views)

I took a look at the crash dump, it appears to be crashing during a recompile on save. 

 

How complex is your VI hierarchy? Do you have a lot of subVIs that were also upconverted from 2009?

 

A few things we can try to get the VI recompiled and hopefully in a good state again - 

 

CTRL + Run Arrow: This will force compile the VI you are running this on.

Clear the objcache: If your VIs are using Separate compiled code from source file then you can clear the VI objcache through Tools>>Advanced>>Clear Compiled Object Cache which will delete the compiled code and require a recompile.

CTRL + Shift + Run Arrow: This one is a bit more complicated. It will force a recompile of everything that is in memory and in the same context as the VI you are click the run arrow on. So if you are using OOP, this can recompile your entire class hierarchy. If you use this on your top level VI, it will recompile your hierarchy (although it will not touch any dynamic dependencies).

 

That being said, is it possible for you to send me the VI that is giving you problems (preferably saved in 2009)? It is a reproducible crash so I would like to file a CAR against it.

 

Thanks,

 

Jeff Peacock 

 

Product Support Engineer | LabVIEW R&D | National Instruments 

0 Kudos
Message 12 of 14
(809 Views)

Jeff-P and Wise_Owl.

 

I'll rack my brains a bit more but (anyone feel free to chime in)

 

Now that OOP was brought up... And the recompile thing is confirmed.

 

I'm fairly sure a deep dig through the CAR database (Fixed in 2009SP1 or 2010) might point to an unallowable class that the 2009 compiler did not catch at compile time.

 

Does the 2009 verion really run or is there a potential for a run-time crash in 2009?


"Should be" isn't "Is" -Jay
0 Kudos
Message 13 of 14
(805 Views)

I tried all the things, in order, that Jeff-P suggested with no change to the crash behaviour.

 

I saved the project as LabVIEW 2009 sucessfully, but LabVIEW 2011 gave me an internal report on quitting:

LabVIEW internal errors.PNG

I filed this as report ID: b627c9d6-6873-4d33-bde6-cdc5cf5a8084

 

This 2009 code runs and saves in LabVIEW 2009 without crashing and I attach it as ZIP file.  I am 99.5% sure that if you open it in LabVIEW 2010 or later it will exhibit the crashing as I have tried this on fresh installs of LabVIEW on different computers.  FYI MOMiAPI.dll is a home grown dll that doesn't crash many other projects in 2011, so I don't think that it can be the culprit.

 

Thanks for all you help.

 

Damian

 

Message 14 of 14
(784 Views)