Broken Arrow makes LV crash !!

[mekman]

Hi,

A while ago I excperienced a problem with activation of the broken arrow that made LV to crash.

By simple activating the same functionality by using the menu selection "View->Error List"

I found a work-around that worked fine, for a while.

Now I back to square 1. I can not develop my code anymore.

No help seems to be found.

Does anyone have any idea what to do ?

Regards,

Mikael Ekman

[GerdW]

Hi Mikael,

it really helps to see your broken code... Otherwise we are only trying to fish in troubled water!

[Will.D]

Mikael,

A colleague of mine is experiencing this problem as well.  This happened when we upgraded from 8.0 to 8.2.  His 'broken' vi generated the error list in 8.0, but not in 8.2.

He has sent NI his code, and we have also had people from NI in here, but to date, I don't believe we've gotten a solution.  The only really obvious fix is to use the error list workaround you mentioned, and fix what's wrong.

[mekman]

Hi GerdW,

The problem is that there is no (visible) errors in the code.

Without errors it is OK to run the and the arrow is solid.

If I disconnect a wire the broken arrow appear, as it should.

If I activated the LV crashes. That problem make development a hell.

The code is big. Top VI about 3.5 Mb using roughly 50 sub VI.

There has to be a built in problem in the LV.

This problem suddenly appeared after upgrading to LV 8.2.

Regards,

Mikael Ekman

[mekman]

Hi WIll.D,

My problem is that the work-around does not work anymore,

and I'm back to my problem.

Regards,

Mikael Ekman

[GerdW]

Hi Mikael,

maybe the problem is related to the size of your top vi. 3.5MB is rather unusual in my opinion.
Can't you create some subvi's from your top-vi to reduce it's size?

[mekman]

Hi GerdW,

Good thinking, it is a big top VI, indeed.  Of course,  I can break it down into more sub VI:s.

But it is hardly the size causing the problem.

I've removed a lot of code from the top VI, just for test, and the problem is still there.

I've tried several "easy" tricks like creating a new VI and copy the contents.

Still the same result.

Regards,

Mikael Ekman

[GerdW]

Hi Mikael,

when you already tried the easy tricks, you should send this vi to NI with a proper error description. So they can reproduce the problem and (possibly) solve it.
Sorry for not offering more help 😞

[mekman]

Hi GerdW,

That's OK. Thank you.

Regards,

Mikael Ekman