Vegas Remains In Memory? Like a Bad Smell....

harry-worth wrote on 5/6/2019, 2:49 AM

Hi Grazie. I am running Win10 v 1803 and Magix Vegas v 424. When I close Vegas it disappears from the task manager. Tried it a few time and it work ok on my system.

Marco. wrote on 5/6/2019, 2:51 AM

What's your graphic system? Intel HD Graphics 5xx/6xx?

Grazie wrote on 5/6/2019, 3:36 AM

What's your graphic system? Intel HD Graphics 5xx/6xx?

@Marco. - All in my Signature. Is there something I'm missing you'd need further info on? - Anyway, Marco, worked prior to this Build.

Anton-Kovalenko wrote on 5/6/2019, 6:12 AM

I have the same problem!

Vegas (Update 5, build 424) keeps a new copy in RAM after every launch and exit.

Win 7. GeForce GTX 680. 32GB RAM.

Grazie wrote on 5/6/2019, 6:34 AM

I have the same problem!

@Anton-Kovalenko - Thanks for the confirmation. Had you noticed this any previous builds?

Marco. wrote on 5/6/2019, 6:43 AM

I have this since a long time but it only happens when I used certain type of media in a project.

Anton-Kovalenko wrote on 5/6/2019, 7:02 AM

I have the same problem!

@Anton-Kovalenko - Thanks for the confirmation. Had you noticed this any previous builds?

I have it for the first time.
Yesterday I reset the Vegas settings (Ctrl+Shift+Start Vegas). Problem disappeared!

Today, working with the project, I have slightly adjusted the interface (buttons, etc.).
The problem appeared again.

?????

This does not really interfere with work, only the computer turns off much slower.

Media Format: XAVC S 4K. (Sony a6500). Native for Vegas!

I launched and closed Vegas several times without opening any project (and media). Every time waited a few minutes. (Vegas always unloades from RAM slowly.) All instances remained in RAM.

Bug or feature?

lan-mLMC wrote on 5/6/2019, 7:04 AM

In Win7, It does this

Dexcon wrote on 5/6/2019, 7:21 AM

VP16 b424 - W10 up-to-date - AMD RX470

VP removes from Task Manager after closing VP.

Grazie wrote on 5/6/2019, 8:39 AM

@lan-mLMC & @Dexcon Not here. Just closed a 4.6gb and after reducing size to 250mb it still remains. I have to kill it manually.

Marco. wrote on 5/6/2019, 8:42 AM

While one (or several) VP processes remaining in the Task Manager, are you able to start a new session of VP? This does not work here and for me this is the main annoyance with it. Before I can start a new session of VP I first have to kill the remaining process in the Task Manager. And using a CMD batch file to kill that process does not work, unfortunately.

Eagle Six wrote on 5/6/2019, 8:54 AM

Closes for me as far as I have checked

Grazie wrote on 5/6/2019, 8:58 AM

While one (or several) VP processes remaining in the Task Manager, are you able to start a new session of VP?

Yes.

This does not work here and for me this is the main annoyance with it. Before I can start a new session of VP I first have to kill the remaining process in the Task Manager.

I’m guessing that I could open more and more until my memory got constipated and crashed.

And using a CMD batch file to kill that process does not work, unfortunately.

So you’ve lived with these nonsenses, for how long?

rraud wrote on 5/6/2019, 9:12 AM

"VP removes from Task Manager after closing VP."

Same here, Win 10, 32GB RAM, NVIDIA Geforce 960M.

Grazie wrote on 5/6/2019, 9:14 AM

While one (or several) VP processes remaining in the Task Manager, are you able to start a new session of VP?

@Marco. Here's the sorry tale:

That's SIX, not going away. MAGIX?!

G

Marco. wrote on 5/6/2019, 9:27 AM

"So you’ve lived with these nonsenses, for how long?"

Don't know exactly, maybe a year. I think on my system this happened with one of the Intel driver updates. But it only happens with certain types of H.264 media, though I never found out which particular H.264 property causes the issue.

j-v wrote on 5/6/2019, 10:04 AM

I managed to found a solution on my laptop (the only place it happened for a long time) to start the program not with the Nvidia GPU but with the Intel 630 GPU or switch to the last available updates for my Nvidia provided by Asus (driver version 399.24) and than I can start and stop again normal without any hangs of the program in memory.

Musicvid wrote on 5/6/2019, 1:53 PM

I tested this when I saw it in VP8, and found out that operator patience may be a factor. Lingering processes and sequestered memory went away after several minutes.

Although I haven't tested in VP14, I haven't had an issue, because I habitually reboot my system between saving and rendering my project.

D7K wrote on 5/6/2019, 2:52 PM

VP removes from Task Manager after closing VP."

Same here, Windows 10 PRO, Intel i7700 4300, AMD 480 8 gig, V424 Vegas

bitman wrote on 5/7/2019, 2:00 AM

VP is removed from the taskmanager. Windows 10 latest build. Looking at the posters signatures (where available), it seems that the issue as far as I can tell from the posters is limited to windows 7...

Grazie wrote on 5/7/2019, 2:25 AM

Looking at the posters signatures (where available), it seems that the issue as far as I can tell from the posters is limited to windows 7...

@bitman - Yup! Thanks confirming what I’ve been thinking. This Build and only this Build is doing this. The last Build was rock solid. Somebody from MAGIX needs to confirm or deny if the installer was Q&A for Windows 7 too. If it hasn’t been or that MAGIX is no longer supporting Windows 7 then we’d need to know.

@bitman - Thanks again.

Marco. wrote on 5/7/2019, 3:24 AM

It's Windows 10 here.

Grazie wrote on 5/7/2019, 3:32 AM

@Marco_Polo - So you’re running Windows 10 AND you’re still getting residual VegasPro in Task Manager. Huh.... All that’s left is the installer.

Marco. wrote on 5/7/2019, 3:46 AM

Yes, it's been Windows 10 all the time I had/have this issue appearing. In my case it is very likely the Intel graphic driver causing the issue which is why I asked if you also use a Intel graphic system. So it seems there are similar problems triggered by different causes.