Labview 2009f2 crashes when probing

[Daklu]

I've been experiencing a lot of crashes when probing wires in Labview 2009 f2.  Usually it happens when I probe an object wire (no custom class probe), thought it has happened when I probed a global also.  It's gotten to the point where 2009 is almost unusable--I'm afraid to probe anything. 

The error is always the same.  Has anyone else run into this problem?

[Guruthilak]

Hello Daklu,

Just a question...

1) Is this crash oocurs when ever you probe a particuler wire?

2)Is this crash oocurs when ever you probe a particuler wire in a VI?

If yes...Then either you have to rewire that particular wire and try again..Also recompiling "may" be of some use...

Guru

CLA

[Daklu]

Thanks for the response. 

Right now the crash seems to be related to particular classes.  (The other day I was seeing crashes when I probed a specific global, but I no longer have that code available to test.)  I have at least two classes (an abstract parent and a concrete child) that will cause Labview to crash whenever I probe their wires in any vi.  There are other classes in different class hierarchies that I can probe.

Recompiling didn't help.

[NAKeel]

Hi Daklu,

There is a known issue associated with probing LabVIEW OOP wires with IMAQ controls in them.  Do the problem wires contain anything related to IMAQ or VIsion? 

Nick Keel 

Applications Engineering 

National Instruments

[Guruthilak]

If this is the case then what would be solution?

Guru

[Daklu]

"Do the problem wires contain anything related to IMAQ or VIsion?"

Nope.  The child class does make some calls into a .Net assembly that wraps a generic usb driver dll, but no IMAQ or Vision.

[NAKeel]

The solution for the IMAQ issue is to either use indicator instead of probes, or to avoid including IMAQ VI's in OOP classes.  Since you are not using IMAQ, we do not have any recorded issues.  Could you post your crash log and the associated files that are causing the crash.  I would like to reproduce your issue here, so I can report it to R&D.

Nick Keel 

Applications Engineering 

National Instruments

[Neil.Pate]

---

NAKeel wrote:

The solution for the IMAQ issue is to either use indicator instead of probes, or to avoid including IMAQ VI's in OOP classes. 

---

Nice work around!

[Daklu]

I can't post the VI's here, but I could send them to you via email on Monday.

Where does Labview record the crash logs?

[NAKeel]

You can use this article to help you find the crash log:

Where is the Error Log File Saved After a LabVIEW Crash?

http://digital.ni.com/public.nsf/allkb/7E9EBE4CA3B6DCE786257633005E7121?OpenDocument

If you cannot post the VI's on this forum that is no problem.  Just create a service request and we can help you out that way.  The link for that is:

Request Support

http://sine.ni.com/apps/utf8/niae_asc.main?lang=US