Actor Framework Message Maker crashing LabVIEW

[BillMe]

Over the last several days there must have been 15 crash reports sent to N.I. Apparently, whenever I use Message Maker, I have a 50/50 chance of it working without causing a major malfunction and crashing LabVIEW. When it does work and the new VIs pop up, there is also a good chance that the next time I run my application, it will crash.

Is anyone else having crashes using the Message Maker? Maybe it just doesn't like me...

LV2014 SP1

[BillMe]

The last crash message I got stated:

Access Violation: 0xC0000005

Possible Cause: C:\Program Files (x86)\National Instruments\LabVIEW 2014\vi.lib\ActorFramework\Message Priority Queue\Obtain Priority Queue.vi

This was after I ran Message Maker and then ran my application. Like I said...50/50 chance.

If I don't run Message Maker but do make lots of changes (recode) and then run my app to test, no crashes.

[dsavir]

While I have had some crashes after using the message maker, it certainly wasn't 50 percent of the time...

My actor framework got corrupt at some point and message priority queue was no longer part of the actor framework.lvlib as a result. Is you actor framework lvlib OK?

Do you have anything you wouldn't expect to see in your dependencies?

If you take a fresh project and create an actor and use the message maker, is it still 50/50 crash?

Good luck,

Danielle

[BillMe]

The only dependencies I have are from vi.lib.

I'll try a new, simpler project see what happens. My current project is starting to get up there in size (444 files)

[BillMe]

Ok, I created a new Actor Framework project, created a public VI, ran Message Maker...worked. Created another new VI, ran Message Maker.....crashed:

Exception: Access violation (0xC0000005) at EIP=0x00C681A6

Version: 14.0.1 (32-bit)

Possible Cause: C:\Program Files (x86)\National Instruments\LabVIEW 2014\vi.lib\SourceControl\sccconnsrv\SCC_ConnSrv GenDoneEvent.vi

So, large project or small, the problem persists.

By the way, my installation of LabVIEW 2014 SP1 is hardly two weeks old. I have been running another project (non-AF) without any problems.

[dsavir]

Hi,

I doubt it has any connection, but did you install the f2 patch? Perhaps try uninstalling labview and installing again? This sounds like a fundamental problem of your LabVIEW, have you tried asking NI for support?

[BillMe]

I have Service Pack 1....that came after the f2 patch didn't it?

I planned to call N.I. support if my problem didn't get resolved here. Guess it's time to do that.

[dsavir]

Yup. Sorry I couldn't help.

[justACS]

Do any of the messages you make invoke methods that take a class as an input (other than the actor that owns the method)?

[BillMe]

That would be a no.