Archived: LabVIEW 2013 SP1 Bug Fixes

NI does not actively maintain this document.

This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.


The following items are the IDs and titles of a subset of issues fixed between LabVIEW 2013 and LabVIEW 2013 SP1. If you have a CAR ID, you can search this list to validate that the issue has been fixed.


IDLegacy IDFixed Issue
.NET event leaks memory when register/unregister repeatedly
Using save for previous on a for loop containing a subdiagram label in LabVIEW 2013 causes the loop N terminal to appear on top of the subdiagram label
Crash when deleting a newly created comment with Automatic Tool Selection turned off.
When repairing LabVIEW 2013, the service locator dependency is uninstalled
Using the Get Waveform Attribute in a subVI can cause incorrect data to be returned to the main VI
If an HTTP method VI outputs an analog waveform it cannot be locally debugged
Deploying a Web service to the Application Web Server gives an error "NI Application Web Server service is still starting"
Under certain conditions, a compiler optimization will cause array shift registers to share memory space.
In LabVIEW 2013, once a Type Definition is made a Strict Type Def, it can not be made non-strict.
If a LabVIEW executable containing .NET is included in an installer, it will fail to run when installed
Calling Quit will not quit LabVIEW if the calling VI also contains an event structure handling the Application Instance Close Event
Building an installer with VIs that contain unsatisfied dependencies within diagram disable structures fails with Error Generating Preview
In LabVIEW 2013, including VIs from some libraries causes building an installer to fail with error 1 "Error Generating Preview"
Under certain circumstances an internal race condition can cause the LabVIEW UI thread to stop updating front panel objects
LabVIEW crashes when .NET event callback calls a VI that has already been deregistered in LabVIEW.
.NET event callbacks to VIs that are already unloaded causes memory access violations
In LabVIEW 64bit manipulating arrays with the Array Subset node can cause LabVIEW to crash

Glossary of Terms


  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on  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).