LabVIEW 2019 SP1 Bug Fixes

Panoramica

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

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 Patch

Reported Version:

LabVIEW 2019 SP1

Resolved Version:

LabVIEW 2019 SP1 f3

Added:

Jun 10, 2020

960771

Packed project library not properly replacing a .lvlib

In a project, when you use a packed project library to replace the library from which it was built, the library moves to vi.lib in the project dependencies rather than being replaced. Additionally, the LabVIEW class hierarchy viewer shows that some classes remain linked to the library instead of the packed project library.

Workaround:

Downgrade to LabVIEW 2019 or install the LabVIEW 2019 SP1 f3 Patch.

Reported Version:

LabVIEW 2019 SP1 | LabVIEW 2020

Resolved Version:

LabVIEW 2019 SP1 f3

Added:

Jun 10, 2020

170713 738946

LabVIEW hangs when programmatically opening projects containing FPGA VI-Defined Data Storage and Transfer Nodes

LabVIEW sporadically hangs when programmatically opening projects that contain FPGA VI-Defined
Data Storage and Transfer Nodes such as VI-Defined Registers, Memory, FIFOs, and Handshakes.

Workaround:

Fixed in the LabVIEW 2019 SP1 f3 Patch.

Reported Version:

LabVIEW 2018 SP1

Resolved Version:

LabVIEW 2019 SP1 f3

Added:

Jun 10, 2020

973540

"Equals" primitive for sets/maps is not defined correctly

The "Equals" primitive for empty sets and maps did not consider NULL and "not NULL but has zero elements" to be equal.

Workaround:

Fixed in the LabVIEW 2019 SP1 f3 Patch.

Reported Version:

LabVIEW 2019

Resolved Version:

LabVIEW 2019 SP1 f3

Added:

Jun 10, 2020

978718

TSM crashes when LabVIEW unloads the module

If LabVIEW or the TSM Test Programs recursively load modules, LabVIEW crashes when unloading the modules.

Workaround:

Ensure there is no recursive loading of modules taking place within the LabVIEW hierarchy of any code used by the TSM Test Programs, PPLs included, or install the LabVIEW 2019 SP1 f3 Patch. 

Reported Version:

LabVIEW 2019 | NI Semiconductor Test System Software 19.0

Resolved Version:

LabVIEW 2019 SP1 f3

Added:

Jun 10, 2020

989585

LabVIEW crashes when using "User Interaction.Compare VIs XML" invoke method

If you use the "User Interaction.Compare VIs XML" invoke method to diff two VIs and then copy and attach the images to a pull request, LabVIEW may crash.

Workaround:

Fixed in the LabVIEW 2019 SP1 f3 Patch.

Reported Version:

LabVIEW 2019

Resolved Version:

LabVIEW 2019 SP1 f3

Added:

Jun 10, 2020

255940, 315146

Race condition in creating threads in the LabVIEW Runtime may sporadically hang or crash LabVIEW applications on Linux and macOS systems.


Workaround:

Fixed in the LabVIEW 2019 SP1 f1 Patch

Reported Version:

LabVIEW 2019 | LabVIEW Real-Time Module 2019 | NI Linux RT 2019

Resolved Version:

LabVIEW 2019 SP1 f1

Added:

Mar 17, 2020

259305

No scrollbar in the "Choose Implementation" dialog box.

Workaround:

Fixed in the LabVIEW 2019 SP1 f1 Patch.

Reported Version:

LabVIEW 2019

Resolved Version:

LabVIEW 2019 SP1 f1

Added:

Mar 17, 2020

895756

Shipping examples for malleable VIs not running correctly

The shipping examples for malleable VIs were not running correctly because of an error in two support VIs. Search Unsorted 1D Array.vim and Sort 1D Array.vim have been fixed to sort correctly when a class provides its own custom sort order.

Workaround:

Fixed in the LabVIEW 2019 SP1 f1 Patch

Reported Version:

LabVIEW 2019

Resolved Version:

LabVIEW 2019 SP1 f1

Added:

Mar 17, 2020

899392

Performance scales poorly when a large number of resources are registered for cleaning up post VI execution.

Workaround:

Fixed in the LabVIEW 2019 SP1 f1 Patch.

Reported Version:

N/A

Resolved Version:

LabVIEW 2019 SP1 f1

Added:

Mar 17, 2020

166201 678300

Shared/preallocated SubVI clones can become locked when called from another VI at the same time.

Shared/preallocated SubVI clones can get locked into a state where they cannot be edited. This happens if the SubVI on disk is run as a top-level VI while it is being called from another VI at the same time, and then the calling VI is stopped before the SubVI is stopped.

Workaround:

You can create a wrapper VI around the SubVI and execute that instead of running the SubVI directly. If necessary, on the wrapper VI, you can right-click the SubVI node, choose "SubVI Node Setup..." and enable the "show panel when called" option.

Reported Version:

LabVIEW 2010 SP1

Resolved Version:

LabVIEW 2019 SP1

Added:

Aug 27, 2019

166322 727397

Replacing nodes with Malleable VIs connects wires to unused terminals

Replacing nodes with Malleable VIs (VIMs) sometimes results in the wires being attached to unused terminals of the VIM node, which is an incorrect replace experience.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW 2017 SP1

Resolved Version:

LabVIEW 2019 SP1

Added:

Aug 27, 2019

168749 738672

"Change To Array" and "Change To Scalar" don't work for elements inside a set or map constant

The right-click menu items "Change To Array" and "Change To Scalar" don't work for elements inside a set or map constant. If you chose Scalar Type > Change to Array, it remains scalar. If you choose Array Type > Change to Element, it remains an array

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW 2019

Resolved Version:

LabVIEW 2019 SP1

Added:

Aug 27, 2019

166641 723686

Disabled structures within VIMs are not included in PPL builds, as expected, but the files within these structures are referenced in debugging mode.

Disabled structures from data types not in use by custom made VIMs will not be included in PPL builds as expected. However, files within these disabled structures are still referenced and searched for when called from the RunTime Engine.

Workaround:

Disable debugging when creating the PPL and any following executables.

Reported Version:

LabVIEW 2018

Resolved Version:

LabVIEW 2019 SP1

Added:

Aug 27, 2019

166568 736445

The select function always gives outputs false if nothing is in a while loop

When the select function is in an otherwise empty while loop, the select function will always return false if there is a probe placed on the output or if "retain wire values" is turned on.

Workaround:

Add a Wait (ms) Function with 0 wired to it

Reported Version:

LabVIEW 2018

Resolved Version:

LabVIEW 2019 SP1

Added:

Aug 27, 2019

166210 726223

Build Errors when building Malleable VIs into an EXE

When using default build options (removing block diagrams and removing unused polymorphic VIs) when you have a Malleable VI, you get the following error: "A VI broke during the build process from being saved without a block diagram. Either open the build specification to include the block diagram of that VI or enable debugging to include the block diagrams of all VIs in the build. " Keeping the block diagrams, yet still selecting "Remove unused polymorphic VI instances" , the executable builds but results in a broken run arrow and searches for a few VIMs on load, which it can't find.

Workaround:

Not selecting "Remove Block Diagrams" (under Source Files Settings) and not selecting "Remove unused polymorphic VI instances" (under Additional Exclusions) results in a successful build

Reported Version:

LabVIEW 2018 SP1

Resolved Version:

LabVIEW 2019 SP1

Added:

Aug 27, 2019

173508 739464

Prompt User for Input Express VI only shows "message to display"

The Prompt User for Input Express VI in LabVIEW 2019 only shows the "message to display" option and no inputs are created in the properties box when the VI is run.

Workaround:

If using LabVIEW 2019, convert the Express VI to it's SubVI contents and use the low level VIs instead of the Express VI.

Reported Version:

LabVIEW 2019

Resolved Version:

LabVIEW 2019 SP1

Added:

Aug 27, 2019

166606 735521

Implicit Value (Signaling) Property node does not change type definitions correctly

If you create a type definition with a control and implicitly link the "Value (signaling)" property node, changing the type of the control does not change the type of the property node.

Workaround:

Delete and recreate property node so that it has the correct type.

Reported Version:

LabVIEW 2019

Resolved Version:

LabVIEW 2019 SP1

Added:

Aug 27, 2019

186526 741834

The Compare VI Hierarchies will delete folder named C:\\temp when saving a Microsoft Word Report

After running the Compare VI Hierarchies tool, if a user saves a Microsoft Word Report, a folder named C:\\temp will be deleted if it exists in the user's system. This is not a default folder created by Windows, but it is a common name for a folder that a user may create.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW 2019

Resolved Version:

LabVIEW 2019 SP1

Added:

Aug 27, 2019

172844 738587

Source distribution that would previously fail because of missing commented-out dependencies will now succeed with warnings.

Source distributions that would previously fail due to missing dependency items that were within diagram disable structures will now succeed with warnings.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW 2018 SP1

Resolved Version:

LabVIEW 2019 SP1

Added:

Aug 27, 2019

180018 740616

LabVIEW hangs when double-clicking a recursive dynamic dispatch VI in the "Choose Implementation" diagram preview

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW 2019

Resolved Version:

LabVIEW 2019 SP1

Added:

Aug 27, 2019

182889 741225

LabVIEW crashes when trying to autoindex a Map

The crash occurs autoindexing a map that consists of an I32 key that also uses a set type as a value.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW 2019

Resolved Version:

LabVIEW 2019 SP1

Added:

Aug 27, 2019

315069 733737

CPU Load raises 20% when Front Panel with Custom Style Element is shown

CPU Load raises about 20% if a Front Panel with a Custom Style Element is on the screen. Delete the Element or minimize the Front Panel and the CPU Load drops again within a second.

Workaround:

Use an element of a Standard Style

Reported Version:

LabVIEW 2018 SP1

Resolved Version:

LabVIEW 2019 SP1

Added:

Aug 27, 2019

188376 742093

Maps containing classes cause LabVIEW to crash while probing

Adding a probe to a map containing classes will crash LabVIEW once the class has been instantiated.

Workaround:

This issue has been fixed in the LabVIEW 2019 f2 Patch

Reported Version:

LabVIEW 2019

Resolved Version:

LabVIEW 2019 SP1

Added:

Aug 21, 2019

166643 686080

Replacing ActorFramework.lvlib with a packed project library causes LabVIEW crash

Replacing the ActorFramework.lvlib with a built version of ActorFramework.lvlibp in any project puts LabVIEW into an unstable state and leads to a crash breaking Actor Framework.

Workaround:

Delete the AFDebug folder from \resource. Delete the ActorFramework folder from \vi.lib. Repair the LabVIEW installation.

Reported Version:

LabVIEW 2017 SP1

Resolved Version:

LabVIEW 2019 SP1

Added:

Mar 11, 2018

166332 603576

Channels carrying typedefs/classes create crosslinks when users duplicate projects

Workaround:

This issue was improved in the LabVIEW 2016 f2 Patch to be less frequent, but it was not fixed completely. It is fully addressed in LabVIEW 2019 SP1.

Reported Version:

LabVIEW 2016

Resolved Version:

LabVIEW 2019 SP1

Added:

May 21, 2017

167463 245148

Class Properties dialog sometimes throws timeout error 123 when opening and must be restarted

In LV 2010, there appears to be a timing race condition in the Class Properties dialog for LabVIEW classes. Every once in a while if you try to launch the dialog, the dialog will throw an error dialog reporting error 123 that the dialog has timed out while trying to launch. After you dismiss the dialog, you may see a secondary error dialog. Once you dismiss that, you can relaunch the Class Properties dialog and will generally succeed. There is no danger to your class and no corruption to you class file has occurred. It is solely a bug in trying to launch the dialog.

Workaround:

Hit Continue or OK button to dismiss all error dialogs that come up then retry opening the Class Properties dialog.

Reported Version:

LabVIEW 2010 32-bit

Resolved Version:

LabVIEW 2019 SP1

Added:

Feb 17, 2011

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. 

Patch Version Description
LabVIEW 2019 SP1 f3 This patch only applies to the LabVIEW 2019 SP1 (32-bit and 64-bit) Development Environment and Runtime Engines for Windows.

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