BandA Posted November 8, 2007 Share Posted November 8, 2007 I am on os 10.5 and vw2008 sp1 and i am finding that while rendering a relatively simple viewport in hidden line rendering (one which rendered in 12.5.2 and vw2008 on os 10.4.10 ok) the active memory usage shoots through the roof (up toward 2 gig) and then vw punts me out of the application saying 'insufficient memory to complete task' or something similar. i am also finding that the longer i use vw2008 sp1 during a given session, the amount of active memory usage inches up toward 2 gig which never happened in os 10.4.10. i am on a macbook pro, 2.33 c2d, 3g ram, osx 10.5 anyone else had similar experiences? Quote Link to comment
BandA Posted November 8, 2007 Author Share Posted November 8, 2007 it appears that the only rendering mode i could find this in is 'hidden line'. this is a fairly crucial part of my work flow and i am dead in the water without hidden line viewports. has anyone had the same problems? has nna found these problems as well? Quote Link to comment
BandA Posted November 8, 2007 Author Share Posted November 8, 2007 though, to keep adding to my rambling thoughts, i've also noticed that vw2008 takes up a LOT of memory in leopard. anyone else found the same? Quote Link to comment
Guest Posted November 9, 2007 Share Posted November 9, 2007 Can you please send all this info to bugsubmit@nemetschek.net? If you have a sample file you would like to provide, that would be extremely helpful. Quote Link to comment
Guest Posted November 9, 2007 Share Posted November 9, 2007 PS - you may want to update your signature and change VW !2 to VW 2008 Quote Link to comment
BandA Posted November 10, 2007 Author Share Posted November 10, 2007 i'll send the info in a sec. what if my sample file is large (~150 mg)? do you have a server i can upload to? i can't really attach that to a email. Quote Link to comment
Guest Posted November 10, 2007 Share Posted November 10, 2007 Stuff it to see if you can get it down to 100 mb. If you can, send the file using yousendit.com If you can't, send me an email and I'll reply with FTP information. Quote Link to comment
islandmon Posted November 11, 2007 Share Posted November 11, 2007 Before sending a huge possibly sensitive client file... why not first try send off a simple Console Log report or use one of the Developer tools to punch-out the memory issues and report them ? Tech can tell which procedure to use to best meet their needs . ~/Developer/Applications/Performance Tools/ Quote Link to comment
BandA Posted November 12, 2007 Author Share Posted November 12, 2007 i was not aware of such tools. i will ask tech support Quote Link to comment
Guest Posted November 12, 2007 Share Posted November 12, 2007 Go ahead and send the file. We want to look at the actual file. Quote Link to comment
Vectorworks, Inc Employee Andrew Bell@NV Posted November 13, 2007 Vectorworks, Inc Employee Share Posted November 13, 2007 There is an active bug for this issue, so we have several files we're already looking into. The odds are good the cause of problems with those files is the same as with your file. So if you haven't sent it in already and would find it difficult, you may want to hold off. Quote Link to comment
BandA Posted November 13, 2007 Author Share Posted November 13, 2007 Thanks Andrew. I did send the file already, so hopefully it will help. For what it's worth, most rendering modes seems to have trouble to a certain extent, but the one that had the most problem was Hidden Line. This is especially the case when cutting Section Viewports. Quote Link to comment
Sky Posted July 28, 2008 Share Posted July 28, 2008 I am having the same problem doing an animation in hidden line rendering. Has this memory problem been solved yet? Quote Link to comment
gmm18 Posted July 28, 2008 Share Posted July 28, 2008 Be sure you have installed the latest service pack: http://www.nemetschek.net/downloads/fundamentals/2008/2008SP3.php Quote Link to comment
RonMan Posted July 28, 2008 Share Posted July 28, 2008 This problem has been driving me crazy for some time. With the amount of memory that I have (10 GB) it is very frustrating when an application says it is out of memory. The memory leaks in VW2008 are very serious. Memory grows every time you render something and is not fully released. After a while VW either crashes or you get messages that indicate that you have run out of memory, or you see nothing until you look at your console log and VW is trying to fill up your disk with messages like this: 6/21/08 3:29:07 AM VectorWorks[541] VectorWorks(541,0xf42ce000) malloc: *** mmap(size=27840512) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug 6/21/08 3:29:07 AM VectorWorks[541] VectorWorks(541,0xf4350000) malloc: *** mmap(size=27840512) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug 6/21/08 3:29:07 AM VectorWorks[541] VectorWorks(541,0xf43d2000) malloc: *** mmap(size=27840512) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug 6/21/08 3:29:07 AM [0x0-0x5f05f].net.nemetschek.vectorworks[541] VectorWorks(541,0xf42ce000) malloc: *** mmap(size=27840512) failed (error code=12) 6/21/08 3:29:07 AM [0x0-0x5f05f].net.nemetschek.vectorworks[541] *** error: can't allocate region 6/21/08 3:29:07 AM [0x0-0x5f05f].net.nemetschek.vectorworks[541] *** set a breakpoint in malloc_error_break to debug 6/21/08 3:29:07 AM [0x0-0x5f05f].net.nemetschek.vectorworks[541] VectorWorks(541,0xf4350000) malloc: *** mmap(size=27840512) failed (error code=12) 6/21/08 3:29:07 AM [0x0-0x5f05f].net.nemetschek.vectorworks[541] *** error: can't allocate region 6/21/08 3:29:07 AM [0x0-0x5f05f].net.nemetschek.vectorworks[541] *** set a breakpoint in malloc_error_break to debug 6/21/08 3:29:07 AM [0x0-0x5f05f].net.nemetschek.vectorworks[541] VectorWorks(541,0xf43d2000) malloc: *** mmap(size=27840512) failed (error code=12) 6/21/08 3:29:07 AM [0x0-0x5f05f].net.nemetschek.vectorworks[541] *** error: can't allocate region 6/21/08 3:29:07 AM [0x0-0x5f05f].net.nemetschek.vectorworks[541] *** set a breakpoint in malloc_error_break to debug 6/21/08 3:32:01 AM com.apple.launchd[138] ([0x0-0x5f05f].net.nemetschek.vectorworks[541]) Exited: Terminated I had to kill it (the last line). My workflow is totally messed up. I have to monitor memory whenever I am updating viewports and quit and restart as soon as memory usage gets to about 1.5 GB (sometimes lower). I have submitted a bug report, and except for the comment above, I have never heard anything about this from NNA. Love the program, hate this problem. RonMan Quote Link to comment
Sky Posted August 15, 2008 Share Posted August 15, 2008 I upgraded to SP3 but that didn't help. So I guess this problem has not been solved yet? *sigh* 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.