BreakPoint
Monthly Bugs, August 2014
Continued from the July 2014 bugs thread
Now that August has arrived, many will make the annual pilgrimage to Austin and the forum will be all quiet!
After that, we will all have a chance to find new bugs in the upcoming LabVIEW version. 🙂
The posting rules are as always:
- Each post here should only contain a brief description of a bug, together with a link to the thread where it is being discussed.
- One post/bug!
- One bug/post!
- No discussion of bugs. All discussions of a bug must take place in the original linked thread.
No bugs in Agust so far? Even with the release of LabVIEW 2014? 😄
OK, here's one. Open the VI LineCapture_v6.vi posted here and press the "Cleanup diagram" button. Poof!!!!
LabVIEW 2014 crashes immediately (discussed here).
(Tried twice and sent the automatic reports, one last night and one this morning.)
Here's the content of lvlog.txt:
####
#Date: Sat, Aug 30, 2014 9:17:37 AM
#OSName: Windows 7 Enterprise Service Pack 1
#OSVers: 6.1
#OSBuild: 7601
#AppName: LabVIEW
#Version: 14.0 32-bit
#AppKind: FDS
#AppModDate: 6/25/2014 12:35 GMT
#LabVIEW Base Address: 0x00400000
InitExecSystem() call to GetCurrProcessNumProcessors() reports: 2 processors
InitExecSystem() call to GetNumProcessors() reports: 2 processors
InitExecSystem() will use: 2 processors
starting LabVIEW Execution System 2 Thread 0 , capacity: 24 at [3492253070.44697240, (09:17:50.446972371 2014:08:30)]
starting LabVIEW Execution System 2 Thread 1 , capacity: 24 at [3492253070.44697240, (09:17:50.446972371 2014:08:30)]
starting LabVIEW Execution System 2 Thread 2 , capacity: 24 at [3492253070.44697240, (09:17:50.446972371 2014:08:30)]
starting LabVIEW Execution System 2 Thread 3 , capacity: 24 at [3492253070.44697240, (09:17:50.446972371 2014:08:30)]
EDIT: tried with LabVIEW 2013SP! and it also crashes immediately after pressing cleanup, but with a little more information in the lvlog.txt (attached).
