Can not save due to lack of memory.

[Tom Klaber]

I do not understand why this happens. I have 350GB of free disk space - so it is not that kind of memory - and I have 16GB of Ram - so I should I have plenty of that type - what is VW talking about? What can I do to avoid the problem?

I think it is time that VW hopped on the 64bit train.

[bcd]

I had this yesterday - I believe this issue is the description.

From what I can tell, if you move or rename an open file then VW doesn't know where or what it is.

The solution is to Save As and browse to the correct location.

[Tom Klaber]

Thanks but the file was not moved. Both "Save" and "Save As" were met with the same error: "Action can not be preformed due to lack of memory." I do not think it was a path issue.

[Kevin McAllister]

I had this happen twice yesterday. Both times, the problem continued when I chose "Save As" yet the file still saved even though I was given the warning. After each occurrence I restarted my machine and found a Vectorworks temp file in the folder along with the original file. Upon deleting that, things returned back to normal.

I have seen this happen before but usually when the original file is moved or changed as bcd mentions. In my case, nothing was moved or changed, which makes me think this may be something different entirely....

Kevin

[Tom Klaber]

I, too, found that though the warning dialog appeared, it was actually saving a file - PHEW!. I smells of a RAM issue to me. I have seen similar issues when dealing with large photoshop files.

[Tom Klaber]

I am now getting this problem once a day at least. Is this a file size issue?

[CipesDesign]

I assume you have tried a full shutdown/restart??

[Tom Klaber]

That is what I have to do. The problem then re-surfaces at some later point.

[bcd]

Is File>Document Settings>Document Preferences>Save Viewport Cache checked?

[Tom Klaber]

No it was not checked.

I was unaware of that option.

[bcd]

This problem is recurring here too.

Batch Export>PDF successfully creates a PDF with out of date Viewport Annotations!!!, missing viewports, and old data.

Clearly the Viewport Cache isn't being overwritten.

Please NV, fix this one asap.

[Joe-SA]

We've been having the lack of memory issue ever since we started generating building section and elevation viewports from our model. We've also been experiencing some lag in the screen display regeneration. I think this is a combined problem with Vectorworks memory management and your hardware.

After extensive discussions with our IT consultants our current theory is that its the amount of dedicated RAM on the graphics card. Even though my iMAC has a 3.06GHz processor and 12GB of RAM and 500GB harddrive....it only has 256MB of dedicated RAM on the graphics card and unlike macmini's the iMAC graphics card doesn't have the ability to share the system RAM so 8GB vs 12GB of RAM makes no difference.

New smaller iMACs only have a base graphics card and 512MB of RAM and can't be upgraded. We didn't think that was enough. The 27" iMACs can get an upgraded graphics card and you can increase the dedicated RAM. We just ordered a couple of these that have the upgraded cards increased to 2GB of RAM. This will be 8x the graphics card processing power of my current machine.

To say the least, we are hoping these upgrades solve the problem.

Joe

Edited April 4, 2013 by Joe-SA

[M5d]

I have the newest iMac with a GTX 680MX (2Gb RAM) and get these errors every couple of renders once the model is detailed. I also bumped the RAM to 16Gb with this purchase in hope of mitigating the problem but it's made no difference from my previous machine. The solution is to close and reopen Vectorworks after renders.