LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LabVIEW needs more memory to compile VI - 2009 SP1

I have full LabVIEW SP1 and all modules and drivers installed including IMAQ and it gives the memory full error.
0 Kudos
Message 11 of 27
(2,633 Views)

I have professional LabVIEW 2009 SP1 w/ VDM and VAM and am having this same error.

 

This application has been running for some time flawlessly, just upgraded to SP1 last week and went in to modify this app.  Front panel is broken with the "LabVIEW needs more memory to compile this VI" error.

 

What now....?  I have a deadline of today for a simple fix, and I am getting nowhere trying to copy/recompile/mass-compile/....?


--------------------

"I have made no decision...
My main concern now is to open as many options to the future as I can."
-- from Stephen Baxter's "The Time Ships"
0 Kudos
Message 12 of 27
(2,605 Views)

Update: I was able to open up my project and edit without problems on a non-SP1 machine.

 


--------------------

"I have made no decision...
My main concern now is to open as many options to the future as I can."
-- from Stephen Baxter's "The Time Ships"
0 Kudos
Message 13 of 27
(2,602 Views)

I have two other coworkers now that have encountered this problem on their SP1 machines.  Has there been any word on a workaround, or as an alternative: how do we get SP1 off of our machines once it is installed?

 

We've tried to uninstall/reinstall, but there must be some left behind hooks in the registry, because upon re-installation of LV2009, it will not allow us to install the "fix" packages (claims it is already at SP1 even after uninstall). 

 

Joe


--------------------

"I have made no decision...
My main concern now is to open as many options to the future as I can."
-- from Stephen Baxter's "The Time Ships"
0 Kudos
Message 14 of 27
(2,563 Views)
This was reported to R&D (# 188063) for further investigation.  Is this occurring with more than one VI?  If so, what's in common with all of them?  If possible, could you post one of them?  Some people have seen success by removing and recreating certain parts of their VIs.
Jared S.
Applications Engineering
National Instruments
0 Kudos
Message 15 of 27
(2,543 Views)

I also just started experiencing this issue on 2009 SP1 (Q4).  We've been developing an IMAQ app for 2 months and after the latest addition we got this and can't get rid of it.

 

Jeff Francis

 

0 Kudos
Message 16 of 27
(2,378 Views)

Hi Jeff,

 

Are you seeing this with multiple Vis, or just one?  Would you mind posting the VI to the forums?

Jared S.
Applications Engineering
National Instruments
0 Kudos
Message 17 of 27
(2,330 Views)

Hi Guys,

 

I also had this issue yesterday on my main logging VI of a large system. Just wouldn't run. Checked all Sub Vi's - they were fine.

I had to check out a previous version from Version Control and redo some of the work (wasn't that much). However I am a bit concerned for the future.

Unfortunately i can not post my vi.

 

If there was lots of work to be redone on the VI my next step would have been to open it in Labview 2010 then "Save for previous version". (few legacy issues with 2010 for us so haven't installed it yet else I would have tried already) - Might work, might not, but a suggestion for someone to try.

 

Regards

 

Joe

0 Kudos
Message 18 of 27
(2,321 Views)

We backed out some of the days work and redid it all with success.  It was the Top level VI only and sorry to say I cannot post it.

0 Kudos
Message 19 of 27
(2,309 Views)

Hi Joe,

Perhaps this discussion should move to another forum but... What were your legacy issues w/ 2010.  We're analyzing when it's best to roll up to 2010.

 

Best,

Jeff

0 Kudos
Message 20 of 27
(2,307 Views)