LabVIEW 2018 Bug Fixes

Overview

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

JavaScript is disabled. Details


Bug Fixes

The following items are Bug Fixes in LabVIEW 2018.

IDLegacy IDFixed IssueIssue Details
457851
Bundling class data is slower than bundling cluster dataUnbundling or bundling class data is substantially slower than bundling or unbundling a cluster.
536763
Popup Menu can appear only limited number of times before LabVIEW crashes.The number of of times the popup menu can be accessed before the crash depends on the number of items within a menu and how many times this menu is populated.
619819
Icon transparency of VIs is not maintained when building a Packed LibraryN/A
629258
In some cases, reading from a corrupt TDMS file will delete the file from your machineAfter opening a corrupt TDMS file and attempting to read from it, closing the reference to the TDMS file can delete the file from disk in some cases.
630227
LabVIEW incorrectly allows dropping a shared variable in to a clusterLabVIEW crashes when dropping a shared variable from project tree to a cluster on block diagram. This behavior should not be allowed.
631802
Exporting typedef array of numerics to Excel may crash LabVIEWWhen using the right-click menu option to export a non-empty, typedef numeric array's data to Excel, LabVIEW will crash.
639000
LabVIEW crashes when updating the radix of a numeric control on an Actor Core VI that is runningN/A
643107
Changing multiple plots' line styles does not work as expecting in XY graphsIn an XY graph with N data sets, changing the line style of data sets 2 through N will revert the line style for data set 1 to small dash
645059
Uninitialized shift registers may cause incorrect type propagationIn some very rare cases, an uninitialized shift register may cause type propagation to occur incorrectly.
648582
Express VIs cannot be created in certain localized versions of LabVIEWN/A
654024
File Dialog in LabVIEW for macOS has no title barWhen wiring a string to the "prompt" input, this should be written to the title bar. Since there is no title bar, the string will never appear to the user.
658587
Rescripting a message for an actor on a Linux RT target results in error 7N/A
664649
Accessing a DVR and deleting its reference in parallel can, in certain circumstances, cause LabVIEW to crashN/A
666823
VIs that use channel wires are broken when built into a Packed Project LibraryN/A
670440
When dynamically registering events, LabVIEW may behave unexpectedly if an event is fired and unregistered before it is processedN/A
671753
The LabVIEW Application Builder has the potential to hang when building malleable VIs with subarray or substring inputsN/A
672120
Malleable VIs may not properly break after you rename a class method that the mallable VI calls when performing class substitutionN/A
678973
Tools->Synchronize with ni.com icon library fails in the LabVIEW Icon EditorWhen attempting to synchronize the Icon Editor with the ni.com icon library, the operation fails.
681895
When resizing arrays on macOS High Sierra, the array will sometimes not expand or shrinkN/A
684125
In some cases, resizing a Mixed Signal Graph will cause LabVIEW to crashN/A

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).