LabVIEW Run-Time Crash (2009) lvrt.dll

[Sean_N]

Try building it on a different machine so we can rule out the development machine as part of the issue.  Let me know if you still get the error.

[Greg AA]

Hi Sean,

I have done the build from a new machine with a fresh install of Windows XP and LabVIEW 2009.  After a few days of testing the error was observed again.

Any thoughts?

Thanks,

Greg

[Jake_H]

Do you know which version of the Run Time Engine you have installed? 

[Greg AA]

I am using the LabVIEW Run-Time Engine 2009 SP1.

[Jake_H]

Have you tried creating a debuggable executable? It will help pinpoint where in the program the problem is occuring and there's some information on that below.

http://zone.ni.com/reference/en-XX/help/371361F-01/lvhowto/debug_apps_dlls/ 
http://digital.ni.com/public.nsf/allkb/8DA679805915DE40862572D5007B2F70 

Also, I would recommend monitoring Windows performance to see how much memory the executable/run-time is using when it fails. This could help identify a memory leak.

[Yashasvi]

Hi,

This seems to be almost exactly identical to the error that my team is receiving with our application(vision based inspection of pharma products). We contacted our local NI point of contact and after a lot of trial and error, log file generation and assorted other tests, NI responded saying that this error "could" be due to an obscure LV bug in multi column list boxes. Do you also use multi column listboxes in your code and specifically are you using a read property node to read back the contents of the list box? If so, then try doing this:

a. Remove the listbox altogether and replace it with a table instead.

b. Stop using the read property node to read the list box content and instead keep the data in a 2d array and read from the array instead.

We are still implementing the suggestions and testing them out. Will let you know if the bug turns up again. Hope this helps,

Yash

[Greg AA]

Hi Yash,

Yes, this is the identical issue, and I received the same advice from my local NI contact.

I am interested in what you've found however, in my case we use multiple listboxes, and read various properties of these boxes (current value, item names, etc).  Initially NI advised me to remove the "Read Value" property node and replace it with a corresponding local variable.  From what I can tell so far this fixed the problem, although it still may be too early to tell.  NI has also advised that the "Read Item Names" property can also cause the error, which there is no easy fix for (other than the procedure you described, which would be too clunky in our case).  I am still in the process of testing the change.  For us the mean time between errors was fairly large.

I will post any findings here, please feel free to post any updates you find as well.

Thanks!

Greg

[andre.buurman@carya]

Do any of you Greg, Yash already have some results regarding the crash?

[andre.buurman@carya]

In my case this patch solved the problem: http://digital.ni.com/public.nsf/websearch/A22F95B2007DA53B8625773E00636578?OpenDocument. 9.0.1f1.

[Sajeesh]

hiii.....

i am too getting this error while running Excecutable of the VI on windows XP proffesional SP 3.Please solve the issue.