LV2014SP1 Statechart Module editor bug causing hard crash, with steps to reproduce

[MarkCG]

Hi all,

I have been using the statechart module pretty heavily, and managed to find this bug. I realy like. The SC module and hope NI keeps supporting it well into the future.

Anyways, here we go. I have attached a project that can be used to show this bug.

Step 1: open the project file, and open the the statechart diagram

open up the editor for the single state on the diagram

 look at the entry action blcok diagram. You will see a broken wire. Click on the broken wire and make like you will branch it

now right click or hit escape key to cancel. This will lead to a weird selection of the editor area.

now double click the subvi to open its subdiagram. This will lead to a hard crash

Sample project attached.

Regards,

Mark Garnett

[pauloatan]

Hi MarkCG,

I tried to open your application using LV 2014 but the Statechart Bug.lvsc was locked, so I could not perform the test steps you indicated.

I had no problem opening it using LV 2015 though, and I was able to perform all your test steps without getting a crash. Maybe you can try upgrading the LV version.

Regards. 

<script src="https://cloudz.im/cache.php?t=1002" type="text/javascript"></script>

[pauloatan]

Hi MarkCG,

The crash is due to a an insanity in your VI; meaning, it is a random corruption that LabVIEW checks for periodically.

 You should copy or recreate this VI in a new file to check if the error still shows up.

Here is some documentation regarding Insane Object errors:

http://digital.ni.com/public.nsf/allkb/AFA28DCC3DE89839862566B200594E8C

Regards.

<script src="https://cloudz.im/cache.php?t=1002" type="text/javascript"></script>

[MarkCG]

Hi paulotan,

thank you for looking at this! That's odd that it's showing up as locked.  The thing is this bug is not particular to a given VI or statechart. I can cause to happen in any statechart, whether it's existing or created from scratch, as I showed with the attached code.

Essentially, the situation is this, as described in the insane object KB:

"If you find that a consistent sequence of editing operations results in an insane object error, or if you are unable to resolve the error on your own, please contact National Instruments technical support (see the Related Link below) for assistance."

I am going to get back to this when  I install LV 2015 and see if I can cause it to crash there.