CRASH: Replacing enums in statecharts can bring LabVIEW 2012 down

[JKSH]

Environment

Windows 8 64-bit, LabVIEW 2012 32-bit

Steps to reproduce

1. Open the attached project
2. Open Statechart.lsvc/Diagram.vi
3. Double-click on the blue Transition in the middle, navigate to Guard
4. Right-click on the enum constant -> Replace -> Select a VI...
5. Choose "Enum 2.ctl"
6. The "Select the VI to Open" dialog pops up again. Select "Enum 2.ctl" again
7. Observe first weird behaviour: The Guard block diagram is replaced by the enum's front panel
8. Click "Cancel"
9. Double-click on the blue Transition again. LabVIEW crashes here.

Error messages

I first encountered this in a large project with a complex statechart. This was the message shown before LabVIEW died:

With the small example I attached, there was no message at the time of crash -- LabVIEW just aborted silently. When I restarted, it showed (tested twice, same message):

[Branch_Support-NIC]

Hi Rejwan,

Sorry for the late reply, I actually thought I posted this but it turned out that it did not go through. I was able to reproduce the crash in LabVIEW 2013 on Win7. I definitely agree that this is a bug. The workaround is to just add the enum and then delete the original enum. If you want, you can file a CAR on this issue (not sure if you get points for them there like we do). Otherwise, I could file the CAR. Whatever works for you. Let me know your thoughts.

Best Regards,

Bill Everson
Applications Engineer | NIC
SR: 2047047

[JKSH]

Thanks for following up, Bill.

I'm not Rejwan; he might not see your message here. I reported this through the "Email NI" option at http://sine.ni.com/apps/utf8/niae_asc.main last week.

When a CAR is filed, could you please post the number here?

[Branch_Support-NIC · Accepted solution]

Hi JKSH,

Sorry for the incorrect post, I was talking with one of my colleagues on this issue. I was able to reproduce the issue on Windows 7 32-bit and LabVIEW 2013 (32-bit). I filled a bug report (called a Corrective Action Request or CAR) on the issue. The CAR number is 421985. You can use this to track when the CAR will be fixed as there will be a list of resolved CARs in the release notes. I also wanted to post that the workaround for this error is to just add the VI manually and then delete the original VI (as opposed to using the replace feature). 

Thanks for helping find this bug. 

Thanks,

Best Regards,

Bill