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

Comments

Robert Johnston wrote on 5/9/2019, 1:01 PM

Even though you don't see the Vegas process listed in the Task Manager on the Process tab, it may still be running. You also need to check the list of processes in the Task Manager on the Details tab if Vegas isn't listed on the Process tab. Vegas has always taken a long time to clean up memory, and sometimes it never finishes.

bitman wrote on 5/9/2019, 1:08 PM

@bitman - I missed that? Where is that?

@Grazie Eh you are joking right? Uninstall Firefox like you uninstall any program through windows the normal way.

Last changed by bitman on 5/9/2019, 1:10 PM, changed a total of 3 times.

Current system: VP16 (suite) build 424, VP15 (suite) build 416, Magix Video Pro X (VPX11), Corel VS ultimate 2019, a lot of NEWBLUE plugins, Titler Pro 6, Mercalli 4.0, Respeedr, Vasco Da Gamma 12, VASST stuff, Production Assistent pro3, Boris Continuum 2019,...

  • OS: Windows 10 Pro 64, version 1903
  • CPU: der8auer i7-8700K (advanced edition), default speed (no overclock), Cooler: Noctua NH-D15s
  • RAM: G.Skill Trident Z 3200C14 DDR4 64GB, XMP set to profile 1 in BIOS
  • Videocard: NVIDEA RTX 2080Ti (Founders edition), NVIDEA studio drivers
  • Monitor: LG 38 inch ultra-wide (21x9) - yes upgraded from 34 to 38, I can see more tracks now! Resolution: 3840x1600
  • C-drive: Samsung NVMe SSD 2TB 960 pro
  • Data storage: WD gold 6TB + WD Yellow 4TB
  • MOBO: Gigabyte Z370 Aorus Gaming 7
  • PS: Corsair HX1200i, Case: Silverstone fortress 2, shuttlePROv2, Keyboard and mouse: Logitech G910 and G700s (and now Evoluent Vertical Mouse)

Before November 2018: NVIDEA Gibabyte GTX 1080ti

Before November 2017: windows 10 Pro 64, i7-4790k, mem: DDR3 16GB GTX TITAN X (Maxwell)

 

Grazie wrote on 5/9/2019, 1:41 PM

@bitman - Joking? Nope. I was wanting to know where/when you’d asked me to uninstall FF? I do know how to uninstall a Program.

Grazie

PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti

PC 10 64-bit 64gb * Intel® Core™i9 - 3.3GHz * 40Gb NVIDIA  GeForce RTX 2070

Cameras: Canon XF300 + PowerShot SX60HS Bridge

fifonik wrote on 5/9/2019, 6:24 PM

Why FF should be uninstalled? This change nothing. It is just local html file. Many programs these days create logs as html because they are more readable by human as they might have some formatting as headers, bold, tables etc. FF is just default program associated with these files on that system (in my case it would be PaleMoon, on other it might be Google Chrome, IE, Edge etc). If uninstalled, another program will be associated with the file but it change nothing with a way how the the local file is created.

 

P.S. I do not have such issue on Win 10 with VP15.

Last changed by fifonik on 5/9/2019, 6:26 PM, changed a total of 1 times.

Camcorder: Panasonic X920

Desktop: MB: MSI B350M PRO-VDH, CPU: AMD Ryzen 1600, RAM: G'Skill 16 GB DDR4 2400, Graphics card: MSI RX470 4GB, SSD: Samsung 850 EVO SATA 250MB, HDDs: Seagate & Toshiba 2TB, OS: Windows 10 64-bit 1809

NLE: Vegas Pro 11, 12, 13, 15

bitman wrote on 5/10/2019, 3:38 AM

@bitman - Joking? Nope. I was wanting to know where/when you’d asked me to uninstall FF? I do know how to uninstall a Program.

@Grazie I understand your confusion & question now, my fault, I used the word "already" which I suppose implicates I asked something before (which I obviously did not). Sorry, English is not my native language.

@fifonik Well it is just a long shot as Grazie had issues in another post with Vegas files being associated with FF.

Last changed by bitman on 5/10/2019, 3:44 AM, changed a total of 2 times.

Current system: VP16 (suite) build 424, VP15 (suite) build 416, Magix Video Pro X (VPX11), Corel VS ultimate 2019, a lot of NEWBLUE plugins, Titler Pro 6, Mercalli 4.0, Respeedr, Vasco Da Gamma 12, VASST stuff, Production Assistent pro3, Boris Continuum 2019,...

  • OS: Windows 10 Pro 64, version 1903
  • CPU: der8auer i7-8700K (advanced edition), default speed (no overclock), Cooler: Noctua NH-D15s
  • RAM: G.Skill Trident Z 3200C14 DDR4 64GB, XMP set to profile 1 in BIOS
  • Videocard: NVIDEA RTX 2080Ti (Founders edition), NVIDEA studio drivers
  • Monitor: LG 38 inch ultra-wide (21x9) - yes upgraded from 34 to 38, I can see more tracks now! Resolution: 3840x1600
  • C-drive: Samsung NVMe SSD 2TB 960 pro
  • Data storage: WD gold 6TB + WD Yellow 4TB
  • MOBO: Gigabyte Z370 Aorus Gaming 7
  • PS: Corsair HX1200i, Case: Silverstone fortress 2, shuttlePROv2, Keyboard and mouse: Logitech G910 and G700s (and now Evoluent Vertical Mouse)

Before November 2018: NVIDEA Gibabyte GTX 1080ti

Before November 2017: windows 10 Pro 64, i7-4790k, mem: DDR3 16GB GTX TITAN X (Maxwell)

 

gary-rebholz wrote on 5/14/2019, 1:38 PM

Yes, this is a real issue where an unwanted VEGAS process hangs around. It's actually a very old one that we've discovered stretches way back several versions. It mostly affects Win 7, but as Marco reports, it can also happen on Win 10. We're looking into it and hope to fix it in a future update. For now, I'm afraid the workaround is that which has already been discussed: kill the rogue process in Task Manager before attempting an install. Hopefully now that we all know about it, we can help other users here who stumble across it. Thanks for reporting and discussing so that we could find it.

Grazie wrote on 5/14/2019, 1:49 PM

@gary-rebholz - Thanks for the reassurance. I was concerned that my work would NOT be saved with killing the process in TM. What’s odd is that the behaviour had only surfaced after I installed this recent Build. Is that helpful?

Grazie

PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti

PC 10 64-bit 64gb * Intel® Core™i9 - 3.3GHz * 40Gb NVIDIA  GeForce RTX 2070

Cameras: Canon XF300 + PowerShot SX60HS Bridge

OldaC wrote on 5/23/2019, 9:59 AM

Same to me. Vegas still running after exit. (last build)

 

Acky wrote on 5/24/2019, 5:43 AM

Same happening here. Just purchased upgrade to Vegas Pro 16
(I’m on windows 7). When I close Vegas Pro, having opened and closed with
various projects, there are loads of vegas160.exe still running in task
manager. I noticed it because when I tried to eject my audio interface and shut
down my computer, it reported a programme was still running which was using it.
Turned out to be several instances of vegas160.exe still running in the task
manager. So I’m having to force shutdown. Or stop all the vegas160.exe in task
manager manually. Please fix this.

 

Dexcon wrote on 5/24/2019, 6:41 AM

Please fix this.

Acky, please refer to the post 3 above yours … the MAGIX Vegas Pro development team has already advised:

We're looking into it and hope to fix it in a future update

 

Acky wrote on 5/25/2019, 4:27 AM

Thanks Dexcon.

Here's hoping this gets sorted out.

karma17 wrote on 5/25/2019, 1:02 PM

Are you mixing metaphors? I don't think Vegas has a smell. If it did, I assume it would smell like coffee.

OldaC wrote on 5/31/2019, 1:40 AM

Please fix this bug, it is really annoying! Amount of my RAM is limited. :(

Grazie wrote on 5/31/2019, 2:02 AM

@OldaC - Yes . . Just had it again whilst working hard on a Tutorial. I had to again kill VegasPro in WTM. It gobbles RAM and leaves me unsure and queasy about what damage is being done to my work. And again, for me this ONLY appeared in the latest Build, along with that FireFox HTML taking up residence in my TEMP folder.

Grazie

PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti

PC 10 64-bit 64gb * Intel® Core™i9 - 3.3GHz * 40Gb NVIDIA  GeForce RTX 2070

Cameras: Canon XF300 + PowerShot SX60HS Bridge

Musicvid wrote on 5/31/2019, 7:02 AM

@Grazie

Your theory. (other thread) makes perfect sense to me.

My version is 14, and about the same as VP8 in the memory dept (kind of acceptable). I don't have much RAM, so my save-restart-render ritual has been the same for seventeen years. Back then, I was convinced that buffer overflow was the problem, owing to the nature of the freezes and blue screens (then on Win98SE and Vista 32).

So yes, our minds our running parallel. Again. And Autosave behavior in newest build may have reintroduced poor buffer regulation. The nature of all the inconsequential things that go into buffer memory may warrant a fresh look, too.

OldaC wrote on 6/12/2019, 3:21 AM

Please, fix this bug.

OldaC wrote on 7/2/2019, 1:48 PM

Please, any news about this issue??? It is really boring to killing Vegas processes. :(
Thank you very much!

Marco. wrote on 7/2/2019, 2:12 PM

See -> here.

Grazie wrote on 7/2/2019, 4:00 PM

I'm using WAAG's Vegas "Save 'n Kill" Tool working well.

Grazie

PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti

PC 10 64-bit 64gb * Intel® Core™i9 - 3.3GHz * 40Gb NVIDIA  GeForce RTX 2070

Cameras: Canon XF300 + PowerShot SX60HS Bridge