The following items are notable issues fixed between the release of LabVIEW 2021 and LabVIEW 2021 SP1, including additional patches and service packs. If you have an issue ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of LabVIEW 2021.
|
Bug Number |
Legacy ID |
Description |
Details |
|---|---|---|---|
| 1500249 |
Sets and Maps Incorrectly Treat Some VI References as EqualInserting a VI reference as a key into a Set or Map can incorrectly fail and return True for "key already included?" when a different reference to the same VI already exists in the set or map, even if the existing reference was obtained separately and has a different reference value or refers to a different clone instance of the VI than the reference being inserted. Workaround: Use the "Clone Name" property or another unique attribute of the VI rather than a VI reference as the key to a set or map datatype when looking up values based on VI instances.
|
Reported Version: LabVIEW 2019 Resolved Version: LabVIEW 2021 SP1 Added: Oct 14, 2021 |
|
| 1182809 |
IMAQ Create Executes More Slowly with Additional Calls in Built ApplicationsWhen the IMAQ Create function is built into a LabVIEW application, the execution time increases non-linearly each time it is called.
Workaround: There is currently no known workaround for this issue. |
Reported Version: Vision Development Module: 2019 SP1 Resolved Version: LabVIEW 2021 SP1 Added: Oct 14, 2021 |
|
| 1534200 |
Session to Refnum Sometimes Returns Non-Unique RefnumsMultiple calls to the Session to Refnum function sometimes return the same refnum rather than unique ones.
Workaround: There is currently no known workaround for this issue. |
Reported Version: N/A Resolved Version: LabVIEW 2021 SP1 Added: Oct 14, 2021 |
|
| 1635734 |
LabVIEW Cannot Open VI Because SubVI Cannot Load Default DataLabVIEW returns the following error when opening VIs that use some hardware-related refnums in sets or maps: "LabVIEW load error code 15: Could not load default data."
Workaround: There is currently no known workaround for this issue. |
Reported Version: LabVIEW 2020 Resolved Version: LabVIEW 2021 SP1 Added: Oct 14, 2021 |
|
| 1707381 |
Some Callers Not Updated Correctly after "Replace With" Operation on a Library in a LabVIEW ProjectIn a LabVIEW project, the right-click "Replace with" operation on a library can fail to update some VIs in the project. This issue affects VIs that reference the original library only through a dynamic dispatch call to a class method that is inherited from a parent class and not overridden by the child class wired to the call.
Workaround: There is currently no known workaround for this issue. |
Reported Version: LabVIEW 2020 Resolved Version: LabVIEW 2021 SP1 Added: Nov 2, 2021 |
|
| 1708546 |
LabVIEW Crashes After Moving TestStand UI Controls Out of Tab ControlWorkaround: There is currently no known workaround for this issue. |
Reported Version: LabVIEW 2019 SP1 Resolved Version: LabVIEW 2021 SP1 Added: Dec 2, 2021 |
|
| 1543721 |
LabVIEW Memory Usage Grows Unnecessarily When Using XControl PropertiesLabVIEW may leak memory in running VIs that use XControl property nodes.
Workaround: There is currently no known workaround for this issue. |
Reported Version: LabVIEW 2020 SP1 Resolved Version: LabVIEW 2021 SP1 Added: Dec 2, 2021 |
|
| 1126601 |
LabVIEW Crashes When Saving a Copy of a VI Referencing an XControlWhen saving a copy of a VI that is a member of a library and which calls an XControl that is a member of the same library, LabVIEW crashes if the copy is added to the library.
Workaround: Make a temporary change so that the XControl is broken before copying the VI.
|
Reported Version: LabVIEW 2019 Resolved Version: LabVIEW 2021 SP1 Added: Jan 6, 2022 |
|
| 1176457 |
Event Structure Always Preserves Space for Event Data NodeAn event structure with the Auto Grow option enabled will preserve space for the Event Data Node even if the Event Data Node is not visible.
Workaround: There is currently no known workaround for this issue. |
Reported Version: N/A Resolved Version: LabVIEW 2021 SP1 Added: Jan 6, 2022 |
|
| 1513139 |
Malleable VIs Are Sometimes Erroneously Broken When Operating on Cluster Data Value ReferencesWorkaround: There is currently no known workaround for this issue. |
Reported Version: LabVIEW 2020 Resolved Version: LabVIEW 2021 SP1 Added: Jan 6, 2022 |
|
| 1518822 |
Change Parent Interfaces Dialog Does Not Allow Removal of Missing InterfaceIf a class or an interface inherits from an interface that is missing on disk, the Change Parent Interfaces dialog does not provide a way to remove that parent. Workaround: There is currently no known workaround for this issue. |
Reported Version: LabVIEW 2020 Resolved Version: LabVIEW 2021 SP1 Added: Jan 6, 2022 |
|
| 1528110 |
Objects Are Not Added to Sets and Maps If Parent Interfaces Are PresentWhen adding objects to a set or map, if they inherit from interfaces that are also in the set or map, those objects are erroneously excluded.
Workaround: There is currently no known workaround for this issue. |
Reported Version: LabVIEW 2021 Resolved Version: LabVIEW 2021 SP1 Added: Jan 6, 2022 |
|
| 1529057 |
Ctrl-Delete Keyboard Shortcut Does Not Remove Array ElementUsing the keyboard shortcut Ctrl-Delete can appear to remove an array element but does not update the value of the array.
Workaround: There is currently no known workaround for this issue. |
Reported Version: LabVIEW 2020 SP1 Resolved Version: LabVIEW 2021 SP1 Added: Jan 6, 2022 |
|
| 1539898 |
LabVIEW Crashes When Removing Class Member VI With Recursive CallerLabVIEW may crash when removing a dynamic dispatch method VI from a class. This happens if a child class doesn't implement the method but has a recursive call to it.
Workaround: There is currently no known workaround for this issue. |
Reported Version: LabVIEW 2020 Resolved Version: LabVIEW 2021 SP1 Added: Jan 6, 2022 |
|
| 1564621 |
Block Diagram Wires Sometimes Misaligned After Repositioning FunctionsWorkaround: There is currently no known workaround for this issue. |
Reported Version: LabVIEW 2021 Resolved Version: LabVIEW 2021 SP1 Added: Jan 6, 2022 |
|
| 1596011 |
Block Diagram Wire to Malleable VI is Broken ErroneouslyA wire to a malleable VI can be broken even though the malleable VI accepts the type of the wire.
Workaround: There is currently no known workaround for this issue. |
Reported Version: LabVIEW 2019 Resolved Version: LabVIEW 2021 SP1 Added: Jan 6, 2022 |
|
| 1597634 |
LabVIEW Crashes When Setting Strings[] Property to Empty ArrayIf a combo box has an element whose value is an empty string, then setting Strings[] to an empty array crashes LabVIEW.
Workaround: There is currently no known workaround for this issue. |
Reported Version: LabVIEW 2020 f1 Resolved Version: LabVIEW 2021 SP1 Added: Jan 6, 2022 |
|
| 1602215 |
Wire Context Menu Does Not List All Available Custom ProbesThe Custom Probes section of a wire's context menu does not display probes from <Documents>\LabVIEW Data\Probes.
Workaround: Copy probes to <LabVIEW>\vi.lib\_probes.
|
Reported Version: LabVIEW 2021 Resolved Version: LabVIEW 2021 SP1 Added: Jan 6, 2022 |
|
| 1631819 |
Subpanel Can Fail to Insert VIs After VI Reference ClosedIf a VI inserts another VI into a subpanel and then closes that VI's reference, subsequent attempts to insert any VI into the subpanel can fail.
Workaround: Remove a VI from a subpanel before closing its reference.
|
Reported Version: LabVIEW 2020 Resolved Version: LabVIEW 2021 SP1 Added: Jan 6, 2022 |
|
| 1692754 |
LabVIEW Crashes After Adding Parent Interface to Class With Missing Parent InterfaceLabVIEW crashes after adding a parent interface to a class if the class inherits from a parent interface that cannot be found.
Workaround: There is currently no known workaround for this issue. |
Reported Version: LabVIEW 2021 Resolved Version: LabVIEW 2021 SP1 Added: Jan 6, 2022 |
|
| 1705840 |
Bundle by Name in Malleable VI Updates Wrong Cluster ItemIf a cluster has a nested element with the same name as an element, a Bundle by Name function that is in a malleable VI and configured to the nested element can access the element instead of the nested element.
Workaround: There is currently no known workaround for this issue. |
Reported Version: LabVIEW 2018 | LabVIEW 2020 SP1 | LabVIEW 2021 Resolved Version: LabVIEW 2021 SP1 Added: Jan 6, 2022 |
|
| 1766383 |
Moving Wired Functions on Block Diagram Automatically Routes Wires When "Enable Automatic Wire Routing" Preference is DisabledWorkaround: There is currently no known workaround for this issue. |
Reported Version: N/A Resolved Version: LabVIEW 2021 SP1 Added: Jan 6, 2022 |
|
| 1667266 |
LabVIEW VI Window Title Only Uses Latin-1 Character Encoding on LinuxOn Linux, the window title of a VI does not display UTF-8 encoded extended characters. Workaround: There is currently no known workaround for this issue. |
Reported Version: LabVIEW 2021 Resolved Version: LabVIEW 2021 SP1 Added: Jan 10, 2022 |
|
| 1667279 |
Captions Using Application Font Do Not Display Non-English Characters on LinuxOn Linux, LabVIEW defaults to using Helvetica for the Application Font, which cannot correctly display some non-English characters. Starting in LabVIEW 2021 SP1, LabVIEW on Linux tries to match "sans" as the application and system fonts when the LANG does not match "en_*". Workaround: Configure the Application Font to a font that supports non-English characters.
|
Reported Version: LabVIEW 2021 Resolved Version: LabVIEW 2021 SP1 Added: Jan 25, 2022 |
|
| 1887820 |
LabVIEW 2021 SP1 Leaks MemoryLabVIEW 2021 SP1 causes an increase in the memory usage of some applications unnecessarily over time.
Workaround: You can disable the performance optimization which caused the memory leak by adding "MemoryManger.UseMasterPointerPool = FALSE" to the LabVIEW INI file. LabVIEW 2021 SP1 f1 patch fixes the issue by disabling the performance optimization by default.
|
Reported Version: LabVIEW 2021 SP1 Resolved Version: LabVIEW 2021 SP1 f1 Added: Apr 22, 2022 |
|
| 1759565 |
LabVIEW Appends Extraneous NULL Character to Path When You Drag and Drop a File to a Path ControlWhen you drag a file from the File Explorer to a Path control or constant, the value of the path will have an extraneous NULL character at the end.
Workaround: Manually delete the extra character after completing the drag and drop. Fixed in the LabVIEW 2021 SP1 f2 Patch.
|
Reported Version: LabVIEW 2021 SP1 Resolved Version: LabVIEW 2021 SP1 f2 Added: Jun 27, 2022 |
|
| 1521038 |
LabVIEW for Linux Crashes on Exit after Using RFSA Self-Calibration VIsIn Linux, loading a DLL built in a different version of LabVIEW than the version loading may cause LabVIEW to crash on exit. Using the NI-RFSA Self-Calibration VIs could lead to this crash.
Workaround: Fixed in the LabVIEW 2021 SP1 f2 Patch. |
Reported Version: LabVIEW 2021 Resolved Version: LabVIEW 2021 SP1 f2 Added: Jun 27, 2022 |
|
| 1920163 |
LabVIEW Application Using "Enable Enhanced DSC Run-Time Support" Option CrashesAn application built in LabVIEW with the "Enable Enhanced DSC Run-Time Support" option enabled crashes upon execution.
Workaround: Fixed in the LabVIEW 2021 SP1 f2 Patch.
|
Reported Version: LabVIEW 2021 SP1 Resolved Version: LabVIEW 2021 SP1 f2 Added: Jun 27, 2022 |
|
| 1909340 |
Linux RT System Disconnects When User Opens a Type Definition File from the Search Results WindowWhen running an application on a PC connected to a Linux RT system, opening a type definition file from the search results in LabVIEW can cause the application to disconnect from the remote system. Workaround: Fixed in the LabVIEW 2021 SP1 f2 Patch. |
Reported Version: LabVIEW 2021 | NI Linux RT 21.0 Resolved Version: LabVIEW 2021 SP1 f2 Added: Jun 27, 2022 |
|
| 168361 |
LabVIEW Class is Locked When Not Open in Multiple ContextsIn some instances, a LabVIEW Class is locked and the project reports that it is used in multiple contexts when it is not.
Workaround: Fixed in the LabVIEW 2021 SP1 f2 Patch. |
Reported Version: LabVIEW 2018 Resolved Version: LabVIEW 2021 SP1 f2 Added: Jun 27, 2022 |
|
| 1759565 |
Map Get/Replace Value Structure Fails to Overwrite Data with Array ManipulationWhen using the Map Get/Replace Value Structure with the In-Place Element Structure, if you manipulate the value from the "Get" structure with array functions, the key inside the map will not be overwritten with the manipulated data.
Workaround: Edit the array data in some way, for example, by indexing and building the array after the "get" of the key. Fixed in the LabVIEW 2021 SP1 f2 Patch. |
Reported Version: LabVIEW 2021 Resolved Version: LabVIEW 2021 SP1 f2 Added: Jun 27, 2022 |
|
| 1847167 |
LabVIEW Cannot Connect to a Remote Application to DebugWhen using "Operate≫Debug Application or Shared Library" to connect to an application that was built with the debugging enabled, LabVIEW reports "Failed to connect to the remote application."
Workaround: Fixed in the LabVIEW 2021 SP1 f2 Patch. |
Reported Version: N/A Resolved Version: LabVIEW 2021 SP1 f2 Added: Jun 27, 2022 |
Installing some patches may require certain additional steps or considerations. Please refer to the following table for more information about patches for this release.
These patches currently do not have any special instructions.