LV crashes when number of (his own) threads goes over 150.

Question

Hey,
I've found LV crashes when it goes over 150 threads. Is this true? I'm not particularly interested in having so many threads and have already removed the "problematic code" from my application. However, LV should return an error instead of crashing.
How to reproduce:
I'm using LV 8.6 on a dual core Dell Latitude D830, WinXP Prof sp2.
I've created a simple reentrant VI with a TimedLoop inside. The VI is programmed so it consumes minimal CPU resources and memory. The TimeLoop structure creates the threads (in my application, I've replaced them by regular While Loops and it goes fine).
Then I've created another VI that calls the reentrant VI several hundred of times.
Run it and LV crashes when it reaches the 150th iteration. From Windows Task Manager window, CPU use is around 25% and I've only used 20MB of memory, thus it looks alike to be an OS problem.
Is this a configurable parameter in LV? Can I change it? Wich is the maximum number of threads I can create in LV? Can this crash be changed by a simple Error that can be handled?
Thank you and Buenas fiestas!
Guillermo

Answer 1

Hi,
You can find the total number of Threads (not just the LabVIEW ones) into the Windows Task Manager (right click on the task bar >> Task Manager).
Place the attached example VIs (LV 8.6 and LV 8.2) on the same directory. Run "master.vi" and you'll see the number of threads grows with the automatically opened reentrant VIs. When new created threads go beyond 150 (around the 130th FOR loop iteration), LabVIEW suddenly crashes and hangs.
Hope this helps better understand the problem.
Thanks!
Guillermo
Attachments:
master.vi ‏11 KB
reentrant.vi ‏20 KB
VIs for LV 8_2.zip ‏36 KB