Movie Studio 16 (build 142) does not release RAM on exit

PatB wrote on 9/10/2019, 5:56 AM

Anyone else observing the buildup of RAM use after starting / closing Vegas Studio 16 (platinum) ?

Take a project containing 3 GB of HD video media (1920x1080, avc, *.mp4).

TEST

1) Start condition RAM = 30 % (hardware: Intel® Core™ i7-8550U + UHD Graphics 620, Memory 8 GB)

2) Start Vegas Studio 16 and open the project. Exit Vegas Studio 16. RAM increased from 30 % to 40 %. Task manager: 1 background process "Movie studio 16.0 Platinum " taking up 578 MB of memory.

3) Start Vegas Studio 16 and open the project. Exit Vegas Studio 16.RAM increased to 54 %. Task manager: 2 background processes "Movie studio 16.0 platinum" taking up respectively 578 MB + 589 MB.

4) Repeat three more times. RAM increased to 70 %. Task manager: 5 background processes taking up respectively 578 MB + 589 MB + 602 MB + 599 MB + 608 MB.

So, after five times starting / exiting of Studio 16 (and opening a project with media), the RAM usage has increased from 30% to 70%.

 

Comments

Musicvid wrote on 9/10/2019, 8:17 AM

Known issue.

FayFen wrote on 9/10/2019, 8:21 AM

well,

PatB wrote on 9/10/2019, 12:35 PM

Ah, it can be reproduced. Beside ending the background task(s) in Task Manager, is there a work-around to clear the RAM on exit?

Known issue.

Is it known by the development team and will it be addressed? I'm new to the forum and haven't seen any specific bug reporting section.

FayFen wrote on 9/11/2019, 12:48 AM

Strange the developers never came with this tip

TASKKILL /IM MovieStudioPlatinum160.exe /F

simply copy that into a text file, save it on desktop as VMSkill.cmd and run it as administrator. It will kill all that related to VMS

I'm not that smart I just googled.

FayFen wrote on 9/11/2019, 5:06 AM

Pat-Berghe, I wouldn't publish it here if it didn't work for me at least for 3 tries

I'm on win7, if you on 10 than there might be other tweak to this command

FayFen wrote on 9/11/2019, 10:52 AM

And still that "known issue" had to continue on.

robertOZ wrote on 9/12/2019, 9:10 PM

Pat-Berghe, I wouldn't publish it here if it didn't work for me at least for 3 tries

I'm on win7, if you on 10 than there might be other tweak to this command

Does not work for me on Win 7, followed your process exactly, but still remains in Task Manager, have not tried on Win 10 laptop yet

FayFen wrote on 9/13/2019, 12:06 AM

Do you run as administrator? do you run the bat file or the cmd file?

robertOZ wrote on 9/13/2019, 12:51 AM

Ran the .bat file as administrator

FayFen wrote on 9/13/2019, 1:05 AM

this one?

https://www.vegascreativesoftware.info/us/forum/no-more-vms-ram-leak--117115/

is the path correct?

robertOZ wrote on 9/13/2019, 1:19 AM

Yes, highlighted the text and copied to notepad, noted that when opened, the VMS-run.bat opens VMS 16, should it do that, if it is killing the process

Last changed by robertOZ on 9/13/2019, 1:40 AM, changed a total of 1 times.

Inspiron 7567, Intel Kaby-Lake i7-7700HQ, 16Gb DDR4 Ram, Nvidia GTX 1050Ti GDDR5, dual drives 1TB SSD +1 TB internal, HDD, Samsung 28" 3840x2160 UHD 4K LED Monitor

robertOZ wrote on 9/13/2019, 8:20 PM

On the laptop, Win 10, there is no issue, when MSP is closed, the process is also removed from Task Manager

FayFen wrote on 9/13/2019, 11:35 PM

Robert, same with 7. I have no idea what's differ my 7 than yours. (only that you are down under)