LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Repeatable crash!

I sent an error report about this, but I was able to reproduce the bug outside my project, so I'll post it here, with all the screenshots and attachments I need to 😛

 

I'll explain the procedure I used, but it's possible that a lot of steps are not needed...

 

Initial state (step1.png):

I have a chunk of code that includes a stacked sequence, and some wires as input. These wires ARE LABELED.

In the same VI, I have an empty state-machine kind of structure: a string case inside a while loop.

 

 

I move the stacked sequence and what's around it into the state machine (step2.png)

 

If I save the VI at this point, I get a crash at fpsane.cpp, line 442. If I wait long enough for the auto-save to kick in, I also get a crash.

 

But let's look at some symptoms... Notice on step2.png how a selection rectangle for the labels still appear at their initial location. If I unselect everything, the labels reappear on the wires, but if I try to select them, the selection rectangle still appears where it was before the move.

 

 

The crash upon saving will happen every time... Now, if I make the labels invisible before moving the chunk of code, and set them back to visible after moving the code, everything works fine.

 

 

Some specs:

LabVIEW version 10.0.1

XP 32bit SP3

Intel(R) Core(TM)2 CPU 6700 @ 2.66GHz

2 GB RAM

 

 

Edit:

If that can be of any help, this is what I received from NI after sending the bug report:

 

RE: (Reference#7320545) LabVIEW 10.0.1%2032-bit error log file: textmgr.cpp line 1197

 

In case you want to cross-reference this post to it or something... "you" referring to the NI people.

Download All
0 Kudos
Message 1 of 8
(3,320 Views)

Interesting!

 

If you deselect the wire labels before moving the wires there is no issue and the labels move with the wires. This is unexpected behavior. Cute bug!

this happens when moving any visably labeled wire into or out of any structure that can contain a dropped wire.  

 

Try it yourself!  the workaround is obvious- deselect wire labels before drag-drop


"Should be" isn't "Is" -Jay
Message 2 of 8
(3,289 Views)

Hey sampacio, 

 

Were you contacted about the error report you sent in? An engineer should have been in touch saying whether a Corrective Action Request would be filed. If this has not happened, please let me know and I will do it myself. Thanks!

 

~kgarrett

 

District Sales Engineer
0 Kudos
Message 3 of 8
(3,245 Views)

Nope... not yet. I only received automated replies.

0 Kudos
Message 4 of 8
(3,243 Views)

I am sorry that no one has contacted you! I am curious-how did you file the error log, and when? 

 

I will try to reproduce this behavior on my system, and if successful, I will file a Corrective Action Request (CAR). Either way, I will be in touch with my results. Thanks!

 

~kgarrett

 

District Sales Engineer
0 Kudos
Message 5 of 8
(3,212 Views)

see the example I posted earlier.  (running 2009 sp1 on Win xp)


"Should be" isn't "Is" -Jay
0 Kudos
Message 6 of 8
(3,207 Views)

Well, I clicked 'Investigate error now', and proceeded to the "email NI" step, attached the log, and all that.

 

I sent the error report about an hour before I posted this topic... I wrote the reference number of the report in my first post as well.

0 Kudos
Message 7 of 8
(3,204 Views)

Someone replied, I linked him here to avoid confusion.

 

It's all in your hands now! 😛

0 Kudos
Message 8 of 8
(3,196 Views)