This document contains information about all patches available for the following LabVIEW products:
All issues fixed in each patch are listed in the tables below. NI strongly recommends that you install the latest patch to all LabVIEW 2014 SP1 installations.
Issues Fixed in LabVIEW 2014 SP1 f11
Note: The LabVIEW 2014 SP1 f11 patch drops support for Microsoft Windows 7 RTM (with no service pack), Windows Vista, Windows XP, and Windows Server 2003. For more information about the changes to our OS support, refer to KB 79UC78LS, Why Does my LabVIEW, LabWindows/CVI, Measurement Studio, or TestStand Built Installer Fail on Windows XP/Vista and Server 2003?.
| ID | Description |
| 653897 | Make LabVIEW more robust when presented with corrupted resource files.. |
Issues Fixed in LabVIEW 2014 SP1 f10
Note: The LabVIEW 2014 SP1 f10 patch drops support for Microsoft Windows 7 RTM (with no service pack), Windows Vista, Windows XP, and Windows Server 2003. For more information about the changes to our OS support, refer to KB 79UC78LS, Why Does my LabVIEW, LabWindows/CVI, Measurement Studio, or TestStand Built Installer Fail on Windows XP/Vista and Server 2003?.
| ID | Description |
| 624957 | Memory corruption, usually resulting in an immediate crash, can occur when LabVIEW loads a file containing invalid data. |
| 611315 | Queues, notifiers, rendezvous, and semaphores may return an unexpected timeout when used in particular ways. For more information, please see details regarding timeout behavior for these mechanisms in LabVIEW. |
| 470197 | The Application Builder does not detect a naming conflict when VIs have exactly the same name but differ in capitalization. |
| 517128 | The Preview Build functionality in the Application Builder will not detect a naming conflict when VIs have exactly the same name but differ in capitalization. |
| 478801 | LabVIEW is unable to return to the calling VI when debugging a reentrant VI with the "Suspend when called" execution setting enabled. |
| 578871 | LabVIEW has the potential to crash when opening network ports in rapid succession on Linux systems. |
| 635495 | Menus within the LabVIEW environment may not display correctly on systems with display scaling set to greater than 100%. |
| 544526 | (OS X) LabVIEW has the potential to crash when you repeatedly and programmatically change the mouse cursor. |
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).
| ID | Description |
| 512714 | LabVIEW built .NET assemblies do not marshall some clusters correctly on 64-bit platforms. |
| 576778 | VIs configured as shared clones that are included in a PPL are displayed incorrectly as private VIs when using Desktop Execution Trace Toolkit. |
| 478590 | In some scenarios, dynamically loading LabVIEW classes with ancestors requiring compilation 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.
| ID | Description |
| 578899 | 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. |
Note: In order to apply the change for CAR 578899 you need to recompile affected code.
This can be accomplished by force recompiling the affected VI hierarchy: <Ctrl+Shift> + Run Button.
Issues Fixed in LabVIEW 2014 SP1 f5
| ID | Description |
| 563825 | 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. |
| 564219 | Sometimes if RFmx continuously modifies the loading state of the UI thread a race condition can occur and potentially cause a crash. |
| 552345 | 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
| ID | Description |
| 530158 | In a specific case, the Array Max & Min primitive will output the minimum value from the Max Value output. |
| 532975 | 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. |
| 526540 | In specific cases, TestStand will receive error -18005 when passing a NULL pointer to LabVIEW. |
| 526044 | On subsequent calls, VISA resource and DAQmx resource controls retain their original value when called using a COM interface, such as TestStand. |
| 495612 | 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. |
| 525308 | 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
| ID | Description |
| 515530 | VeriStand 2014 can crash when closing the project after changing the system definition. |
| 516999 | Under certain conditions, running VISA Session Monitor can cause LabVIEW to crash. |
| 516679 | In certain cases the Array Max&Min primitive can cause LabVIEW to crash. |
| 497256 | 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. |
| 511299 | 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. |
| 519665 | LabVIEW can sometimes handle high priority user events incorrectly causing LabVIEW to crash. |
| 408025 | LabVIEW has the potential to crash if there are more than 256 simultaneous event queues active at one time. |
| 515844 | Using the Class Browser to select a class, which contains an accessor method via a property node, can cause LabVIEW to crash. |
Related Links:
Drivers and Updates: LabVIEW Patches