Archived: LabVIEW 2011 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.

Visión General



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

Refer to the LabVIEW 2011 Service Pack 1 Software Download page (linked below) to download LabVIEW 2011 SP1.

Contents

Bug Fixes

The following items are bugs fixed for LabVIEW 2011 SP1.

ID Fixed Issue
202432 Throw the error with detailed message for the ReserveEPDS function in generated .NET assembly
241971 GenLeaInstruction, mapping null reg, EventData copy err=1 errors when debugging an .exe
288455 Shared variable not updated when changing representation
300856 Unable to use certain smart probes when debugging LabVIEW-built DLLs
304328 Typecasting an empty I/O constant to a numeric array crashes LabVIEW
304531 Red dot not working correctly for variants
305157 LabVIEW crashes when unflattening an empty string to a specific cluster
305220 Solve Linear Equations.vi can return incorrect values on Real-Time
306797 Cannot create indicator/control/constant for refnum data types from XML property and invoke nodes
307318 Crash when merging a change to a class control/indicator
307687 Error 1012 merging VIs from command line
308464 LabVIEW cannot build some large applications because it fills the image table
308503 Marking VIs as NOT source only will crash LabVIEW unless panels/diagrams are force loaded first
309233 LabVIEW 2011 crashes when doing a cut and paste of a system checkbox
309834 Access violation (0xC0000005) at EIP=0x00764624
310077 Variable browse dialog doesn't show any deployed IOVs
310513 LabVIEW can crash when aborting a VI using Asynchronous Call by Reference
310850 Internal error (OxA824222F) on user cancel of VI load
311279 Deploying a web service will fail
311460 Silver XY Graph - palette buttons are wrong color when toggled
312257 Executable build fails and locks the LabVIEW User Interface after finishing
312332 Charts history changed memory usage between LabVIEW 2010 and LabVIEW 2011
313231 LabVIEW Application Builder cannot deploy Mean.vi when setting passwords to the Analysis library
314062 Silver listbox control does not gray disabled item
315103 Execution-time crash with Scan Value.vi
315365 Enum/Ring control in Silver palette results in Generic Error on save
315378 Project loads significantly slow if .lvlps file is present after a build
315726 "Prompt for a comment on save VI" during builds
315878 Internal error (0xF50EFD7B)
316379 Assembly load error 1589 when using '#' in the assembly path
316408 LabVIEW 2011 crashes after running and closing a VI that uses packed library
316606 Strict typedefs containing a Named IO reference refuse to allow their label to be written via scripting.
316641 LabVIEW 2011 does not limit internal warning prints (to the log file)
316909 Custom license agreements are not displayed on LabVIEW-built installers
318426 Callers of items in packed library that are in subitems don't get their links updated properly.
320393 Owner references for controls within a typedef cluster do not match cluster reference
322188 VI Revision History "prompt for comment when a VI is closed" doesn't save comment

 

Glossary of Terms

 

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