LabVIEW 11.0 crashes when using Match True/False String

[BMajor7]

Does this sound familiar to anyone?

It took quite a while to find out that LabVIEW crashes everytime the VI (red arrow) is called.

It is weird that the VI is called formerly and everything works fine.

Anyway, the workaround is just not using this VI, nevertheless this bug should be fixed.

In my opinion LabVIEW 11.0 crashes much more often than older versions...

[Norbert_B]

Please attach the code as vi or as snippet. Just a screenshot without LV functionality is not suitable in tracking down issues like this....

Norbert

EDIT: Trying a sole "Match True/False String" function in the block diagram does not crash LV on my machine....

[BMajor7]

You are right. I forgot.

Sorry

Ben

[BMajor7]

Neither it crashes on mine if I run it solely or just the first of the two Match True/False String in the attached VI.

We could not reproduce this bug on older Versions of LV either.

But it happens on my machine here always.

Ben

[ErnieH]

Not a bug. Now it is a know issue!

[Norbert_B]

Ben,

Your code crashes LV 2011 on my machine as well.

I don't know whats going on here, but i notified one thing i wanted to pass on to you:

Put a diagram disable structure around the Match True/False String function and set it to enable (so no disabled case).

On my machine, the code does not crash LV 2011 after making this change.

hope this helps as workaround for now,

Norbert

[smercurio_fc]

It also crashes my LV 2011 on my virtual machine. I also noticed that if you delete the wire going to that specific string function's "string" input from the source and replace it with a constant then it doesn't crash. Furthermore, if I connected the input directly to the front panel control it did not crash. As soon as I connected the "string" input to any of the output strings from any of the other string functions it would crash. So, it appears to be a compilation issue. I tried to force a recompile of the VI and that didn't make a difference

[Norbert_B · Accepted solution]

I broke it down a little to the least number of functions needed. CAR #360838.

Workaround as already stated: Put a structure around the last Match True/False String running parallel to String Length. It could be Diagram Disable, Case, Single Sequence Frame.

hope this helps,

Norbert

[BMajor7]

Thank you guys for your effort.

As I have said already: no bug/issue if this exotic VI is not used. But the diagram "enable" workaround is a good trick nonetheless.

Hopefully NI will fix it in the future to avoid that others will lose several hours trying to find out why LV crashes out of a sudden.

Ben

[Norbert_B]

---

@BMajor7 wrote:

Thank you guys for your effort.

As I have said already: no bug/issue if this exotic VI is not used.

[...]

Ben

---

Uh, well, you CAN use it in your VI.... but obviously, you need a weird workaround 😉