LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Use of context menus of the Mixed Signal Graph causes application crash

Use of functions from context menu of the cursor legend of the Mixed Signal Graph causes application crash. When I use context menu from remote panel, application crashes after I perform operations "Bring to center", "Go to cursor", "Create cursor" and "Delete cursor". May be use of any item of the context menu causes application crash, I have not tested them all. When I use context menu locally, application crashes after I perform operation "Change Plot legend to tree view" from context menu of the Mixed Signal Graph. Crash reports are in attached file.

 

I've created support request, but have no received confirmation e-mail, therefore I've duplicated message here.

0 Kudos
Message 1 of 16
(3,207 Views)

Hi Sectoid,

 

Would it be possible to send your code so that I can see if it can be reproduced? What version of LabVIEW are you running?

 

If you are not able to send code, screenshots would be informative. I am curious what else is going on in your code that may cause the crash, even on your local machine.

Rahul B.
0 Kudos
Message 2 of 16
(3,096 Views)

I've created minimal test program which produces same fault. Program becomes faulty when I add event case "Mixed Signal Graph:Cursor Menu Selection" . Project archive and crash reports are in attachment.

 

 

CrashTest Crash Reporter.jpg

Download All
0 Kudos
Message 3 of 16
(3,076 Views)

Application server: Windows 7 Ultimate 64-bit MUI or Windows Server 2008 R2 Standard MUI (LVRTE2013std + 2013DSC_RTS)

Remote Panel client:  Windows 7 Ultimate 64-bit MUI (LVRTE2013min) or Windows XP Professional 32-bit Russian (LabVIEW 2013 professional development system installed), 

Development system: Windows XP Professional 32-bit Russian

0 Kudos
Message 4 of 16
(3,066 Views)

Hi Sectoid,

 

When I run the code on my machine/follow your directions (run, right click on the graph, "Change Plot legend to tree view"), I don't get the same error. Would it be possible to run the sample code locally on a different machine to see if we get the same behavior? I want to determine if this is a machine specific problem. If possible, it would also help if you could generate and send me a MAX technical report, by following the steps in this KB: http://digital.ni.com/public.nsf/allkb/271F252B4EF0A2E0862570E70056A1E4. That was I can compare the differences between our systems to try to find the problem.

 

Thanks,

Rahul B.
0 Kudos
Message 5 of 16
(3,024 Views)

Hi Rahul,
It is possible for me to run test code only on my application server and on virtual machine. I've made MAX reports for both. I can't reproduce bug with "Change Plot legend to tree view" in my sample application, therefore I've sent you private message with link to project archive of application I develop. It definitely have this bug.
But it is more important for me to fix bug with cursor palette context menu because I use cursor palette in my application, while bug with "Change Plot legend to tree view" was found accidentally.

Download All
0 Kudos
Message 6 of 16
(3,008 Views)

Hi Sectoid,

 

I will have a look at this and get back to you. It may take me a little to parse through the information!

 

Best,

Rahul B.
0 Kudos
Message 7 of 16
(2,976 Views)

Hi Sectoid,

 

I have been looking through the reports with some of my colleagues, in addition to the project you sent. Unless I am misunderstanding, it seems as though this issue is machine-specific. As I said, the initial sample code does not reproduce the problem on my machine, whereas the large project you sent me is a significant application and makes it somewhat difficult to pinpoint the cause. There were also some dependencies missing so I could not actually run the code.

 

The error does seem to be in the even structure (the eventoracle.cpp is LabVIEW's event handler). Two suggestions I had were:

 

1)  Try running your code on a fresh local machine. If you can set up a fresh virtual machine (or a separate computer if you have one) that has LabVIEW Development Environment so we can isolate any effects of building into an executable/remote machines in addition to any other affects your computer may be having on this that mine is not, do you still experience that error?

 

2) Try finding a middle ground between the test code you sent and the large project you sent that reproduces/pinpoints the error.

 

I hope these are helpful steps for now. Please let me know any updates as well!

Rahul B.
0 Kudos
Message 8 of 16
(2,948 Views)

Hi Sectoid,

 

Did those steps help at all?

Rahul B.
0 Kudos
Message 9 of 16
(2,925 Views)

Hi Rahul,

 

Last week I was occupied with other project. This week I can make tests you offer.

0 Kudos
Message 10 of 16
(2,911 Views)