This document contains information about all patches available for the following LabVIEW products:
LabVIEW 2014 SP1 (32-bit and 64-bit) for Windows, OS X, and Linux
LabVIEW 2014 SP1 Run-Time Engine (32-bit and 64-bit) for Windows, OS X, and Linux
All issues fixed in each patch are listed in the tables below. National Instruments strongly recommends that you install the latest patch to all LabVIEW 2014 SP1 installations.
Issues Fixed in LabVIEW 2014 SP1 f7
Note: The f7 patch is not applicable to the Mac and Linux Run-Time Engines (of any bitness).
LabVIEW built .NET assemblies do not marshall some clusters correctly on 64-bit platforms.
VIs configured as shared clones that are included in a PPL are displayed incorrectly as private VIs when using Desktop Execution Trace Toolkit.
In some scenarios, dynamically loading LabVIEW classes with ancestors requiring compilations will cause crashes or undesired behavior.
Issues Fixed in LabVIEW 2014 SP1 f6
Note: The f6 patch is only applicable to the 64-bit version of the LabVIEW 2014 SP1 Development Environment.
LabVIEW 64-bit Development Environment has the potential to crash while running certain RFmx examples. This occurs on 64-bit operating systems with Top-Down Memory Allocation enabled.
Issues Fixed in LabVIEW 2014 SP1 f5
In certain rare cases, the Not A Number/Path/Refnum? function can cause LabVIEW 64-bit to crash; LabVIEW 32-bit is unaffected. Note: A recompile of the VI using the function is required to apply the fix.
Sometimes if RFmx continuously modifies the loading state of the UI thread a race condition can occur and potentially cause a crash.
In rare cases, updating an IMAQ indicator and a LabVIEW Listbox at a high rate in two different, but visible, VIs can cause LabVIEW to crash.
Issues Fixed in LabVIEW 2014 SP1 f3
In a specific case, the Array Max & Min primitive will output the minimum value from the Max Value output.
Loading the LabVIEW 2014 Run-Time Engine and the LabVIEW 2015 Run-Time Engine can cause LabVIEW to crash when it encounters minor internal warnings.
In specific cases, TestStand will receive error -18005 when passing a NULL pointer to LabVIEW.
On subsequent calls, VISA resource and DAQmx resource controls retain their original value when called using a COM interface, such as TestStand.
Static VI calls using Adaptive Inplaceness in a LabVIEW Packed Project Library (PPL) have slow execution time relative to VIs not built into a PPL.
LabVIEW 2014 SP1 (32-bit) for Mac OS X contains the 64-bit version of the liblvexports.a file.
Issues Fixed in LabVIEW 2014 SP1 f1
VeriStand 2014 can crash when closing the project after changing the system definition.
Under certain conditions, running VISA Session Monitor can cause LabVIEW to crash.
In certain cases the Array Max&Min primitive can cause LabVIEW to crash.
Calling a LabVIEW 2014 SP1 64-bit framework in an application linked with OSX 10.10 Yosemite SDK can cause a thread warning to occur.
Pressing escape on the Getting Started Window or Quick Drop in LabVIEW Mac OS causes a pop-up to appear. Selecting an item from this list can cause LabVIEW to crash.
LabVIEW can sometimes handle high priority user events incorrectly causing LabVIEW to crash.
LabVIEW has the potential to crash if there are more than 256 simultaneous event queues active at one time.
Using the Class Browser to select a class, which contains an accessor method via a property node, can cause LabVIEW to crash.