LabVIEW 2017 Bug Fixes

Overview

The following items are the IDs and titles of a subset of issues fixed between LabVIEW 2016 and LabVIEW 2017. If you have a CAR ID, you can search this list to validate that the issue has been fixed.

Bug Fixes

The following items are Bug Fixes in LabVIEW 2017.

IDLegacy IDFixed IssueIssue Details
404983
Dynamic load of LabVIEW Class fails when built into a DLL.N/A
522606
Error Ring does not adhere to dataflow in an executable or in a VI with debugging disabledSee this forum for more details: http://forums.ni.com/t5/LabVIEW/Error-ring-excluded-in-executable/td-p/3100932
524160
Updated Timed Loop Mode example VI to better display custom phase and show correct value for period in context helpN/A
567353
When an XNode output is wired to the Loop count of a Parallel For Loop the VI breaks.Connecting the output of an XNode (such as Match Regular Expression) to the count terminal of a Parallelized For Loop will result in a broken VI. The error list will also be empty in this situation.
571901
Using the BD Get Image Scaled method crashes LV 2014 and 2015 if the depth of the image is 1N/A
572024
Built applications hang in some instances when calling Quit LabVIEWWhen the Customer Experience Improvement Program is enabled and the application uses the Start or Wait on Asynchronous Call VIs it may cause the application to hang if Quit LabVIEW is called.
584378
LabVIEW has the potential to crash when simultaneously setting multiple variant attributes to empty variant constantsN/A
588140
Insert of Compound Arithmetic node on wire can result in undesirable configurationWhen you Quick Drop Insert a Compound Arithmetic node on a Boolean wire, the node is in Add mode, rather than boolean logic.

Also, when you insert a Compound Arithmetic node on any wire, it only has one input.
590370
Levenberg-Marquardt algorithm has poor convergence in some casesIn some cases, NI's implementation of the Levenberg-Marquardt algorithm can have poor convergence.
591709
Calling Format Value on improper value can result in crashCalling Format Value with value input of zero (or unwired) can cause crashes with some input and format strings.
592088
Improper updates of library members when using Actor Framework Message MakerAdding a message to an Actor with the message maker updates all members of the library rather than just the modified members.
594760
Example "Extract number with match pattern" gives incorrect outputFor cases with multiple decimal point separators the example does not yield correct output.
595178
Certain Vision Acquisition Software examples show incorrect title barsN/A
595814
The unflatten from String primitive can take several minutes to return when given malformed input stringsN/A
595815
DataSocket Read VI crashes LabVIEW when calling certain IP addressesN/A
596804
Re-registering a dynamic event can cause subscribing event frames to behave improperlyN/A
597858
File permissions error when saving a LabVIEW file to a Windows Server from Windows 10In some cases, you may receive File Permissions Error 44 when saving a LabVIEW file to a Windows Server from a computer running Windows 10.
598986
Scrollbar does not properly respond to clicks on string constantClicking and dragging the scrollbar in a string constant may move the string constant itself instead of scrolling the contents.
599478
LabVIEW may not update classes on Real-Time targets after changing the inplaceness of a connector pane terminal for a VI within those classesIn rare cases, changing the inplaceness of a connector pane terminal for a member VI of a class will not update the class. This can cause deployment problems for deploying LabVIEW classes to Real-Time targets.
600962
VI Analyzer does not properly handle some files when creating file listsWhen a folder contains a file named "icon?" the folder listing that results may be incomplete.
601256
Error message when replacing existing channel endpoint with an invalid configuration is not clearThe message provided when users try to replace an existing endpoint with Read Multiple or Write Multiple, with an array element type which is not supported) is unclear.
601764
Local variables can be created from channel wiresIt should not be possible to create a local variable that references a channel wire.
601807
Resizing a "Register for Events" Node Crashes LabVIEWWhen there are at least two "Register For Events" nodes, one inside and one outside of an Event Structure, and the node outside of the event structure is resized, LabVIEW crashes the second time that the node is resized.
602230
Connecting conflicting channel types does not always break the wireTwo conflicting channel types should but don't break wire if tunnel is in between on forkable channel wire.
602973
In some cases, using the Min/Max function on array of single precision floating point numbers can cause a VI to fail to compileN/A
603092
Rearranging tabs in tab control can cause a crashWhen the tabs of a tab control are rearranged, the tab control is corrupted. This causes a crash when saving or running the VI.
603391
Incorrect Out of Memory dialog when using "Active Plot" property node in 64-bit LabVIEW.In 64-bit versions of LabVIEW, calling the active plot property node of a chart generates a popup message indicating three is not enough memory to complete this operation. After clicking on “ok," the VI runs normally.
603562
Using dynamically dispatched VIs with unwired input terminals can, in some cases, cause crashesN/A
603576
Channels carrying typedefs/classes create crosslinks when users duplicate projectsN/A
603854
QMH project template contains a potential race conditionA Merge Errors is needed within the QMH Main VI to avoid a potential race condition with registering for events:
605231
Attempting to abort a VI may not always cause the VI to abortAttempting to abort a VI while stopped at breakpoints within an Inplace Element Structure does result in an abort.
606365
Dragging a control or indicator to the edge of the block diagram can cause duplication of the front panel objectN/A
606847
Dynamic Dispatch VIs break when the class wire is passed through a shift register in specific casesIf the class wire is passed into a loop as both a tunnel and a shift register, in some cases it will break the run arrow
607685
Cast Unit Bases does not correctly remove units from outputIf a control with units is wired to the input of the Cast Unit Bases function, the default output incorrectly contains a unit
609835
Actor Framework debug traces do not occur on Real-Time targetsN/A
611532
Selecting "Use Default if Unwired" on an output tunnel with a LabVIEW class data type will cause a broken VI with no errorsN/A
611810
Saving a VI containing a "Lookup Channel Probe" node for LabVIEW version 2015 and earlier can result in failure to open the saved VIN/A
611838
The abort behavior of the Accumulator Tag channel wire does not match that of other implementations.N/A
612501
Interpolate 2D Scattered VI will return an incorrect value for specific size input valuesN/A
613416
Installing LabVIEW evaluation for Mac can sometimes cause the .app file to be installed to the wrong directoryIf the LabVIEW evaluation installer is run on a machine that has a previous version of LabVIEW installed, the .app file will be installed to the previous LabVIEW version's directory.
614469
Execution Highlighting does not display correctly on Mac OS XN/A
615195
Collapsing "Variant Attribute Get / Replace" border node on In Place Element Structure causes LabVIEW to crashWhen collapsing a "Variant Attribute Get / Replace" border node from the top edge of the node past multiple inputs, LabVIEW can crash.
615288
Previous versions of LabVIEW are unable to open dynamic classes saved using "Save for Previous Version" in 2016N/A
616848
Using Quick Drop to add a Custom Control Template to a VI's Front Panel crashes LabVIEWN/A
617119
Pressing Abort during project creation then creating another project causes LabVIEW to crash in some casesN/A
617504
Dragging the front panel icon of a VI onto the block diagram of another VI will undo the last edit of the dragged VI in some casesWhen creating a subVI by dragging the front panel icon of a VI onto the block diagram of another VI, the last edit made on the original VI will become undone.
617917
Possible crash when loading particular classesIn some cases, particularly with TestStand Fast Loading enabled, loading some classes may cause LabVIEW to crash.
623269
Attempting to drop a file on a path control in OS X will require the file to be dropped below the path control in some casesWhen attempting to drop a file on a path control, you must move your mouse below the path control to drop the file rather than dropping the file directly on the control.
624304
Actors that return an error from Pre Launch Init also send a Last Ack containing the same errorWhen Pre Lanch Init returns an error, the calling Actor will incorrectly receive an error from Last Ack in addition to the error from Launch Root/Nested Actor
624957
Possible memory corruption when opening invalid fileMemory corruption, usually resulting in an immediate crash, can occur when opening a file containing invalid data,
627716
Opening a project with "Messenger Channels" causes a search for Wrapper.lvclassWhen opening a project containing "Messenger Channels," a dialog may occur requesting the user to locate "Wrapper.lvclass." This is most likely to occur the first time the project is opened on a specific machine,
627910
Large projects may have extended save timesWhen saving very large projects with complex dependency relationships, save times may be significantly longer than expected.

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).