LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Not enough memory message

How can I remove not enough memory message while running labview code?

0 Kudos
Message 1 of 8
(2,551 Views)

Simple solution, move to 64 bit OS, buy 64 bit LV, buy 1TB of RAM and run the code unmodified.

Alternative:

Remove memory hogs and leaks from the code.

 

For the alternative, you should either learn the important stuff self-paced or attend approrpiate classes like the LV performance class.

 

Norbert

Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
Message 2 of 8
(2,546 Views)

@MKsarith wrote:

How can I remove not enough memory message while running labview code?


Make more memory effencient code.  This is usually an issue with arrays.  There are tricks to reduce the memory usage.  If you post your current code, I'm sure we could show you some of these tricks.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 3 of 8
(2,516 Views)

You can find some methods to help you in the LabVIEW help.  You may also want to read this white paper.  It is dated and does not mention the In Place Element structure or Data Value Reference, but it does have sample code for some of the more important techniques.

0 Kudos
Message 4 of 8
(2,508 Views)

The most common reason (which is mentioned above in different ways) is arrays which builds indefinatly. Can you post some code showing the problem?

/Y

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 5 of 8
(2,494 Views)

0 Kudos
Message 6 of 8
(2,465 Views)

@MKsarith wrote:

@crossrulz@crossrulz


If you are posting a big hierarchy full of VIs, please tell us what the name of the toplevel VI is. Thanks!

0 Kudos
Message 7 of 8
(2,451 Views)

There are a bunch of subVIs still missing.  Look like drivers of some sort.

 

From very quickly looking at your code, I would recommend NOT using an array for your state machine.  Use a Queue instead.  A queue is a set place in memory and therefore a much more efficient.  Each time you delete from an array, new memory allocation must happen.  Not so when you dequeue an element.

 

I haven't dug any more to find anything glaring as of yet.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 8 of 8
(2,404 Views)