The following items are the IDs and titles of a subset of issues fixed between LabVIEW 2015 and LabVIEW 2015 SP1. If you have a CAR ID, you can search this list to validate that the issue has been fixed.
Icon transparency of VIs is not maintained when building a Source Distribution
In rare cases, LabVIEW may crash when saving the results of the Compare VI Hierarchies tool when used on a reentrant VI.
Internal warning when saving a VI with a Fixed-Point datatype for LabVIEW 8.2 or earlier
When building a packed project library containing classes, changes in class inheritance would not propagate to calling VIs
LabVIEW applications do not run properly if libgnomeui is present on 32-bit OpenSUSE Linux
Case Structure auto-complete functions incorrectly when used with Enum Controls in LabVIEW 2015
Unregistering and re-registering an event while an event callback VI is running may crash LabVIEW when the callback VI returns
LabVIEW 64-bit crashes when selecting a result from the Search text box on Windows 10
Make Space/Remove Space does not work when Bookmark Manager is open and there is a bookmark in the VI.
Channel Wires are incompatible with Control & Simulation Loop tunnels
LabVIEW executables with ActiveX Server enabled do not have read-only properties
In rare cases, LabVIEW applications that contain a Web Service may crash on exit.
DAbort 0x2CADF6E3 caused by scrolling the mouse wheel within an array
In some cases, LabVIEW 2015 creates a minor internal warning when shrinking diagrams
In some cases, using Sort 1D Array and Array Max & Min or Less Than on a cluster would report incorrect data
Ctrl-A, then Delete does not delete the icon in the Icon Editor in LabVIEW 2015
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
Iteration and Stop terminals can be hidden when removing space even with loop Auto Grow enabled
LabVIEW 2015 leaks memory when copying an empty array of strings into a non-empty array of strings
In rare cases, leaving the Index input of Index Array function retrieves correct data but can cause other math functions to return incorrect results.
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.