LabVIEW 2020 Bug Fixes

Überblick

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

Bug Fixes

Bug Number

Legacy ID

Description

Details

1009923

Using Asynchronous Calls by Reference in LabVIEW 2019 SP1 can cause a memory leak.

Workaround:

Fixed in the LabVIEW 2019 SP1 f3 and LabVIEW 2020 f1 patches.

Reported Version:

LabVIEW 2019 SP1

Resolved Version:

LabVIEW 2020 f1

Added:

Aug 31, 2020

1057446

Dynamic Dispatch method overrides do not save updates

In specific situations, changes made to method overrides will not save.  Reopening the VI after saving changes will show the previous code.  This prevents users from updating Dynamic Dispatch VIs for child classes.

Workaround:

None

Reported Version:

LabVIEW 2020

Resolved Version:

LabVIEW 2020 f1

Added:

Aug 31, 2020

997305

LabVIEW can crash or display incorrect text characters when "Use Unicode UTF-8" option enabled in Windows

On systems that have the Windows option "Beta: Use Unicode UTF-8 for worldwide language support" enabled in Region settings, LabVIEW can crash or display garbled text in some languages. To find the Region settings go to Control Panel > Region > Administrative > Change system locale...


This option causes the system default code page to be UTF-8, which LabVIEW does not support.

R&D made changes in the LabVIEW 2020 f1 patch to prevent the crash, but some text will still display incorrectly in some languages.

Workaround:

Disable the "Beta: Use Unicode UTF-8 for worldwide language support" option in Windows.

Reported Version:

LabVIEW 2020

Resolved Version:

LabVIEW 2020 f1

Added:

Aug 5, 2020

1054835

SHA-256/SHA-224 results are incorrect for some message sizes

LabVIEW returns the wrong value for a SHA-256 and SHA-224 for message sizes 56, 120, ..., (N*64+56) bytes

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW 2020

Resolved Version:

LabVIEW 2020 f1

Added:

Aug 31, 2020

1019181

Unable to install package: ni-vipm

An error can occur during the LabVIEW 2020 installation which prevents the install of the package ni-vipm

Workaround:

Deselect VI Package Manager when installing

Reported Version:

LabVIEW 2020

Resolved Version:

LabVIEW 2020 f1

Added:

Aug 31, 2020

1056583

Right-clicking on a class wire/terminal/control when when right-click plugins causes crash

When using right-click plugins, LabVIEW can sometimes crash if right clicking on a class wire, terminal, or control.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW 2020

Resolved Version:

LabVIEW 2020 f1

Added:

Aug 31, 2020

1014647

LabVIEW hangs when the LabVIEW CLI tries to disconnect from the target LabVIEW instance

Automated build systems using the LabVIEW CLI can cause LabVIEW to hang sometimes when disconnecting in the middle of a build.

Workaround:

Avoid trying to disconnect while building.

Reported Version:

LabVIEW 2019

Resolved Version:

LabVIEW 2020 f1

Added:

Aug 31, 2020

1009119

XControls do not load correctly when placed in subVI

When a XControl is placed in a subVI, the XControl may not appear.

Workaround:

Temporarily fix by redropping the XControl in the subVI, but the problem will return when the VI is loaded again.  No workaround for built applications. 

Reported Version:

LabVIEW 2020

Resolved Version:

LabVIEW 2020 f1

Added:

Aug 31, 2020

1048670

LabVIEW crashes with id 0xC0000005 when using some forms of error tracing

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW 2020

Resolved Version:

LabVIEW 2020 f1

Added:

Aug 31, 2020

1078977

LabVIEW 2020 crashes when using the File >> New.. dialog and selecting Class or Interface

Workaround:

Add a class by right clicking and selecting New >> Class or Interface

Reported Version:

LabVIEW 2020

Resolved Version:

LabVIEW 2020 f1

Added:

Aug 31, 2020

1000558

LabVIEW can crash when the Class Hierarchy window is open and missing dependency

If there is a class or interface which has a missing dependency class or interface and the LabVIEW Class Hierarchy window is open and the missing dependency is selected when you close the project or quit LabVIEW, a crash may be encountered.

Workaround:

Deselect the missing item before closing or close the Class Hierarchy window

Reported Version:

LabVIEW 2020

Resolved Version:

LabVIEW 2020 f1

Added:

Aug 31, 2020

1047200

VI for Override Throws Error 7 when overriding Packed Library with Debugging Enabled in LabVIEW 2020

Try to create an override VI in a child class which inherits from a parent inside a Packed Project Library and debugging is enabled, it fails with Error 7.

Workaround:

Build override VI manually.

Reported Version:

LabVIEW 2020

Resolved Version:

LabVIEW 2020 f1

Added:

Aug 31, 2020

1072837

Casting Utility For Actors.vim has incorrect error handling

When messages are created for interfaces there may be incorrect error handling behavior due to wiring in the Casting Utility For Actors.vim

Workaround:

Modify the VIM manually 

Reported Version:

LabVIEW 2020

Resolved Version:

LabVIEW 2020 f1

Added:

Aug 31, 2020

1055195

"Casting Utility For Actors.vim" causes dependency issue when used in a PPL

Workaround:

Edit new messages to separate from the VIM

Reported Version:

LabVIEW 2020

Resolved Version:

LabVIEW 2020 f1

Added:

Aug 31, 2020

1043411

RFmx Memory leak in LabVIEW 2020

Large RFmx applications could see large memory leaks under some circumstances

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW 2020

Resolved Version:

LabVIEW 2020 f1

Added:

Aug 31, 2020

166601 545835

LabVIEW Runtime Engine encounters Worker Thread Limit when using web services on Linux RT-based cRIO

On a Linux RT-based cRIO, the LabVIEW Runtime Engine can get into a deadlocked state waiting for action from the Web Server. This can cause process hangs resulting in a Worker Thread Limit error reported to the user by the Web Server.

Workaround:

Use a mechanism other than web services.

Reported Version:

LabVIEW 2015

Resolved Version:

LabVIEW 2020

Added:

Feb 11, 2020

221253 509876

Bundle by Name function can send wrong pointer into subVI with Call Library Function Node

If a main VI has the output of a Bundle by Name function connected to a subVI, a Call Library Function node within the subVI can receive the wrong pointer from the wired cluster.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW 2013 SP1

Resolved Version:

LabVIEW 2020

Added:

Aug 7, 2016

320200 704376

EXE including 'Std Deviation and Variance' VI is unloadable

Building an executable including a VI that uses the 'Std Deviation and Variance' VI results in an error: "(Hex 0x464) VI is not loadable".

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW 2018

Resolved Version:

LabVIEW 2020

Added:

N/A

316578 457854

Aborting a VI can leave VIs targeted by a Call By Reference node reserved permanently

Workaround:

Close the project to unreserve the VI

Reported Version:

LabVIEW 2013

Resolved Version:

LabVIEW 2020

Added:

Feb 18, 2020

166386

Incorrect behavior when using a Boolean control from the System palette

When using a Boolean control from the System palette and running the VI, you do not see the "hover" picture change. When clicked, the value stays consistent, but the button does not change visually.

Workaround:

Do not use the System Boolean buttons or place them inside another structure.

Reported Version:

LabVIEW 2017 SP1

Resolved Version:

LabVIEW 2020

Added:

Apr 20, 2020

166645

LabVIEW Application Builder fails to build a Source Distribution on Windows when using some specific vi.lib VIs that contain non-Windows components

When using some specific vi.lib VIs (including vi.lib\Utility\tdmsutil.llb\TDMS Component Path.vi) that contain non-Windows components, LabVIEW Application Builder will fail to build a Source Distribution on Windows.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW 2015 SP1

Resolved Version:

LabVIEW 2020

Added:

Apr 20, 2020

188865

When making multiple calls to Python function in a For Loop, the Python execution treats the passed data as a list, rather than a NumPy array

When making multiple calls to Python function in a For Loop, the Python execution treats the passed data as a list, rather than a NumPy array.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW 2019

Resolved Version:

LabVIEW 2020

Added:

Apr 20, 2020

221209

Hovering over an override method in the Project Explorer does not show parent class description if the VI has empty description

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW 2017 SP1

Resolved Version:

LabVIEW 2020

Added:

Apr 20, 2020

166772 587931

Special characters (\r, \n, etc.) are not correctly converted to JSON when using LabVIEW Web services

When a LabVIEW Web service is set to the JSON output type, strings with special characters such as tab constant, carriage return constant, and end of line constant are not escaped properly. This does not include the /s character.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW 2015 SP1

Resolved Version:

LabVIEW 2020

Added:

Apr 20, 2020

166397

Calling a Channel Write VI by reference in a loop results in a compiler error

Workaround:

Call this VI by reference outside the loop.

Reported Version:

LabVIEW 2017 SP1

Resolved Version:

LabVIEW 2020

Added:

Apr 20, 2020

Additional Patch Information

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