Labview hangs on exit after running VI with ActiveX

[Slawek]

I have a vi with an ActiveX container which generates many events (30-50/sec). The events are serviced in queued mode. Among other things the ActiveX object polls internally for snapshot data from DSC Tags (rarely - only once per minute).

After the vi terminates there are two types of errors:
1. Labview can't close even though it is asked to from its main UI - it still resides as a process and is present in the task bar but there is no UI to it - something must be preventing it from closing.

2. After restarting, the VI hangs on the first call to the ActiveX object (create event queue)

Does anyone have an idea what can be happening? Can a large number of ActiveX events cause a problem resulting in Labview ins
tability? Are there any tools to find out what is causing it?

Thanks

[mikeporter]

One possibility is that it there is a very large number of unprocessed events in the queue when you stop the application, and it takes LV time to deallocate all the memory. I had this happen one due to control references that weren't geting closed. After running over night it could literally take LV over an hour to deallocate all the thousands of unclosed references left in memory.

Might be the same sort of thing going on. Watch LV's memory allocation in the Task Manager when you attempt to shut down and see if it is very large and then starts going down very slowly...

Mike...