LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

VI's bogging down?

Is there any good reason a VI will start bogging down?  My CPU usage will be running along fine at ~40% and then drop to ~10%, at this point my VI will quit responding or if it does respond it's very sluggish.   I'm running WinXP and LV2009.  It only seems to happen after I've been running for an hour or two, but once it happens the first time... every 5-10 min things will just quit responding normally.  Anyone have any thoughts?

Thanks!

Chad

0 Kudos
Message 1 of 53
(4,148 Views)

Watch your memory usage using the Windows Task manager.

 

That description is the clasic "Running in Virtual Memory" symptom since the process is placed in a Page Fail wait state while the hardware pages in the data from disk.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 2 of 53
(4,139 Views)

Do you have code to look at? Other wise we can just guess at what happens.

 

Array getting to big

Run out of memory

calling something over and over causing memory problems

etc...

Tim
GHSP
0 Kudos
Message 3 of 53
(4,129 Views)

Is there a suggested route to take to correct this problem?  ...a basic solution since this is a "classic" issue.  🙂  ...or better yet, is there a write up that would allow me to learn more about this issue and how to solve it?

 

Ok, after doing a quick search I found that there is the Tools/Profile/Performance and Memory... tool...  Looks like it might be a place to start, unless there are other suggestions?

THX

C

0 Kudos
Message 4 of 53
(4,119 Views)

@chuggins143 wrote:

Is there a suggested route to take to correct this problem?  ...a basic solution since this is a "classic" issue.  🙂  ...or better yet, is there a write up that would allow me to learn more about this issue and how to solve it?

 

Ok, after doing a quick search I found that there is the Tools/Profile/Performance and Memory... tool...  Looks like it might be a place to start, unless there are other suggestions?

THX

C


Start there.

 

I suspect the exact answer to your question can be found in one of these tagged threads which I encorage anyone interested in performance to review.

 

If you have trouble ID the offending code, post back with what you have learned (and code by the way) so others can offer further assistance.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 5 of 53
(4,113 Views)

Well-

Ben's tip on looking at the Windows task manager- memory and page file statistics to confirm that this is  memory leak issue is a start.  Is the memory usage increasing during execution?

 

AEtest suggested showing some code-  We would be able to spot likely causes of this behavior pretty quick so, posting some code is another great suggestion on how to go about "fixing it."  Although- we haven't really identified a "Cause" yet.


"Should be" isn't "Is" -Jay
0 Kudos
Message 6 of 53
(4,107 Views)

@Jeff Bohrer wrote:

Well-

Ben's tip on looking at the Windows task manager- memory and page file statistics to confirm that this is  memory leak issue is a start.  Is the memory usage increasing during execution?

 

AEtest suggested showing some code-  We would be able to spot likely causes of this behavior pretty quick so, posting some code is another great suggestion on how to go about "fixing it."  Although- we haven't really identified a "Cause" yet.


Good! Then it is not too late to still guess.

 

I sense a build array in a loop.... but the image is now starting to fade.

 

Well that's my guess. Smiley Tongue

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 7 of 53
(4,094 Views)

 


@Ben wrote:

@Jeff Bohrer wrote:

Well-

Ben's tip on looking at the Windows task manager- memory and page file statistics to confirm that this is  memory leak issue is a start.  Is the memory usage increasing during execution?

 

AEtest suggested showing some code-  We would be able to spot likely causes of this behavior pretty quick so, posting some code is another great suggestion on how to go about "fixing it."  Although- we haven't really identified a "Cause" yet.


Good! Then it is not too late to still guess.

 

I sense a build array in a loop.... but the image is now starting to fade.

 

Well that's my guess. Smiley Tongue

 

Ben


That was the feeling I was getting from the keyboard too. The vibrations just seemed to say that.

 

Tim
GHSP
Message 8 of 53
(4,091 Views)

@aeastet wrote:

 

...

That was the feeling I was getting from the keyboard too. The vibrations just seemed to say that.

 


If we ever meet, remind me that I owe you a beer.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 9 of 53
(4,087 Views)

I print this page and have it on record. Smiley Happy

Tim
GHSP
0 Kudos
Message 10 of 53
(4,084 Views)