LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

title bar error

Solved!
Go to solution

I have an *.exe I built that occasionally freezes up when I click on the title bar on the LV icon while it's running and then opens the drop-down list shown below.  Has anyone else experienced this? I am using LV 2009 with XP OS.  Once it freezes up I can't close, move it, etc...  It generally tends to happen when I've selected to not show the menu or control buttons when the exe is run.  I'm sure it has to something with the build settings I'm using that possibly conflict with each other, but can't say for sure.

 

 

 

Error.jpg

0 Kudos
Message 1 of 12
(4,339 Views)
Do you face this in development vi as well? Are you trying to read anything using visa functions?
Message 2 of 12
(4,310 Views)
Can you reproduce the problem and load the code here?
Message 3 of 12
(4,299 Views)

Here is the vi that I'm having trouble with.  I can get it to freeze up any time I right click on the title bar or on the LV icon on the left side of the title bar.  At times it seemed that after a while it would timeout in some way and unfreeze itself, but I haven't figured out what I was doing to get it to do it though.

 

Thanks for the replys!

0 Kudos
Message 4 of 12
(4,274 Views)
I see it won't work without the subvi's.  Is there a way I can upload the vi so that the subvi's are attached to it?
0 Kudos
Message 5 of 12
(4,273 Views)
zip up the entire folder that contains your project and attach it.
0 Kudos
Message 6 of 12
(4,269 Views)
Hopefully this will work.
0 Kudos
Message 7 of 12
(4,261 Views)

My guesses:

 

1.  Greedy while loop.  Put a wait statement in your while loop so it doesn't run too fast.

2.  You are using IMAQ Init and Close on every iteration of your while loop.  Is that necessary?  Usually you should open before a loop, close after, and only do the actions that truly need to be repeated withing the loop.  Perhaps you are generating a memory leak on resources by repeatedly opening and closing in the loop.

 

What does Windows performance manager show while this is happening?  What is the usage on your CPU?

Message Edited by Ravens Fan on 06-09-2010 11:59 PM
Message 8 of 12
(4,241 Views)
I guess ravens fan has nailed it. The best way is just put the grab/acquire inside the loop. It is ok if you initialize once and close once.
Message 9 of 12
(4,219 Views)
I would also suggest to follow above suggestion and try it again.
Message 10 of 12
(4,203 Views)