3D graph crashes LabVIEW.. again

[SMeserve]

Able to open all, modify, save VI, etc.

[Erik Månsson]

I also experience frequent crashes when using a 3D surface diagram in LabVIEW 8.6 on Windows XP. I was able to use it a bit without crashes for almost a week, but after finishing the program to do all the work I wanted it became very instable.

The attached file contains error_example.vi that uses a sub-VI which does the actual plotting, via a control reference. It is a stripped down version of my original VIs but still shows the problem. While working on "stripping it down" for this bug report, I think I managed to make some versions of the sub-VI that do not cause the crashes, or at least very seldom. More details are in a submitted text file.

// Erik

[HBraithwaite]

Hi Erik,

Agreed, I've looked at these files and followed the steps (with the error example.vi), when opening the angular distr subVI and viewing the back panel the whole of LabVIEW locked up horribly. I tested the same VIs using LV2009 SP1 and found no improvement. It looks like the 3D graphs make use of Xcontrols and I imagine that thats where the issue lies but I hope NI can look into this as there is definately some major problems with the 3D graphing and or the surrounding VIs at the moment.

[NitinD]

Hi Erik,

I could reproduce the crash using the steps that you have mentioned. I have filed CAR# 244175 for the same. Please remain subscribed to this post so that you can answer any follow-up questions.

Thanks for reporting the issue.

Regards,

Nitin

[tmf171]

Has anything new been discovered with this issue. I have run into something similar and need to get it resolved very quickly. The graphs worked fine under labview 8.5.1 and all version of windows.  After upgrading to LabVIEW 2011, the graphs work fine in vista and windows 7, but crash horribly with Windows XP service pack 3. There are still far too many computers in my industry, and there will continue to be for a long time, running Windows XP. This issue is a large problem and we are unsure of where to go. Currently reverting all the code back to 8.5.1 will be extremely difficult.

One thing we did notice is that the memory requirements of the software start skyrocketing when you open up the 3d graph. They start off around 200 meg, which is normal, but by the time the program crashes the memory is about 1.2 gig and rising.

[Kevin_F]

Hey tmf171,

The developers have been having trouble replicating the issue using the code provided earlier.  Do you have particular VI that causes this issue or is it even with a 3d graph shipping example?

[tmf171]

Let me get a computer up and running and see if I can recreate the results with a minimum graph. I know that it happens after our executable is built. It is only on that operating system, we are calling a bunch of very difficult routines by reference, but it really seems to be related to the specific graphs in question. The 3D ones.  We had problems previously even after a mass compile migrating from 8.5.1 to 2011. It seemed all we had to do was 'replace' the graphs with the current ones to keep the program from crashing (development version)  on both vista and windows 7. I'm hoping I can just get a simple graph, create a similar shape to the one we are using and build an executable to run tests with on the other computer.

Thanks for all your help,

Tom

[battler.]

Tabbed application which performs calculations and parses results to 3D graph on hidden tab. 

On Windows XP when user selects tab containing 3D graph the application immediately crashes, every time. 

The 3D graph is not even viewable.  Renders the application useless.

[HBraithwaite]

We have had issues with the 3D graph crash related (and features not working as I've previosuly posted on). In the instance of the whole application crashing we found that by updating the graphics chipset drivers we were able to get back up and running. Just a suggestion which may help a few out.

[Kevin_F]

Hey battler,

Does the application need to be running as an executable to see this behavior or do you get it when just running a VI?  I tried a couple test VI's with the tab control and was able to really slow down LabVIEW and my computer but not cause it to crash.  If you could provide a sample VI that causes that to happen that would be very useful.