The software Icon is still on taskbar , after I close the software in 64-bit Windows 7.

[StevenInToronto]

Hi,

I programmed two labview software. One is bigger and the other is smaller. Both  work fine on windows XP. After I move those software to 64-bit windows 7, I found the smaller one can not close correctly, but the bigger one is good. The software Icon of the smaller one is still on taskbar, after I close it. The windows 7 tasks manager shows 'Not responding'. I can not figure out how to fix it. I have to kill the process manually.

Please help me

Thanks a lot.

Steven

[DFGray]

This could be due to any number of issues.  Please post your code so we can take a look.

[StevenInToronto]

I can not upload the code, unless I get approved from my boss.

It is OK on 32-bit windows 7. It only happens on 64-bit windows 7.  Anyone has similar experience?

Thanks a lot.

Steven

[StevenInToronto]

BTW, the Labview rev. is 2011

[StevenInToronto]

Please take a look the code. I delete some detailed information as per my boss's requirements.

Thanks

[JÞB]

You have a race condition caused by abuse on Local variables

event element is going to be overwritten in the lower state machine.  (Which is probably why you are abusing Closetimingloop pick a better exit strategy!)

The best guess is the lower loop finishes and the FP closes but one of your top loops stays running

[StevenInToronto]

I updated the software: I put 'CloseOtherloop'  into the program to ensure the lower loop is the last one to finish. But the problem is still there, the software icon is still on the tasker bar, after I close the software.  

Is there any memory or processor that I should release or kill?

Thanks.

Steven

[JÞB]

I'm fairly certain the solution will not involve beating up another local variable.  switch the bool constant on the last case structure. does the vi actually stop?

Is this problem vi actually a built exe?  if so you need to close app instance not close FP.  (Try using the App.Kind property to drive the last cases selection)

[crossrulz]

---

@JÞB wrote:

(Try using the App.Kind property to drive the last cases selection)

---

I'm more of a fan of the Conditional Disable Structure myself

[Ray.R]

I like the Conditional Disable myself...

I would also refactor the code..  There's too much loose logic and spread of Localized nonsense variables..  

Ok.. trying to sound phylosophical didn't work for me today.. 

But I'd still refactor the code..