Hello again,
I'm building an exe out of my AF project, have removed a lot of cruft and whittled it down closer to the correct implementation, but not yet quite there.
Building with debugging flag set to true and not removing any unused instances (no checkmarks on that page), it builds and runs correctly. The resulting exe also weighs in like SW they'd run at CERN, so I'd like to get that size down.
If I turn off debugging flag in build but still leave the 'remove unused' flags as unchecked, then it also builds and will start running, but then I get the 1556 error coming somewhere from the nether regions of the core actor framework. I think it's coming from the priority queue, but the call chain that is kicked back in the error is insanely long and impossible for me to read. It goes right to the popular 'resetting vi' that never recovers, after kicking the 1556 error several times.
I've gone through and removed all but a few diagram disables, and the remaining ones no longer contain any broken code. I think I'm past the errors that occur in exe's due to unreachable code, or broken code that is unused but pops up during exe time with BD's and such removed. This took care of 1502 errors during build and 2208 errors when trying to start the exe. (The 2208 is a nasty one, no useful message given as to the offender, precious little info available online).
On a whim, I tried adding the AF lib itself and its attendant extra classes to the project and build, but this did not change anything I could see, doesn't seem to be a linking issue there.
I should mention here that I had similar behavior running in 'source' code mode right through LabVIEW when I was upgrading the framework from 2010 user.lib version. I cleaned up some messages and did a mass compile and the problem went away. I don't know if that's necessarily related to this. But the behavior was exactly the same, several 1556 errors followed by 'resetting vi'.
Any ideas? I don't see where there could be a race condition in startup, or rather I should say that I should be immune to any differences in the order things start up ... there's no global sharing outside of the mechanisms provided by the framework, no object does any cute little trick like feedback nodes inside a method, etc. The boundaries between actors are pretty clear cut, no cheating.
In particular, I'd like to get a better idea of what actually causes those 1556 errors. When they happen, all I know is that nothing is going to work even close to as expected. It's kind of an inscrutable black box, it's either working or it completely freaks out with no way I can tell to figure out what it actually was.
I don't want to downvote my own post right off the bat, but this is not actually a showstopper, it's just an itch I want to scratch. The big exe can be dealt with for now if need be, if I have to build in 'rookie' mode.
Thanks in advance...
Here's the error chain, undecorated.
