Error after a change to an actor

[JIV]

As I work through development with the AF I'm seeing that after making changes, I often some error in which I have to close out my project in order to recover from it.  Everytime after Labview restarts the code runs fine without me being able to reproduce the error.  It almost seems that something is not being re-compiled properly.  Is anybody else experiencing this, is it a known issue and I should force a recompile?  Anyway, just looking for some help because it's pretty anooying when this happens.

Thanks.

[AristosQueue (NI)]

That happens if your VIs are not all stopping properly. If any actor is still running, that can cause problems the next time you run your app, for example, if there's a non-reentrant VI in an actor that you only expect one copy of.

When you stop your app (and don't use the Abort button because that's almost always going to cause this problem), check if any of the classes in your project are still locked because something is still running. That's a good hint.

If that's *not* the problem, then the only time I've seen issues like that is when someone forgets to wire a shift register and so the shift register is remembering the value from the last execution.

[JIV]

I thnk the problem is related to a VI ref.  I made a child class of actor which I call Window Actor.  This subclass has a VI ref control and methods to read and write the vi ref.  I use it to hold the reference of the actor core.vi so that I can send an actor a message to add itself to a certain subpanel, etc.  It seems like if I change a property of the actor core VI for an actor that is a subclass of this window actor, for example the use of vertical or horizontal scrollbars and I don't close labview, the framework crashes the next time I my main VI.  I think I've made this pretty repeatable and could show you at NI Week if we meet up.  Let me know if any of this makes sense to you.

Thanks for your time.

[AristosQueue (NI)]

If you can replicate the bug, do you mind sharing your code so I can file a CAR sooner than NI Week?

[AristosQueue (NI)]

To anyone else following this thread:

JIV sent me his code.

Yes, I was able to replicate in the 2nd Beta.

Yes, it is fixed in the release candidate.

[Q7]

I'm following & having similar issues. Just spent about 36 hours going over code just to find out it worked when I opened everything in a new project, recompiled, and built a new .exe. Other unexpected behaviors when compiling, building dist., etc... but I just landed in Tokyo & won't be able to give specifics for a while.

Seems like the problem lies in the deep dark depths of how LabView handles that little green wire. Asynchronous parallel actors and the use of queues to manage them seems to be revealing many internal performance issues with LabView. Is there anything we can do to our 2011 copies that will patch-up JIV's bug prior to 2012rc? I've just shipped an instrument running v3 Actor Framework and don't want it to burn the building down...not before they buy a few more anyway.

JPB