Persistant error that Labview needs to close

[Rick_L]

After running Labview for a couple of hours the following message appears.

Labview 8.2 development system has encountered a problem

and needs to close. We are sorry for the inconvenience.

If you were in the middle of something, the information you

were working on might be lost.

Please tell Microsoft about this problem.

What is causing this message? I have three machines running the same operating system, same code

and two of them exhibit this symptom.

Please help

[Sima]

This is a pretty generic error you're describing. Does this happen while you're running code or just with LV open? Have you looked at CPU or memory usage in the task manager? If you don't have code running, maybe try a repair or mass compiling the LV directory. If it's only while you're running code, then I'd look closer at code issues.

Also, does LV give you any .cpp errors at all when it crashes or when you reopen it?

Message Edited by Sima on 07-30-2007 04:51 PM

[chrisger]

hi there

for me (and after the experience with my own apps...) this sounds like a memory leak (like Sima suggested). you can use the vi attached to retrieve some information about the process of your app like memory usage etc. try to log these information in a file for further investigation. i'd search for constant increasing memory usage and then i'd try to find the location where the memory is leaking. popular reasons are reopened references in loops and unclosed references from collections.

[Rick_L]

Thank you guys, I'll continue my search and let you know what I find.

[Rick_L]

What I found running and logging as you suggested is, there is a slow increase in the memory thats used. This occurs when all that I am running is the monitor program as well. I am running this same program on 3 other machines operating with Labview 6, two of which are using Windows XP and the other Windows 2000. they are not currently getting this error. It seems to be isolated to Labview 8.2 and 8.2.1. Has somebody else seen this error before? Please respond with any information you can. Thank you.

[Yi Y]

Hi Rick,
It looks like you are experiencing a memory leak, and eventually the memory violation probably causes the OS to shut down LabVIEW.  If you have an open reference that's not being closed, for example, memory leak will occur.  You can use VI Profiler to see which VI is taking up a lot of memory.  Go to Tools->Profile->Performance and Memory...

Yi Y.
Applications Engineer
National Instruments
http://www.ni.com/support