10-23-2024 01:22 AM
Hi, I'm using a Labview program to run a test. The program is running normally with 15 days and it suddenly popped up a message saying: Not enough to complete this operation. I'm not a computer guy and have limited knowledge about memory management. The program is converted to .EXE so I don't have access to the code.
Here are what I've done: 1. I used Labview desktop execution Trace Toolkit to trace the program and it showed that there are some reference leak in this program. 2. I used performance monitor to view memory usage of labview but the memory usage had not significantly increased over time. 3. I have increased virtual memory from 2Gb to 4Gb. The computer has physical16Gb physical memory and 11Gb left when error happens.
I don't know how to locate this error. Since the program will stuck as the message pops out and will never become normal until I kill labview with task manager and restart it, it's very annoying.
The program doesn't crash at a accurate time. Sometimes it will crash after 8 days running.
Do you have some ways to monitor the program so that I can locate the error, like using some software to track the program and find out what operations it performed, how much memory was requested and rejected.
Thanks!
10-23-2024 01:28 AM
Hi Chun,
@ChunBai wrote:
I'm using a Labview program to run a test.
The program is converted to .EXE so I don't have access to the code.
So you use an executable created with LabVIEW!?
Simple solution to your problem: ask the creator/programmer of that executable!
10-23-2024 08:02 PM
Hi GerdW,
The programmer says this is a problem with my computer's hardware and there is nothing wrong with the program. I want to find out the reason so that I can tell the programmer that he need to repair this program.
10-23-2024 08:30 PM
In general, the error states that LV doesn't have enough free memory available from OS for it to continue functioning and this limit is dependent on the bitness of the OS (number of addressable memory locations).
I bet the LV application was built in 32-bit and hence has access to <4GB RAM, though you have a lot more free memory.
10-24-2024 12:19 AM
Hi santo,
Windows task manager displays that this program usually uses 700Mb ~ 1.2Gb memory. So it didn't occupy much memory. This confuses me.
10-24-2024 03:17 AM
If you open lots of references you can run out of available such (i think there's a limit of a million) although the memory itself isn't that big.