Thread failure with Labview 6.0.2

[Mickey]

I had the following message after my application had run for about a day: Failure Thread.cpp line XXXX with Labview 6.
Upgraded to 6.0.2 without any luck.

[Darren]

Hello,

We will probably need some more information in order to help you diagnose the cause of this problem. What kind of hardware (if any) are you using with your system? Did you mass compile all your VIs after installing the 6.0.2 update? You can read the on-line help in LabVIEW to learn more about how to perform a mass compile.

Also, is there any way you can try the application on another computer, just to see if the problem has to do with the computer hardware itself?

If you continue to have any problems, is there any way you can send me a pared-down example demonstrating what your program does, so I can at least investigate to see if I can narrow down the cause of the thread.cpp failure?

One more thing...have you changed the priority and/or execution s
ystem of your main VI or any of your subVIs? If so, change them back to the standard values and see if that solves the problem.

You can also attempt to turn off multithreading in LabVIEW by going to Tools >> Options >> Performance and Disk and de-selecting "Run with Multiple Threads". You have to restart LabVIEW after making this change. Let me know if that helps with the problem.

I appreciate your patience on this issue. Please update me on your progress. Have a pleasant day.

Sincerely,
Darren Nattinger
Applications Engineer
National Instruments

[KH]

I had a similar problem but in LV 6.1 However, the error only showed once. All the other times I had a page fault occur that required LV to exit emmediately.

My main vi has CINs as subvi's involved and I was messing with the priority and execution formats to see which was best, especially execution as subroutines.

I tried changing to not "Run with Multiple Threads" and that didn't work. So I went back to the standard values for priority and execution and the error dissappeared.

Does anyone know why this occurs?

[GregD]

For more information on the Thread.cpp error:
I have a compiled LV6.1 application that is called by another application(a TCP/IP server) with Active-X to look up info in a database with DB Connectivity toolset. The calling program also calls 2 other LV applications with Active-X which have not crashed. The multithread option is OFF. The four programs have coexisted and ran fine for 3-months. Recently I have had 2 thread crashes on the DB toolset program within 1 week. I believe this error may be related to mishandling the object references (either programmatically, by LabView, or by the operating system) due to system load. The operating system is Win2Kpro. The setup ran previously under LV6.0.2 (without the database toolset) for 4-months without err
or. I had previous experienced this problem before on another application that heavily made multiple Active-X calls to several applications in parallel. The problem was very repeatable. I eventually solved it by programmatically "time sharing" the Active-X traffic to limit the amount of open object references.