XYGraph Cursor legend bug instantly crashes LabView 2012

Hi!
I am just facing a very annoying bug.
Please find my example VI attached, I would like to know wheather you can confirm the bug? Run the VI if you wish to see some curve (actually the bug appears even if you do not put any data on the graph, if you do, just the same) and after that try to click on the cursor legend vertical scrollbar to scroll up or down to see the cursor names.
It instantly crashes my LabView 2012 Full version: 12.0.1f2 (32-bit). This XYGraph always crashes LabView... I cannot go on with my project, now I will just try to bypass the error, I will try to delete the cursors, and add them again...
Anyhow, very strange and annoying behaviour...
Anyone could repeat the same bug?
Thanks for support!
Solved!
Go to Solution.
Attachments:
XYGraph_bug_test1.vi ‏149 KB

hello,
please find attached my example VI, where I would like to programmatically set the label position of a cursor. Why my code does create at every run a new cursor with the same name?
thanks!
Attachments:
cursor_offset_label_via_propertynode.vi ‏12 KB

Similar Messages

Lot of bugs & Crash labview 2012 SP1 in Table control

Run applied vi.
We see lot of bugs in Table control. I fixed some on the right table, but not all.
How fix other?
Thanks in advance, Alex.
Attachments:
NI_BugReport_in_Table.vi ‏30 KB

The attached modification includes a workaround for the ctrl+z bug on the Data Mixer (Not Table). It basically keeps a history of your deleted headers and adds them back in when the user types ctrl+z. Not the most elegant solution, but gives you an example of what you can do to work around it.
You could clean it up by using functional globals instead of shift registers.
www.movimed.com - Custom Imaging Solutions
Attachments:
NI_BugReport_in_Table (Modified).vi ‏49 KB

CRASH: Replacing enums in statecharts can bring LabVIEW 2012 down

Environment
Windows 8 64-bit, LabVIEW 2012 32-bit
Steps to reproduce
Open the attached project
Open Statechart.lsvc/Diagram.vi
Double-click on the blue Transition in the middle, navigate to Guard
Right-click on the enum constant -> Replace -> Select a VI...
Choose "Enum 2.ctl"
The "Select the VI to Open" dialog pops up again. Select "Enum 2.ctl" again
Observe first weird behaviour: The Guard block diagram is replaced by the enum's front panel
Click "Cancel"
Double-click on the blue Transition again. LabVIEW crashes here.
Error messages
I first encountered this in a large project with a complex statechart. This was the message shown before LabVIEW died:
With the small example I attached, there was no message at the time of crash -- LabVIEW just aborted silently. When I restarted, it showed (tested twice, same message):
Solved!
Go to Solution.
Attachments:
Statechart Crash.zip ‏138 KB

Hi JKSH,
Sorry for the incorrect post, I was talking with one of my colleagues on this issue. I was able to reproduce the issue on Windows 7 32-bit and LabVIEW 2013 (32-bit). I filled a bug report (called a Corrective Action Request or CAR) on the issue. The CAR number is 421985. You can use this to track when the CAR will be fixed as there will be a list of resolved CARs in the release notes. I also wanted to post that the workaround for this error is to just add the VI manually and then delete the original VI (as opposed to using the replace feature).
Thanks for helping find this bug.
Thanks,
Best Regards,
Bill
Notes for Branch AE:
Please reply to This Post within 24 hours
The US AE is expected to reply to all of your posts within 24 hours. Having this expectation will keep the escalation moving quickly and toward a fast resolution.
You can also use other communication channels: Phone, Sametime, Lync,etc. to discuss the issue with the US AE. This can help with troubleshooting and quick diagnosis of the issue.
Click here to provide kudos for a post on this page

Cursor Legend Tab Control BUG

Attached is a VI illustrating a bug with the Cursor Legend when graphs are in tab controls. If you enter in a number in the "Cursor X position to move to", then switch pages on the tab control, you'll notice the cursor has moved to the appropriate place, BUT the cursor legend has not changed to reflect that. Once you manually move it, it updates.
In short, if the cursor position changes programmatically, the cursor legend will update ONLY IF THE XY GRAPH IS VISIBLE, even though the cursor position DOES change.
I hope someone from NI will see this post and add it to the bug list (if not already there??). If anyone knows a work around, that would be appreciated also.
Michael
Using LV 8.2
Attachments:
CursorLegendTabControlBUG.vi ‏27 KB

Good idea. It doesn't work exactlly, but gave me the idea for how to work around. It appears even if you have a tab value change event doing the same thing the Cursor X Position numeric indicator value change event, the cursor legend X value will not change. You can even try entering the same value in the indicator and pressing return after switching tabs, the cursor legend will not update. It thinks for some reason it is on the correct index. I made a Tab Value change event that first moves the cursor to the next index, then moves the cursor back to the correct index. Ugly but works. Hopefully in the next ver of LV they will have fixed a lot of these cursor bugs; there is definitely some work to be done (i.e. fixing cursor X position for XY graphs, an extremelly annoying bug)
Michael
Message Edited by miguelc on 02-23-2007 03:49 PM
Message Edited by miguelc on 02-23-2007 03:50 PM
Attachments:
CursorLegendTabControlBUG_wrkaround.vi ‏34 KB

Bind FPGA host reference to type definition in labVIEW 2012 crashes labVIEW

Hi,
I am using FPGA target device 5641R and labview FPGA 2012 with 5640R ver 1.7.
On the configure window of open FPGA VI reference function, choosing the dynmaic mode shows broken arrow when wired to the 5640R configuration VIs (i.e. Configure timebase, Configure ADC default, Configure ADC NCO functions). So i tried the other option which is binding the FPGA host reference to type definition and choose the control from path C:\Program Files\National Instruments\LabVIEW 2012\instr.lib\ni5640R\Configuration\NI-5640R VIs\ni5640R FPGA VI Reference.ctl. But after that when i try to save the VI on which open FPGA VI reference function is placed, labVIEW crashes. I am unable to figure out the reason. Earlier I was working with labVIEW 2011 and it was working fine there. Any suggestions would be highly appretiated.
Please see the attached images for more details.
Thanks
Attachments:
1.png ‏33 KB
2.png ‏71 KB
3.png ‏40 KB

Check out this thread. It looks like someone else ran into a similar issue and made changes that fixed their application.
http://forums.ni.com/t5/IF-RIO/correct-5640r-template-use-recommendation/td-p/1331918
Jeff B.
Applications Engineer
National Instruments

Labview 2012 Runtime Application Crash: Access Violation Error

hi All,
my rather large app that I been develping over teh last few years has recently been crashing.
I do not know if it is since I began compiling it in LV2012 SP1 that the problem occurred or I have some programming error
that I cannot track down.
It use to run with uptimes over months, even with some memory leaks.
If I monitor using Task Manager there is no decernable increase in memory usage.
It crashes on two different systems - both running Windows XP.
The developer version running in LabVIEW 2012 f5 ( Windows XP ) does not crash. Only the runtime version crashes.
It also crashes either if the program sits idle for a few days - 5 or so ( memeory footprint stable ), or if it is used extensively to actively gather and control several instruements ( memory increase matches data size increase )
It does call several external API via ActiveX to spawn off processes, however from the lvlog.txt it seems the crashing is a simple open file that uses the NI supplied String to Config.vi.
I have double/triple check my code and I close any refernces open by the calling vi.
I am sure how to read teh mini-dump files so if someone can look at these it would be apreciated
thanks
Michael
Here are two crash logs:
Attachments:
fde86f7f-a024-417d-ac1c-d38b2e9a41e3.zip ‏61 KB
4f75c413-793d-46db-b66c-889a2f2daf69.zip ‏59 KB
00660fb7-749d-4af5-bcb1-ac5cad73a5cb.zip ‏56 KB

Hi Michael,
It's tough to tell what's going on, especially since it seems like you've really covered your bases! I'm curious about the fact that you don't see the crashes in LabVIEW (LV), just in the Run-Time Engine (RTE). Have you ever tried running it in LV for an extended period of time?
Also, do you have any loops in your program? Perhaps shrinking any waits that might be present and allowing your program to run faster would decrease the amount of time to see these errors from days to shorter.
In the future, when you get a dump file, submit it to our R&D department. It then pops up on a website that allows me to read them. I can also use win debug but that will take me a bit, so I'll have to get back to you on that.
Also, if you could take a picture of the error, that would help as well.
Julian R.
Applications Engineer
National Instruments

LabVIEW 2012 f1 Patch crashes

I've just installed LabVIEW 2012 and unfortunately I've already run into some troubles.
I received a "Setup has stopped working" when I installed the device drivers. But the installation appeared to be fine. LabVIEW started and MAX would open. I did not try connecting to any hardware yet.
When attempting to install the f1 patch, LabVIEW crashed again. Subsequent retries net the same thing.
Has anyone else had this trouble with the patch?
This is on a Win7 machine with LV 8.6, and 2011 previously installed.
Patrick Allen
Solved!
Go to Solution.

Why do you have LabVIEW open when you are trying to install a patch? Are you running other versions of LabVIEW when performing the install? It is highly recommended you are not running anything NI when running installers from NI.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Crashing LabView SignalExpress 2012 at startup

Hi,
I've just installed NI material (PXI-1033) and software which run normaly with MAX
When I try to run LabView signalexpress 2012 and try to open an example or or create a new project, LaBView begins to load then crashes at initialing Style phase. My OS is XP SP3 French, my PC a DELL Optiplex 790. I have uninstall my antivirus, update windows, installed last patch fp3 LabView 2012, but always the same issue. I send screen shot and windows event as attached document.
Thank in advance for your help
Attachments:
Crash_LabView_signalExpress2012.zip ‏468 KB

Hello Rhingray,
Have you tried to uninstall Signal Express and to reinstall it ?
By the way have you tried to reinstall .Net Framework 4 ?
Regards,
Mathieu P. | Certified LabVIEW Associate Developer
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Journées techniques : des fondamentaux aux dernières technologies pour la mesure et le contrôle/comm...

Bug: Windows 7 DLL call to turn off monitor message crashes LabVIEW 10.0f2

Hi,
I wanted to log this bug on the forum. I have already logged this with NI UK Support: CAR# 286873
I was trying to find a way to turn off a laptop lcd
monitor during measurements. I was trying to replicate this
http://codereflect.com/2009/04/03/how-to-programmatically-turn-onoff-your-monitor/
which uses windows messaging.
I found the attached Monitor-1.vi somewhere on the forum that seems to do the above.
However when I run the VI it crashes LabVIEW 10.f2 on Windows 7 32-bit.
cheers
David
Solved!
Go to Solution.
Attachments:
Monitor-1.vi ‏13 KB

Hi Cosmin,
That was it! Thank you so much!
I will let NI UK support that you identified the issue and get them to close the CAR.
cheers
David
Attachments:
Turn off Monitor.vi ‏12 KB

Cursor legend in lv8.2

I'm trying to re-build a project made in LV7.0 but I must do a lot of changes, and I'm very annoyed of it.
I've seen the lv8 cursor legend and I hate it. LV7 style is definitively better.
How can I change column header names? Cursor, X and Y are general, but I'd like more specific names.
Vix
In claris non fit interpretatio
Using LV 2013 SP1 on Win 7 64bit
Using LV 8.2.1 on WinXP SP3
Using CVI 2012 SP1 on Win 7 64bit, WinXP and WinXP Embedded
Using CVI 6.0 on Win2k, WinXP and WinXP Embedded

It is some kind of trick:
change to run-mode (ctrl-m)
change the column width
change to edit-mode (ctrl-m)
EDIT: you might have to 'allow' the user to change the width, (I don't have LV here so I'm not sure how it is named)
Looks kind-a silly to me but it works.
Ton
Message Edited by TonP on 11-08-2006 09:03 PM
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

Cursor Legend not aligned correctly

Hi,
For a while LabVIEW has been misplacing the cursor legend bar. The attached image shows what i am talking about. If I try to move the cursor or have it placed somewhere (Such as at the top of the peaks) it shifts left a little bit. It can sometime be corrected a bit by selecting to the left of the cursor. But it definitely favors the left side of where it is supposed to go.
Thanks
(The red lines on the picture show where the mouse is or where the cursor is supposed to be.
Attachments:
untitled6.PNG ‏7 KB

Hi Mike,
can you find out if the thing is related to these two bugs?
Re: XY graph cursor position bug
CAR ID 119407
property node incorrectly placing cursor (with a workaround)
The ID is not on the bug-fixes list for 8.6, or on the known issues list.
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

Some fonts are not shown correctly in LabVIEW 2012

I found a bug related with fonts in LabVIEW2012 f3 KR.
- When I select NI7SEG in font selection dialog, right font is not shown in the example box.
- Draw text at point.vi shows same problem for some fonts while other fonts are working.
I reported it to Korean NI. As far as I know, this was not reported in previous versions and I couldn't find any related documents in Google.
So, here I would like to know whether it is related with only Korean version. Please let me know if English version is OK.
* OS: Windows 7 32bit KR

Just now, I installed LabVIEW 2012 f3 (32-bit, English) and checked for the issue. But the font(NI7SEG) was not shown properly in VI either.
- Both of Korea and English version of LabVIEW 2012 on Win 7 Korea OS shows wrong results. It is same on 64-bit OS.
- LabVIEW 2010 but on same PC shows correct fonts.
Is there a limit of number of fonts in LabVIEW? There are more than 100 fonts are shown in the "Selection Font" dialog and I can divide them into 3 groups by sequential order. I find that all fonts in the 3rd group are not applied correctly.
(1st group)
Arial Unicode MS...
Bookshelf Symbol 3....
Windings 3
(2nd group)
@Arial Unicode MS...
@Terminal
(3rd group)
Arial...
Consolas...
Courier...
Licida Console...
NI7SEG...
Verdana

XY graph cursor position bug

I have reproduced the bug mentioned here:
http://forums.lavag.org/Graph-Cursor-XY-Position-Bug-t1366.html&gopid=40859#entry40859
I've reproduced this bug (?) in Labview 8.5, with an XY graph doing
much the same as Jack. The attached zip file contains a stripped down
version of my program (originally written by my coworker, Andrew
MacDonald). Run "RENA3 Data Viewer.vi" and follow the instructions.
As Jack said, changing Cursor.PosX to Cursor.Index solves the problem.
I did not find this bug mentioned anywhere other than the above link.
Fraser
Attachments:
XY Graph Cursor Bug.zip ‏142 KB

Hi Karla,
Sorry if that wasn't as obvious as I thought! :-) Hopefully the attached image makes it clear. On the front panel, 'Cursor Channel' is inputted. This is directly wired to Histogram.Cursor.PosX. Immediately following, Histogram.Cursor.PosX is read and wired to the front panel indicator 'Cursor.Cursor Position:Cursor X'. There is always a difference of 15 or 16 between the two values. If there was no bug, these two values should be identical! I can only conclude that Labview is doing something funny...
As I mentioned before, changing Cursor.PosX to Cursor.Index fixes the problem.
A bit of background: my FWHM function outputs the peak channel, and the cursor is supposed to go through the peak so you can have a visual check that it is analyzing the right peak. I noticed that the line would never go through the peak; the line would always have an offset. After wasting a couple of hours, it became clear that I was wiring the correct value into 'Cursor.PosX', but something was going wrong beyond that.
Cheers,
Fraser
Message Edited by fjharris on 01-25-2008 11:34 AM
Message Edited by fjharris on 01-25-2008 11:36 AM
Attachments:
Labview Bug.png ‏27 KB

Bug report: on LabVIEW 2011 SP1 and Windows 8 'Open URL in default browser.vi'

Dear colleagues,
Here is a bug report.
Culprit: 'Open URL in default browser.vi'.
System: Windows 8, Professional. LabVIEW 2011 SP1.
Abnormal behaviour and steps to reproduce:
Above mentioned VI doesn't work when LabVIEW was started with administrator privilegies. And it works as expected when LabVIEW running in normal (non-administrator) mode.
Looking forward to see this fixed.
Best regards,
Igor Titov.
CLD.
=========================
Igor Titov, CLA
WebPager - put LabVIEW front panels into the web page
Labicom.net

Hi Igor,
Unfortunately LabVIEW 2011 SP1 does not support Windows 8. I tested this behavior with LabVIEW 2012 SP1 on Windows 8 and everything worked correctly.
Regards,
Jeff Peacock
Product Support Engineer | LabVIEW R&D | National Instruments

Passing control reference to subVI crashes labview

Hi,
using a image control (as indicator) provided by imaq Vision, I tried to pass the reference of the control to a subVI. On a computer it works and on a other (same labview version, same vision version, same os, same hardware and hardware drivers!), this crashes labview. I tried to close the control refnum at the end of the subVI, but that changed nothing to the issue. Now I use the reference as a global variable and it seems to work...nevertheless, I would like to understand what the issue and if I should remove any passing to subVI of control ref because this can potentially triggers an error. My correlated question is if this global passing is a "fake" workaround or have real chance of improving (this before going through the whole code for changing all passing of reference to subVI)
thanks a lot

Hi,
thank CoastalMaineBird for your answer
How do you know it's this issue which causes the crash?
When I remove this parameter from and the only property node in the subVi that write to it, I have no longer any problem. Moreover, to ensure that's really the "passing", and made a global variable containing the reference to this control and use my original SubVi that do access the control through its reference number
, and it works! In this last exemple, the only change is the way of transmitting the reference
What LabVIEW version?
8.0.1
up to date according Measurement & Automation update tool
Given that one computer works OK, and another crashes, I would say that
you are seeing the effect of something else, not the cause. If passing
a control ref via terminals was fatal, it would be fatal all the time.
You have some other sort of issue, perhaps timing of the different
machines triggers the bug, perhaps running out of memory, perhaps
LabVIEW is corrupted on one machine.... But I don't think changing all
your code to use globals would solve the real problem. Actually, saying that I wonder about problem of synchronisation. I know from Visual C++ that this kind of error happens if two process try to access the same control at the same time. This is typically an error changing from a computer to an other, and mutex or semaphore are the way to deal nicely with that. But does labview contains already such a securisation? If so, the global variable point on a single object and can "fell" the semaphore/mutex. But passing make a copy that will likely have two different semaphore/mutex but will point to a single control! Do someone know if I'm wrong in this idea or not?
Thanks

XYGraph Cursor legend bug instantly crashes LabView 2012

Similar Messages

Maybe you are looking for