LabVIEW quits unexpectedly when running on quadcore CPU !

[ThomasV]

Hi !

I am a seasoned LabVIEW developer, and working for an alliance member of National Instruments.

I have built a LabVIEW application for visual inspection, with pretty high demands:

10 firewire camera's, processing times as short as possible.

I've developed the application on my desktop PC (HP Dual Core Workstation). It is running fine.

Because all 10 camera's and inspections should be working in parallel, I have a lot of timed loops.

(10 acquisitions, 10 inspections, 10 sequencers, user interface, logging, DAQ, TCP,...)

The processor property of these timed loops are set to '-2' (automatic, LabVIEW decides).

So on my desktop it is running great.

Then I copied the code to the target PC (HP Core2Quad Workstation).

After launching the application, LabVIEW immediatly quits without message or error.

Started to try some things, and I first found out that, when I set the processor property of each

timed loop to '0' (manual, first processor), the software would run without error.

Also found out that I can use processor 0 and 1.

If I devide the timed loops over three processors, LabVIEW quits unexpectedly again (sometimes after a second, sometimes

10, sometimes 30, but it quits).

I have removed and reinstalled all NI software, but the issue remains.

Can someone please advise?

In the mean time, I will try to find a sort of freeware benchmark application that tests all 4 cores,

to see if nothing is wrong with my pc.

I can't test the code on another quadcore, because this is the only one we have.

Thanks in advance,

Thomas.

------------------------------------------------

Thomas Vandenberghe
Automation Manager
NiniX Technologies
Kleine Monnikenwerve 9
8000 Brugge
BELGIUM
Tel : 32 (0)50 32 89 65
Fax : 32 (0)50 32 89 63
E-Mail = thomas.vandenberghe@ninix-tech.com

[ThomasV]

Hi,

Ive been digging some more.

If i create a new VI, and place 3  empty timed loops in it,

it allready crashes when I use more than 3 cores.

In my example (see screenshot), LabVIEW crashes after 10 to 30 seconds running.

I am using a brand new HP xw4600 core2quad workstation with Windows XP prof (up to date).

Please help!

Thomas.

[GerdW]

Hi Thomas,

this seems related to this one...

[ThomasV]

You're right,

Apparently there is a known problem when using more than half of the cores available on some CPU's.

I am receiving a patch tomorrow, and I will evaluate it.

PS. I am using a lot of timed loops, because I wanted to dedicate each state engine to a certain processor.
As explained in the workaround in the thread you mentioned, I can solve my problem by implementing the
state engines with a regular while loop, and putting it in a timed sequence.

Thomas.

[ThomasV]

I have received a patch from NI, and it works.

LabVIEW doesn't crash anymore.

Thomas.

[Joachim082]

Hi,

I have the same problem on my quad-core computer. May you share the patch or is it restricted only for your test purpose?

Kind Regards,

Joachim

[ThomasV]

Hi,

Could you send me an email?
I will forward you the patch.
it@ninix-tech.com

Thomas.

[Aristocrate]

Hi,

I hvave the same issue, would you mind sending me the patch as well?

I'm using LabVIEW 2013, will it work with it? or it is valid for all NI Software?

Thanks

[mikeporter]

The thread you added onto was 6 years old and at least that many versions of LV back.

You should start a new thread and say specifically when LV crashes. Also it might be helpful to know things like the OS you are running, what hardware you are using or if you have any special drivers installed.

Simply piling on and saying, "me too! me too!" isn't very helpful.

Mike...