LabVIEW 2015 SP1 Patch Details

This document contains information about all patches available for the following LabVIEW products:

  • LabVIEW 2015 SP1 (32-bit and 64-bit) for Windows, OS X, and Linux
  • LabVIEW 2015 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. NI strongly recommends that you install the latest patch to all LabVIEW 2015 SP1 installations. 

Issues Fixed in LabVIEW 2015 SP1 f13

Note: The LabVIEW 2015 SP1 f13 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 NI ADE Installer Fail on Windows XP/Vista and Server 2003?.

IDDescription
715178(Windows) Reduced the overhead for drawing images and text on Windows 10. This was most noticeable when there were many different controls with text and/or images to draw.
715347Reduced the overhead for updating front panel controls with new data from the block diagram. This was most noticeable for applications with a large number of VIs.

 

 

Issue Fixed in LabVIEW 2015 SP1 f12

Note: The LabVIEW 2015 SP1 f12 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 NI ADE Installer Fail on Windows XP/Vista and Server 2003?. The LabVIEW 2015 SP1 f12 patch only applies to Windows.

IDDescription
411408In rare cases, LabVIEW CPU usage can increase after the parent window of a VI is changed.

 

 

Issues Fixed in LabVIEW 2015 SP1 f11

Note: The LabVIEW 2015 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 NI ADE Installer Fail on Windows XP/Vista and Server 2003?.

IDDescription
657155LabVIEW crashes when a large number of hardware references are opened.
681894In rare cases, LabVIEW can crash when accessing the menu bar if a URL is stored in the clipboard.
691392In rare cases, LabVIEW can crash when searching within a VI for text using Find and Replace while VIs are unloaded from memory.

 

 

Issues Fixed in LabVIEW 2015 SP1 f10

Note: The LabVIEW 2015 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 NI ADE Installer Fail on Windows XP/Vista and Server 2003?.

IDDescription
649952In rare cases, LabVIEW can crash while repeatedly unflattening data from a string.
607006On Windows 10 Anniversary Edition (release 1607) with a different application as the current focus, LabVIEW will receive clicks as making LabVIEW the focused window rather than processing the area clicked.
670440When a VI with user events registered leaves memory, there is a potential for the event to still be processed and throw a Null Window error.
635495Menus within the LabVIEW environment may not display correctly on systems with display scaling set to greater than 100%.
670018VIs within an LLB fail to load if the VI's uncompressed size is larger than 4 MB.
544526On macOS, LabVIEW has the potential to crash when you repeatedly and programmatically change the mouse cursor.
578871On non-Windows systems, LabVIEW has the potential to crash when opening network ports in rapid succession.
546555LabVIEW throws error 1025 when creating an override method of a parent class which is locked against editing.
571935Closing a project library containing a class with unsaved changes does not prompt for save.
597858Saving to a network location from Windows 10 can result in "Error 44: Could not move temporary file to destination".

 

 

Issues Fixed in LabVIEW 2015 SP1 f9

Note: The LabVIEW 2015 SP1 f9 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 NI ADE Installer Fail on Windows XP/Vista and Server 2003?.

IDDescription
653897Make LabVIEW more robust when presented with corrupted resource files.

 

 

Issues Fixed in LabVIEW 2015 SP1 f7

IDDescription
611315Queues, 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.
603562Dynamic dispatch VIs with unwired input terminals would crash LabVIEW under specific circumstances.
619333Simultaneous calls of the .NET Object to Variant VI had the potential to crash LabVIEW on Windows.
617154The product description for the LabVIEW 2015 SP1 64-bit Run-Time Engine was not localized for all release languages in the LabVIEW Application Builder.
624957Memory corruption, usually resulting in an immediate crash, can occur when LabVIEW loads a file containing invalid data.

 

 

Issues Fixed in LabVIEW 2015 SP1 f5

IDDescription
576778VIs configured as shared clones that are included in a PPL are displayed incorrectly as private VIs when using Desktop Execution Trace Toolkit.
567875LabVIEW has the potential to crash when using Register Event callbacks within parallel for loops utilizing multiple threads.
581199In rare cases, branching wires before the inputs to the Unflatten From String function will cause the function to throw error 74 at runtime and to not update indicators wired to its outputs.
528063Increased the LabVIEW Image Table capacity in order to minimize Image Table errors.

 

 

Issues Fixed in LabVIEW 2015 SP1 f3

IDDescription
566313Projects utilizing some C-Series modules will fail FPGA compilation during intermediate file generation.
579359In some instances during class loading, a race condition could cause crashes.
567865Destroying a DVR in parallel to accessing it may lead to crashes or hangs.
567877Destroying a user event in parallel to generating the same event can lead to crashes or hangs.

 

 

Issues Fixed in LabVIEW 2015 SP1 f2

Note: The f2 patch is only applicable to the 64-bit version of the LabVIEW 2015 SP1 Development Environment. 

IDDescription
578899LabVIEW 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 2015 SP1 f1

IDDescription
564219Sometimes if RFmx continuously modifies the loading state of the UI thread, a race condition can occur and potentially cause a crash.
571421In certain cases, dynamically calling a VI containing a SubVI can cause a memory leak. The size of the memory leak scales with the size of the SubVI and its dependencies.
573160The German, Chinese, and Japanese LabVIEW registry files have the incorrect LabVIEW version.
564800The LabVIEW 2015 SP1 Readme does not reflect the correct supported operating systems versions.
573195SystemExec.vi allows child processes to inherit TCP handles, at which point the handles will not be released until both the child and parent have closed. 
573539In some cases, DNS name resolution in LabVIEW can block other TCP calls.
569362In cases of extreme load on a TCP server, LabVIEW can miss new connection notifications, causing a timeout.

 

 

Related Links:
Drivers and Updates: LabVIEW 2015 SP1 (32-bit) f13 Patch for Windows
Drivers and Updates: LabVIEW 2015 SP1 (64-bit) f13 Patch for Windows
Drivers and Updates: LabVIEW 2015 SP1 (32-bit) f13 Patch for Linux
Drivers and Updates: LabVIEW 2015 SP1 (64-bit) f13 Patch for Linux
Drivers and Updates: LabVIEW 2015 SP1 f13 Patch for Mac OS X