Any idea what would suddenly cause seemingly random "Not enough memory to complete this operation." errors.

[Mugs]

Nothing has changed, the system is not on any network, and has run without issue about a year now.  About a week ago, these errors just started popping up.  About once an hour.  It doesn't seem to cause any problems, except you have to click the OK button to continue.

I am a complete stranger to NI and labview systems, but I am am familiar with control system in general and this seems strange to me.  As far as I know, they are not doing any sort of logging or historical recording, so its not like they are running out of room.

There is plenty of HDD space available.  The system has 1 GB of physical ram, with virtual mem settings of 1.5min - 3 max.

I just don't understand what would cause this problem suddenly after almost a year with no issues??

Any suggestions as to what I can try.  I've read through about a thousand forums here, but none seem to match this issue with the "all of a sudden" type of error.

One said to try to delete labview.ini, which is the only thing that I would try at this point...

Help??

[A_Person]

Hi Mugs:

Have you tried deleting the labview.ini file yet?  If so, what result did that have?

Some further information on the program could help us narrow down the issue.  What is the program doing and which functions are being used?  Is this a program that you can post or at least post a screen shot of?  Are you running any other programs alongside your application?

[mikeporter]

What is the operation that is running out of memory?

If this application a compiled executable or are you running it in the development system?

What version of LV are we talking about here?

My suspicion (and its just a suspicion at this point) is that there is an error occurring that is not being handled correctly. This error in turn is causing the "memory" problem. This suspicion is based on experience where this sort of problem is almost always the result of a badly-handled error. One thing that confuses me though is that you say the program continues running after you click the Ok button.

Mike...

PS: I wouldn't expect deleting the INI file to accomplish anything.

[Jacco K]

Often, this error is the result of trying to create large arrays ( at least, that's how I got it :D). If the length of an array is dependant on the result of a division, it might be caused by dividing by a very small factor or even zero.

Are you sure no setting in the program has changed?

[Mugs]

Hi All,

Thanks for the replys.  I'll do my best to answer the questions.  The system is running Labview 8.5 (I think), or at least a current version.  The Labview program is controlling a NI 7350 Motion Controller for (2) Gemini 6 axis maching stations. 

All I really know at this point, is that it has been running for about a year with no issues, then suddently last week, this error started to pop up.  At this point, nothing seems to be affected as far as functionality, you just have to click ok to close the error screen.

I haven't tried anything yet.  I'll probably go there tomorrow or Monday to try to correct the problem, but I thought I would try to get a clue before I did.

I don't have any of the code at this point, I'm hoping to have this later today.

How can I find out which operation is actually running out of memory??  This would certainly help to figure out what is happening.

I guess the only thing that has me baffled with regard to handling errors or a large array, or division error is why all of a sudden, if nothing has changed?

I read one post that said a power failure caused major problems and Vis had to be reloaded.  I thought this had potential, but the fact that the system seems to run without any problems other than the nuisance error, makes me think this is not the case.

Anyway, I realize this doesn't shed any new light on the subject, but I'll post more information as soon as I have it.

Thanks to everyone and have a great day.

[Mugs]

Thinking a bit more and looking at Jacco's post, I'm wondering if a power failure might have caused some variable to clear, resulting in a divide by zero error?  

[mikeporter]

What exactly is your level of LV skill? Do you know how to turn on execution highlighting? single-step code? How big is the application in terms of number of VIs?

Where is the guy that wrote the code in the first place? Is there any LV expertise in your company/organization?

Mike...

[Mugs]

Hi Mike,

I'm pretty much the bottom of the barrel.  I'm a PLC and motion guy.   I've worked with Labview a couple times, and that is about it.  I have no idea who wrote this thing initially, but as far as I know, who ever did is no longer here.  I have the software, which I need to install, then I can hopefully find all the code and start poking around.

As far as execution highlighting and single stepping code, I am very familiar with the terms, at least as far as having done this before with other packages, just not specifically with LV.

Scary huh...  

[Ben]

---

Mugs wrote:

...

Scary huh...  

---

If you did not have the contributors to this forum, it would really be scary! 

Hi Mugs,

Start with the simple no-brainer stuff. There may have been some disk coruption.

Restore all backups over top of what is on the machine.

Use the NI software disks to do a "repair".

If there are still error then you'll have to get technical and strt poking around to find what is not happening that should happen. There maybe a function running in the background to log something etc. that is blowing up but is not part of your core functionality. Sorry I can't be of more service.

Take care,

Ben

Message Edited by Ben on 02-12-2009 08:41 AM

[AnalogKid2DigitalMan]

It may be wise to monitor the processes in Task Manager to see who is consuming the memory and also look at total available physical and virtual memory over time.

A disk cleanup, defrag, and full disk check could not hurt either.

-Ak2DM