Labview Crashes

[billko]

---

@Martin_Kroner wrote:

I am to slow, sorry..

I did not compile any of my code. It runs in the "development mode" of labview.

I did indeed also change the computer, but this was maybe 6 months before the code became unstable.

---

Ahhh, a basic misinderstanding.  VIs are actually compiled code.*  Pretty weird if you come from a text-based language background.  What Norbert wants you to do is select "Mass Compile" from the Tools --> Advanced menu and mass-compile your project.  🙂

*This is why sometimes if you modify a subVI you have to save the VI that calls it.  it is because it needed to recompile.

[Martin_Kroner]

OK. I will try this and come back to you.

Thanks,

Martin

[Martin_Kroner]

OK, I did it.

There are some warnings but onyl about libraries and VIs provided by by companies to interact with a  their devcies. But non of the vis I wrote myself created an error or warning.

[billko]

---

@Martin_Kroner wrote:

OK, I did it.

There are some warnings but onyl about libraries and VIs provided by by companies to interact with a  their devcies. But non of the vis I wrote myself created an error or warning.

---

That's good!  That means they just recompiled without complaint.  Hopefully this helps - be sure to let us know.  🙂

[Martin_Kroner]

Labview crashed again after my code was running for ~24h. The mass compile apparently did not fix the problem. I am wondering, the error message from the crash log file "Thread consumption suspected" what does this actually mean?  Maybe I can fix this issue by avoiding certain features of Labview that are unstable in my environment?

Thanks for the help!

Martin

[billko]

I have to admit that I am out of ideas.  😞

[chembo]

If your LabVIEW license comes with LabVIEW Desktop Execution Trace Toolkit, you may check it out. It helped me in many cases to troubleshoot errors. I think it is included in the professional LabVIEW package

[AKA_TG]

Is there a particular reason for using 64 bit s instead of 32 bits.

Perhaps you have a very good reason to go 64 bit

Pictures being processed or high rates of data acquisition or large graphical displays..

There Is a 32 bit version of LabVIEW 2013 out there.

If nothing else works for you

I would give the same code a shot in 32 bit mode if at all possible.

To do this however (i Think) complete uninstall of the 64 bit LV is necessary but I am not sure. Others can correct me if I am wrong.

[AKA_TG]

PS

Please don't do anything until you hear more input.

My idea is not a guarantee to fix your issue. I am not total expert in all LV things as seen by my not posting too often.

[billko]

32-bit and 64-bit can live peacefully alongside each other.  Also, your source code opens up fine in either one.