Actors appear to shut down, but still lock their libraries. Code included.

[jlokanis]

I don't think your issue is AF specific.  I have applications with no AF where the exact same thing happens.  If I ask the project why a library is locked then it says a VI has reserved the code for execution.  But there are no VIs running.  If I close the project I do not get the warning that some VI are still running like you do if there is code that was not properly stopped.

I am fairly sure that LV is not doing a good job keeping track of running code and is accidentally reserving your classes when it should not.

Unfortunately there is no way to prove this.

[BrianGShea@NGC]

I have expierenced this same issue when using Dynamic Events with an event Structure and not properaly disposing of all the references.

[StevenHowell_XOM]

This is possibly the case....darn LabVIEW housekeeping

[AristosQueue (NI)]

Steven: Can you check LV 2015 SP1? Or... if I get an AE onto this thread, are you able to share your code with them?

[StevenHowell_XOM]

AQ, thanks for the reply. Unfortunately we are locked in to 2014SP1 right now.

I would need to talk to my team lead and find out if I could share my code. It might have to be through a secure channel of some sort...

[AristosQueue (NI)]

In that case, just go through your regular support channels to get to an AE. They can set up those kinds of communications.

[Oli_Wachno]

Just bumped into this issue again

Large Actor application (~75 independent Actors,  2015SP1), they all seem to shut down properly according to Monitored Actor and own logging routines. Still libraries remain locked, VIs are reported to be running when shutting down the project.

I have tried to leave the VI invoking the Root Actor running, no change there. All SubActors are launched using Launch Nested Actor (AutoStop enabled). And since this application has been migrated from 2013, there is even an own version of registering and shutting down SubActors in place, effectively killing each SubActor twice.

Any recommendations before trying with a SRQ?

[drjdpowell]

This reminds me of this blog post Quick Tip: Asynchronously launching VIs the right way

This might be the issue, as some versions of the AF don't have this modification.

[Oli_Wachno]

Thanks for the hint.

(un)fortunately, in LV2015, the AF uses "the proper way".

[Oli_Wachno]

Update on this issue:

sometimes it really helps to look at issues from some distance...

It turned out there was a cheeky helper actor still in the background. Killed this one properly and the world looks beautiful again

Mea culpa, mea maxima culpa