LabVIEW 2020 SP1 Bug Fixes

Overview

The following items are notable issues fixed between the release of LabVIEW 2020 and LabVIEW 2020 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.

Bug Number

Legacy ID

Description

Details

1173469

Converting an LLB to a directory causes Error 7 in LabVIEW 2020

LabVIEW 2020 throws error 7 when converting an LLB to a dictionary.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW: 2020

Resolved Version:

LabVIEW 2020 SP1

Added:

Dec 2, 2020

991959

Performance degradation in Channel Wire generation time

Generating Channel Wires causes performance degradation in LabVIEW 2020.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW: 2020

Resolved Version:

LabVIEW 2020 SP1

Added:

Dec 2, 2020

1013965

Slow application build times for some projects in LabVIEW 2020

Building large projects into applications or other distributables takes longer in LabVIEW 2020 compared to LabVIEW 2019 SP1.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW: 2020

Resolved Version:

LabVIEW 2020 SP1

Added:

Dec 2, 2020

1027690

Upgrading LabVIEW 2019 source to LabVIEW 2020 results in some VIs appearing broken

Upgrading source from LabVIEW 2019 to LabVIEW 2020 breaks some VIs.

Workaround:

Mass compiling the broken VIs or making cosmetic changes and saving can help in some cases.

Reported Version:

LabVIEW: 2020

Resolved Version:

LabVIEW 2020 SP1

Added:

Dec 2, 2020

1004078

Unnecessary Compilation Occurs when a source distribution is set to remove object code

If the Separate compiled code from all source files option is selected when creating a source distribution, LabVIEW compiles the project before saving the source files.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW: 2017

Resolved Version:

LabVIEW 2020 SP1

Added:

Dec 2, 2020

1000943

Passing 1D and 2D arrays of strings between LabVIEW and TestStand is slow

Passing 1D and 2D arrays of strings between LabVIEW 2020 and TestStand using LabVIEW Run-Time Engine causes slowdowns.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW: 2020

Resolved Version:

LabVIEW 2020 SP1

Added:

Dec 2, 2020

1059425

Newly created class overrides of Interface methods will sometimes not save

Sometimes LabVIEW silently fails to save and erases all edits to newly created class overrides of Interface methods.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW: 2020

Resolved Version:

LabVIEW 2020 SP1

Added:

Dec 2, 2020

1079302

LabVIEW crashes when encountering a broken dynamic dispatch VI called from TestStand

When a TestStand step calls a dynamic dispatch VI, the step is configured to call the base class version of the dynamic dispatch VI. If the dynamic dispatch member VI that corresponds to the class input is broken, LabVIEW may hang and crash.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW: 2019

Resolved Version:

LabVIEW 2020 SP1

Added:

Dec 2, 2020

1054394

Restarting a BeagleBone Black using System Configuration causes crash

Connecting to a BeagleBone Black target using the LINX toolkit that is connected to the host via USB LAN can cause the host system to hang and crash.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

System Configuration: 20.0

Resolved Version:

LabVIEW 2020 SP1

Added:

Dec 2, 2020

1126029

LabVIEW 2020 doesn't display UI feedback correctly on macOS 11.0 (Big Sur)

LabVIEW 2020 incorrectly displays selection rectangles, marching ants selection boundaries, dragged objects, and block diagram wiring feedback when run on Big Sur.

Workaround:

Run the following command from Terminal:
defaults write com.ni.labview NSViewAllowsRootLayerBacking  -bool NO

Reported Version:

LabVIEW: 2020

Resolved Version:

LabVIEW 2020 SP1

Added:

Dec 2, 2020

997357

Slowdown in loading PPLs in LabVIEW 2020 from TestStand

Calling LabVIEW 2020 built PPLs from TestStand causes slowdowns if the PPLs are loaded dynamically into memory and unloaded after the step executes.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW: 2020

Resolved Version:

LabVIEW 2020 SP1

Added:

Dec 2, 2020

1123769

LabVIEW 2020 may crash on launch on macOS 11.0 Big Sur

LabVIEW 2020 may crash on launch on macOS 11.0 due to a graphics stack issue.

Workaround:

Run the following commands from Terminal:
defaults write com.ni.labview NSGraphicsContextAllowOverRestore -bool YES defaults write com.ni.labview NSViewAllowsRootLayerBacking -bool NO

Reported Version:

LabVIEW: 2020

Resolved Version:

LabVIEW 2020 SP1

Added:

Dec 2, 2020

1166235

Mic/camera permissions on macOS may not associate properly

A VI requiring mic or camera permissions may not be able to access these system resources or prompt the user for permission.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW: 2019 | LabVIEW: 2020

Resolved Version:

LabVIEW 2020 SP1

Added:

Dec 2, 2020

Additional Patch Information

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.

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