LAbview crash

[TheresaUNCCHEM]

Everytime I try to run my VI, it crashes labview 7.0. It appears to compile fine. I had had 3 internal errors in my log but never did anything about them because they didn't seem to affect the performance when I restarted Labview. Are they related? To try to address any video driver conflict I reinstalled the video driver as suggested by ni.com. I changed some acceleration modes. No luck.

Other VIs that I would consider more complex don't seem to do this.

[Ray.R]

Hi Theresa,

What are your internal errors? It is difficult to determine whether there is a relation between the crash & the errors without knowing what they are.

As for LV7.0, I have used it with both Win-2000 & Win-XP Pro. I did have some issues with XP which are now resolved.

What OS are you running?
Can you also provide more details of the environment leading to the crash?

And don't underestimate the "power" of a small (or seemingly simple) vi. 😉

JLV

[TheresaUNCCHEM]

The errors in the log are listed as diagram.cpp (648), fpsane.cpp (319), and drawingmgr2.cpp (308)

When I tried to look them up on ni.com, diagram.cpp and drawingmgr2.cpp seemed to point to the video driver thing so that's why I tried upgrading that. The fpsane.cpp was supposedly a bad control according to the discussion forum but I ignored it at the time. Would these internal errors occur again and cause the crash without being identified 2x in the lvfailure log?

I am using XP and Labview 7 Express. I also still have Labview 6i on the same computer but have written this code in 7.

This crashing has happened with another program I had written and ended up just abandoning. Both programs involved opening a file (2D array, SGL/binary). Sometimes the crash would come while I was editing. Now it happens every time I try to run this vi.

[Brett_B.]

Theresa,

It sounds as if you have a corrupt VI and or corrupt control. The solution or fix for this would be to identify the corrupt control, delete it, and create a new one. This usually cleans up those .cpp drawing errors. The tricky part is finding the problematic control. Do you know when this started to happen? Would you be able to link this to an individual control or function on the block diagram.

If the VI is corrupt...you can try copying the whole block diagram to a new VI...and the FP as well. Of course, this can be more difficult with larger VIs.

hope this helps,
-Brett