LabVIEW 2019 SP1 Bug Fixes
Overview
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 |
|---|---|---|---|
| 178494 |
Packed Library Compatibility Breaks After Implementing Parent MethodWhen a class uses Call Parent Class Method, but the parent class doesn't implement that method, then adding an implementation to the parent class needlessly requires the child class to recompile. If the classes are in separate packed libraries (PPLs), the child class PPL must be rebuilt. Workaround: Fixed in the LabVIEW 2019 SP1 f4 Patch.
|
Reported Version: LabVIEW: 2019 Resolved Version: LabVIEW 2019 SP1 f4 Added: May 6, 2021 |
|
| 217468 |
Right-Click Menu Commands Fail IntermittentlySome right-click commands fail intermittently. For example, the VI Analyzer command Create » #via_ignore bookmark creates the bookmark but then erroneously deletes it.
Workaround: Fixed in the LabVIEW 2019 SP1 f4 Patch.
|
Reported Version: LabVIEW: 2015 SP1 Resolved Version: LabVIEW 2019 SP1 f4 Added: May 6, 2021 |
|
| 576923 |
Crash When Saving VIs With Corrupted Dependency InformationLabVIEW crashes when attempting to repair VIs that have erroneous internal links to subVIs that aren't used on their diagram.
Workaround: Fixed in the LabVIEW 2019 SP1 f4 Patch. |
Reported Version: LabVIEW: 2019 Resolved Version: LabVIEW 2019 SP1 f4 Added: May 6, 2021 |
|
| 940922 |
New Data Value Reference and Delete Data Value Reference Not Usable in Inlined VIsWorkaround: Fixed in the LabVIEW 2019 SP1 f4 Patch.
|
Reported Version: LabVIEW: 2015 SP1 Resolved Version: LabVIEW 2019 SP1 f4 Added: May 6, 2021 |
|
| 961026 |
Crash When an Element Is Inserted Into a Map After Changing the Data Type Inside the MapWorkaround: Fixed in the LabVIEW 2019 SP1 f4 Patch. |
Reported Version: LabVIEW: 2019 Resolved Version: LabVIEW 2019 SP1 f4 Added: May 6, 2021 |
|
| 954239 |
Crash Loading VIs When Running a Test Sequence in the TestStand Semiconductor ModuleLabVIEW crashes when all of the following conditions are true:
Workaround: Right-click a LabVIEW step in TestStand and select Edit Code before running the test sequence. Fixed in the LabVIEW 2019 SP1 f4 Patch.
|
Reported Version: STS Software Bundle: 19.0 Resolved Version: LabVIEW 2019 SP1 f4 Added: May 6, 2021 |
|
| 970593 |
Editor Responsiveness Is Slow When the Error List Window Is Open and Lists Many ErrorsWorkaround: Close the Error List window when editing VIs.
Fixed in the LabVIEW 2019 SP1 f4 Patch. |
Reported Version: N/A Resolved Version: LabVIEW 2019 SP1 f4 Added: May 6, 2021 |
|
| 970600 |
Cannot Uncheck Options for Custom Actions in NI Package Build SpecificationWorkaround: Fixed in the LabVIEW 2019 SP1 f4 Patch. |
Reported Version: LabVIEW: 2019 Resolved Version: LabVIEW 2019 SP1 f4 Added: May 6, 2021 |
|
| 971623 |
VI Unexpectedly Aborts Execution When Sharing Map With VI That Stopped ExecutingWorkaround: Fixed in the LabVIEW 2019 SP1 f4 Patch. |
Reported Version: LabVIEW: 2019 Resolved Version: LabVIEW 2019 SP1 f4 Added: May 6, 2021 |
|
| 972238 |
Cannot Build Applications on Mac With Xcode 11 or LaterWorkaround: Fixed in the LabVIEW 2019 SP1 f4 Patch.
|
Reported Version: N/A Resolved Version: LabVIEW 2019 SP1 f4 Added: May 6, 2021 |
|
| 974168 |
Right-Click Menu Commands Execute Slowly if Error List Window is OpenRight-click menu commands that are implemented with VIs and use the Right-click Plugin Framework take a long time to complete if the Error List window is open.
Workaround: Close the Error List window when editing VIs. Fixed in the LabVIEW 2019 SP1 f4 Patch.
|
Reported Version: LabVIEW: 2019 Resolved Version: LabVIEW 2019 SP1 f4 Added: May 6, 2021 |
|
| 985611 |
Calls to .NET Assembly Functions With Unsigned Parameter Type Are SlowCalls to .NET assembly functions with unsigned parameter type are much slower in LabVIEW 2019 than they were in LabVIEW 2017.
Workaround: Fixed in the LabVIEW 2019 SP1 f4 Patch.
|
Reported Version: LabVIEW: 2019 | LabVIEW: 2019 SP1 | LabVIEW: 2020 Resolved Version: LabVIEW 2019 SP1 f4 Added: May 6, 2021 |
|
| 1014363 |
Search Sorted 1D Array Function Returns Incorrect Nearest Index for Single-Element ArraysSearch Sorted 1D Array returns 1 instead of 0 when searching an array that contains a single element that is a match for the search. Workaround: Fixed in the LabVIEW 2019 SP1 f4 Patch.
|
Reported Version: LabVIEW: 2019 SP1 | LabVIEW: 2020 Resolved Version: LabVIEW 2019 SP1 f4 Added: May 6, 2021 |
|
| 1210828 |
Crash When Using Array Size Inside For Loop That Indexes a SetWhen running a VI that iterates over a Set of Arrays with a For Loop and uses the Array Size function on an element, LabVIEW will crash. If you save the VI, then LabVIEW will crash when loading the VI. For example:  Workaround: Convert the set to an array before operating on the elements. Fixed in the LabVIEW 2019 SP1 f4 Patch.
|
Reported Version: LabVIEW: 2019 Resolved Version: LabVIEW 2019 SP1 f4 Added: May 6, 2021 |
|
| 1229501 |
Memory Leak When Using "Get Next Non-Text Sibling.vi"LabVIEW leaks memory when using "Get Next Non-Text Sibling.vi" from NI_XML.lvlib.
Workaround: Fixed in the LabVIEW 2019 SP1 f4 Patch.
|
Reported Version: LabVIEW: 2020 Resolved Version: LabVIEW 2019 SP1 f4 Added: May 6, 2021 |
|
| 1249120 |
Crash if Variant to Data Processes ActiveX Data and the Output Is Not WiredWorkaround: Fixed in the LabVIEW 2019 SP1 f4 Patch.
|
Reported Version: N/A Resolved Version: LabVIEW 2019 SP1 f4 Added: May 6, 2021 |
|
| 1271213 |
Slow Execution of Comparison of Variants Containing Large DataLabVIEW makes unnecessary copies of data when doing comparison operations with Variants, which can result in slower performance in LabVIEW 2017 compared to earlier versions.
Workaround: Fixed in the LabVIEW 2019 SP1 f4 Patch.
|
Reported Version: N/A Resolved Version: LabVIEW 2019 SP1 f4 Added: May 6, 2021 |
|
| 1351668 |
Possible Security Vulnerabilities from SQLite Version 3.4Newer versions of SQLite include bug fixes and security improvements.
Workaround: Fixed in the LabVIEW 2019 SP1 f4 Patch.
|
Reported Version: N/A Resolved Version: LabVIEW 2019 SP1 f4 Added: May 6, 2021 |
|
| 1100570 |
LabVIEW Crashes After Selecting a Different .NET Class for a .NET RefnumLabVIEW crashes after you choose a different class from the Select a .NET Class right-click menu on a .NET Refnum.
Workaround: Fixed in the LabVIEW 2019 SP1 f5 patch.
|
Reported Version: LabVIEW: 2019 SP1 Resolved Version: LabVIEW 2019 SP1 f5 Added: Dec 2, 2021 |
|
| 1708546 |
LabVIEW Crashes After Moving TestStand UI Controls Out of Tab ControlWorkaround: Fixed in LabVIEW 2019 SP1 f5 patch.
|
Reported Version: LabVIEW: 2019 SP1 Resolved Version: LabVIEW 2019 SP1 f5 Added: Dec 2, 2021 |
|
| 1554752 |
LabVIEW Cannot Build Packages After Installing 64-bit LabVIEW 2019 SP1 f4 Patch64-bit LabVIEW 2019 SP1 cannot build packages after you install the LabVIEW 2019 SP1 f4 patch because required support files are missing.
Workaround: Fixed in LabVIEW 2019 SP1 f5 patch.
|
Reported Version: LabVIEW: 2019 SP1 Resolved Version: LabVIEW 2019 SP1 f5 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: Fixed in LabVIEW 2019 SP1 f5 patch.
|
Reported Version: LabVIEW: 2020 SP1 Resolved Version: LabVIEW 2019 SP1 f5 Added: Dec 2, 2021 |
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).