I was doing a bunch of renderings overnight of a restaurant, and in the morning I found that VW2017 was paused by Mac OS Sierra because of low memory. Looking at the Activity monitor, I saw that it had used up most of the 16GB on my Mac Pro (Late 2013). I upgraded the computer to 64GB so I wouldn't have that problem again.
Last night I was doing a solar animation of a community center and again it paused because of low memory. How could Vectorworks possibly use up 64GB of memory?
I tried doing a smaller animation on my MacBook Pro (15-inch, 2012) with 8GB RAM and the Memory Used topped out around 6 GB without any swapping and stayed that way until it finished. I tried a similar rendering on my Mac Pro and the Activity Monitor Memory Used slowly crept up from 14GB to over 22.3 GB by the end. Even after the animation was finished, the Memory Used didn't go down.
Is this a memory leak? Why would it affect my Mac Pro and not my MacBook Pro? Has anyone else seen this problem?
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.
Question
Sky
I was doing a bunch of renderings overnight of a restaurant, and in the morning I found that VW2017 was paused by Mac OS Sierra because of low memory. Looking at the Activity monitor, I saw that it had used up most of the 16GB on my Mac Pro (Late 2013). I upgraded the computer to 64GB so I wouldn't have that problem again.
Last night I was doing a solar animation of a community center and again it paused because of low memory. How could Vectorworks possibly use up 64GB of memory?
I tried doing a smaller animation on my MacBook Pro (15-inch, 2012) with 8GB RAM and the Memory Used topped out around 6 GB without any swapping and stayed that way until it finished. I tried a similar rendering on my Mac Pro and the Activity Monitor Memory Used slowly crept up from 14GB to over 22.3 GB by the end. Even after the animation was finished, the Memory Used didn't go down.
Is this a memory leak? Why would it affect my Mac Pro and not my MacBook Pro? Has anyone else seen this problem?
Link to comment
6 answers to this question
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.