LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LabVIEW tries to start, eats all of system RAM

Hey everybody, I've got a question involving a newly built computer here. I recently installed LabVIEW 2011 64-bit, it's pretty much the only program on this computer besides Microsoft Office and Chrome, and yet whenever I try to open LabVIEW it freezes up the computer. Looking at the Task Manager when I open it, LabVIEW starts up, starts eating RAM, turns to Not Responding once it hits about 1 gig of RAM usage and keeps going. If I don't kill the process it just uses all of the RAM and I pretty much have to reboot, I never get beyond the LabVIEW loading screen. I found some errors in Event Viewer having to do with LabVIEW, but I think they correspond to the hard reboots rather than the initial startup problem (the Event ID is 3299, some 404 error about a nonexistant file in the "ni webserver" directory. The time seems to correspond to hard reboots, though I haven't tested. They don't occur if I close the process before having to reboot.). Anybody have any ideas? My motherboard drivers are up to date near as I can tell, I have 8 gigs of DDR3 1600 ram on a Biostar TA990FXE motherboard, running Windows 7 64-bit SP1.

 

Thanks for any help, I'll try to keep an eye on this and respond when I can.

0 Kudos
Message 1 of 5
(2,737 Views)

This sounds like a bug that was found in the 2012 Beta with specific processors that LabVIEW would just go into an infinate loop and eat up all of the RAM.  If you install the latest patch for 2011 SP1, your problem should be solved.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 2 of 5
(2,735 Views)

@crossrulz wrote:

This sounds like a bug that was found in the 2012 Beta with specific processors that LabVIEW would just go into an infinate loop and eat up all of the RAM.  If you install the latest patch for 2011 SP1, your problem should be solved.


That is a brutal bug!

0 Kudos
Message 3 of 5
(2,731 Views)

Okay, I'll try installing the patch and get back to you, that sounds promising.

0 Kudos
Message 4 of 5
(2,720 Views)

You did nor mention the CPU, but I am guessing a recent AMD chip with bulldozer core.

 

I am posting via phone, but try a search for bulldozer or similar.

0 Kudos
Message 5 of 5
(2,714 Views)