Jump to content

One or more operations were aborted due to lack of memory


Recommended Posts

Because VWs is a 32 bit program, it is not entirely clear that adding more RAM will do you any good.

According to post quoted below, CineRender is a separate, 64-bit multicore app running in parallel to VW. Presumably, that means it's running in its own memory space and can address as much RAM as is available. That suggests that RW operations would benefit from more RAM, though VW itself is still limited to 2.5 (REALLY? STILL? What's up with THAT?) Gb.

Vectorworks 2012 is still a 32-bit app, but can be run on 64-bit stations/operating systems. Vectorworks will only address a max of 2.5 GB of RAM.

Renderworks/CineRender 2012 (and 2011) is a 64-bit, multi-core application. It is essentially Cinema4D "Lite". When you render a scene with any of the Renderworks modes, the CineRender app runs in the background, parallel to Vectorworks. CineRender will address as much RAM as it needs, but it takes advantage of CPU power over RAM.

So more cores, faster processor is better. More RAM helps if you have multiple apps running at one time....


Jeffrey W. Ouellette, Assoc. AIA

Architect Product Specialist

Global Product Marketing, Nemetschek Vectorworks, Inc.

MacBook Pro 17" (2009) 2.8 GHz Intel Core 2 Duo, 8GB RAM, OS10.6.8

-- source: Renderworks 2011 or 2012, iMacs, memory, and 64-bit addressing
Link to comment
  • 3 months later...

I am getting this message now!! but have 19 Gb of free ram (32 total). iMac i7 2012??

Very disappointing this is happening - not an overly complex model either, seems to happen after repeated renderings with Bitmap tool.

Now I can t save my file, I have auto save every ten minutes-so no biggy but for 3000$ for Landmark.....

Link to comment

This is definitely a v2013 bug, didn't happen in v2012 on the same computer, same size files.......i have other indications too that it is 'memory happy', residue of closed dialogs remaining on screen, OpenGL orbit views sticking (resettable by panning only) etc. definitely a 2013 issue I think.

Just did a restart because I felt a warning was pending......

Edited by Vincent C
Link to comment
  • 1 year later...
  • 2 years later...
  • 3 weeks later...
  • 5 years later...
26 minutes ago, Stéphane said:

Still an issue in VW 2021. VW doesn't release memory after an openGL rendering. I have to save&restart after 10 pretty basic renderings. 

Discussed in this thread:


I didn't know this was such an old problem - been going on at least 10 years going by when this thread was started.


I've not yet tested whether there's an improvement in VW2023.


Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...