![see how much memory sony vegas pro 13.0 has see how much memory sony vegas pro 13.0 has](https://3.img-dpreview.com/files/p/articles/0942074552/FCPvPP_header.jpeg)
So the problem goes away once the program is terminated. When you exit the program the OS performs a cleanup and reclaims all memory the program was using. Eventually the program will have consumed all the memory. So each time that function is called more memory is taken from the system, and never given back.
#See how much memory sony vegas pro 13.0 has free
A memory leak is when a program doesn't free those temporary buffers. While running, programs often allocate memory (ask the operating system for more) and free it (return that memory to the operating system). An all I-frame codec would eliminate the problem.īut, like I said, it's a long shot that long GOPs is the problem. Even if you use the same file type and codec you could reencode with shorter GOPs. Would me converting to a new file type change that at all? Yes. This is not good - I have a video I need done by tomorrow. I've not had any problems with rendering before - any ideas? I've even tried rendering in various similar and lower quality video formats - nothing seems to work. I have a Dell Cori i5 quad core processor with 6 GB of RAM. I changed the "Dynamic RAM Preview" to 0MB, as suggested, and even tried it at the "Default" setting of 350MB.
![see how much memory sony vegas pro 13.0 has see how much memory sony vegas pro 13.0 has](https://i.ytimg.com/vi/Nbg_Ro9X3P0/maxresdefault.jpg)
Looking at Windows Task Manager, nothing is open that shouldn't be, from what I can tell, and resources of the system certainly aren't being taxed by any stretch. Today I am trying to render a 4.5 minute video, and it is giving me an 'low memory' error, saying, "The system is low on memory." It would occasionally crash, but it wasn't a real problem. It has worked generally pretty well for quite a few months. Bought Sony Vegas 11 Platinum based on the strong recommendations I got at this forum.