Actor Framework: LabVIEW disappears after launch

[TiborK]

Dear community, I am dealing with a really interesting problem.

Using:

LabVIEW version 2016 Pro Dev

Actor Framework

Test 1:

Opened a separate library with 1 test actor. Launch it, no crash, works fine.

Test2:

Opened a LabVIEW project with more actors in it, but still when I launch the same testing actor as previously, LabVIEW just disappears in the point where opening VI reference of the actor.

Between the test actor launcher and the rest of the code, there is just one common stuff, they are using Actor Framework lib.

Even if some actor will be broken, that should not influence the Test actor launcher itself.

Other info:

- the actor framework library was not changed

- tested on 2 PC, same problem

Possible issues:

- some AF overridden method's property was changed? (reetrancy, etc) -> checked, but seems ok

- some VI is broken? -> checked when opened project, no

I know, it can be hard to help, but maybe somebody met with this problem.

Thank you!

[LucianM]

Not clear what exactly you mean by LabVIEW disappears. Can you share the code of that actor?

[Kyle97330]

Can you check and see if LabVIEW generated a crash report?

If there was one made, you'll find it here:

<Your user documents folder>\LabVIEW Data\LVInternalReports\LabVIEW\<Your LabVIEW version number>\

Sort by the date of the folder creation to see if you see one time a timestamp matching one of your recent attempts.  Sometimes it's empty or only contains .DMP files, but if you can find anything with TXT file (possibly inside of ZIP files) then those can sometimes point towards the culprit.

[TiborK]

Hi Lucian, thanks for the question.

LabVIEW disappears = application is doing something in one second and in the next there is no evidence of its running. No process in Task Manager, no Service, no crash reporting

The code for the "Test actor" is simple as shown in the attached picture "System launcher.png", the significant code is before the Case Structure, because the issue happens inside the "Actor Framework.lvlib:Actor.lvclass:Launch Actor Core.vi" as shown in the picture "LV Crash.png".

While debugging, it is doing something 1-2 seconds in this function "Open VI Reference" and then LabVIEW disappears.

Unfortunately I cannot provide you the whole actors structure where the issue comes up, but attached you can find example of usage in project.

[TiborK]

Hello Kyle97330, thanks also.

there is no crash report, just *.dmp files (no zip, no txt). Seems to me that the crash reporter also crashed while creating report ?!?

[TiborK]

I have found project version with this problem and version without it, but there are lots of changes, so the investigation will take a while.

// I got a feeling that some actors property was changed (reetrancy, dependency, hidden conflict, etc) and LabVIEW V16 cannot handle it.

Once it happened the same issue, I have changed one global variable, but in one VI this GV was not refreshed (changed name to longer and data type also).

Also the name of the GV was incomplete when used (for example GV name was "VariableName", but in the constant was shown just partially this name like "VariableNa", now I miss that screenshot), LabVIEW did not found it as error and while creating build it crashed without reporting.

But in today's issue the GV was not changed.