Christiaan Posted September 21, 2012 Share Posted September 21, 2012 (edited) How do I avoid this so-called BIM application from continually spewing its brains out with the message: "One or more operations were aborted due to lack of memory"? I've never thought I'd say this but I'm starting to miss 2D. Edited September 21, 2012 by Christiaan Quote Link to comment
Dieter @ DWorks Posted September 21, 2012 Share Posted September 21, 2012 VW still haven't solved the problem that it doesn't release memory, so the longer you have VW on, the less memory you have. Therefore, you best restart VW several times a day. I know it's sad. This is a bug that is really aged. Quote Link to comment
Christiaan Posted September 21, 2012 Author Share Posted September 21, 2012 With the current file I'm working on it does this with every save, despite quitting and restarting VW each time in between. Feels like I'm flogging a dead horse. Quote Link to comment
Christiaan Posted September 21, 2012 Author Share Posted September 21, 2012 Strange workaround: do a Save as Copy before a normal save. Quote Link to comment
Tobias Posted September 28, 2012 Share Posted September 28, 2012 This is been showing up for me lately, typical when doing an interior render w/ a viewport linked to a camera. I am a little light on RAM. Will that solve it? VW 2012 SP 5 Mac OSX 10.6.8 MacPro 2x2.8 quad Core 6 GB RAM Quote Link to comment
Tom Klaber Posted October 1, 2012 Share Posted October 1, 2012 Because VWs is a 32 bit program, it is not entirely clear that adding more RAM will do you any good. Quote Link to comment
megan Posted October 2, 2012 Share Posted October 2, 2012 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 Quote Link to comment
Tom Klaber Posted October 2, 2012 Share Posted October 2, 2012 That is good to know, unfortunately, drafting is more RAM intensive (I like to keep 12 files open at once) and renderings is more processer intensive. This has long been an issue and we must assume that VWs is frantically pouring all of its resources into fixing this flaw. Quote Link to comment
steve s Posted January 31, 2013 Share Posted January 31, 2013 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..... Quote Link to comment
Kevin McAllister Posted January 31, 2013 Share Posted January 31, 2013 Quit Vectorworks and restart. I often see this when rendering complex sheet layer viewports or rendering many viewports in a row. You can save the file before quitting by choosing save as. It may give you an error while saving but in my experience the file actually saves fine. Clearly there is some sort of memory leak happening when rendering. Kevin Quote Link to comment
VincentCuclair Posted January 31, 2013 Share Posted January 31, 2013 Yeah, I've been experiencing this frequently too! Must be a bug. Quote Link to comment
Dieter @ DWorks Posted January 31, 2013 Share Posted January 31, 2013 This one is a long time thing with VW. It's in it for as long as I can remember, even before version 12.5! The thing is that VW uses memory, but doesn't release everything, so when time passes VW have less and less memory to operate. Only quitting VW releases all the memory. So restarting VW from time to time can solve this. Quote Link to comment
steve s Posted January 31, 2013 Share Posted January 31, 2013 Good to know thanks for the tip Quote Link to comment
VincentCuclair Posted February 1, 2013 Share Posted February 1, 2013 (edited) 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 February 1, 2013 by Vincent C Quote Link to comment
Dieter @ DWorks Posted February 1, 2013 Share Posted February 1, 2013 This bug is in all versions, perhaps worser in others. For example in VW2012: When I work on our library and need to open and close a lot of dialogs like wall styles, class attributes etc... VW has this problem in the hour! Quote Link to comment
DianaK Posted August 14, 2014 Share Posted August 14, 2014 (edited) Still an issue, as a test I restarted VWX and built an extruded hexagon, tried to export an animation revolving around it, super simple, and even now got that same error. OSX 10.9.4 16GB memory 1600 MHz, VWX2014 SP4! Edited August 14, 2014 by dianak Quote Link to comment
archistudent1 Posted January 18, 2017 Share Posted January 18, 2017 Also having this issue on a really small file. I have tried restarting my computer but the problem is not resolved. Anyone found a workaround? Quote Link to comment
Tom Klaber Posted January 18, 2017 Share Posted January 18, 2017 8 hours ago, archistudent1 said: Also having this issue on a really small file. I have tried restarting my computer but the problem is not resolved. Anyone found a workaround? What are your computer specs? Quote Link to comment
Vectorworks, Inc Employee PVA - Admin Posted January 18, 2017 Vectorworks, Inc Employee Share Posted January 18, 2017 8 hours ago, archistudent1 said: Also having this issue on a really small file. I have tried restarting my computer but the problem is not resolved. Anyone found a workaround? And, what version of Vectorworks are you using? Quote Link to comment
Chris Brough Posted February 3, 2017 Share Posted February 3, 2017 (edited) i'm on vectorworks 2016 sp6 and having this error on some very simple viewport updates. Simply cant use VW for 3d if there's no simple fix... more info, viewports are high quality OpenGL colored but not textured. Edited February 3, 2017 by Chris Brough Quote Link to comment
Stéphane Posted January 20, 2023 Share Posted January 20, 2023 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. Quote Link to comment
line-weight Posted January 20, 2023 Share Posted January 20, 2023 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. Quote Link to comment
Recommended Posts
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.