NOT RESOLVED Memory Issues Cant Edit a Project. Crashes upon startup.

LongIslanderrr wrote on 8/28/2019, 10:52 AM

My account is mpeck22490@gmail.com (had register with a new email because the registration reset was not working for me.

(if an admin can send me the email to retreive my old account it would be appreciated.

Anyway Im trying to get a project setup with 30GB of Gopro Hero 7 Footage shot in 4k60p. Every-time I import the media. Or open the project my computer OR Vegas will crash or completely freeze. Its definitely something memory related that needs to be addressed. The page file usage is a whopping 50 gigs. And my physical memory doesn't go over 2gb of usage. Ive had absolutely ZERO issues with vegas 16 until now (the largest project ive ever tried to import.

Any fixes to get me going? Im willing to upload the entire 30GB of video files if admins need to reproduce crash. is seems to be also related to "hevc_decoder"

PC specs : Core i7 7700K 16GB ram/gtx 1080.

Extra Information
File: C:\Users\Peck\AppData\Local\VEGAS Pro\17.0\fileio_x64.log
File: C:\Users\Peck\AppData\Local\VEGAS Pro\17.0\dx_video_grovel_x64.log
File: C:\Users\Peck\AppData\Local\VEGAS Pro\17.0\svfx_video_grovel_x64.log
File: C:\Users\Peck\AppData\Local\VEGAS Pro\17.0\ocio_x64.log
File: C:\Users\Peck\AppData\Local\VEGAS Pro\17.0\dx_grovel_x64.log
File: C:\Users\Peck\AppData\Local\VEGAS Pro\17.0\gpu_video_x64.log
File: C:\Users\Peck\Documents\Montauk.veg

Problem Description
Application Name: VEGAS Pro
Application Version: Version 17.0 (Build 284)
Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\Program Files\VEGAS\VEGAS Pro 17.0\FileIO Plug-Ins\mxhevcplug\MXVideoAllocator.dll
Fault Address: 0x00007FF922181758
Fault Offset: 0x0000000000001758

Fault Process Details
Process Path: C:\Program Files\VEGAS\VEGAS Pro 17.0\vegas170.exe
Process Version: Version 17.0 (Build 284)
Process Description: VEGAS Pro
Process Image Date: 2019-07-30 (Tue Jul 30) 10:16:54

Comments

j-v wrote on 8/28/2019, 11:26 AM

Did you disable the SO4 Comp. plugin through Internal preferences?

I ask that because with me that plug is used to open those files ( in my case 50p) on little weaker hardware of my laptop from signature.
Not a problem to open a lot of those files at my laptop from signature.

LongIslanderrr wrote on 8/28/2019, 11:27 AM

Just imported the same exact project in Vegas 16 and guess what? No issues. All is back to normal project opening fine.

There is most definitively a big bug with the HEVC plugin or vegas 17.

vkmast wrote on 8/28/2019, 11:37 AM

There's this comment on MXVideoAllocator.dll from a Vegas dev.

LongIslanderrr wrote on 8/28/2019, 11:54 AM

Thanks vkmast. Just changed the setting in that thread and still ran into the same issue with v17. The memory issue is so apparent I have to/had to force restart my machine. It freezes the entire operating system. No issues at all on v16. Id be willing to send my source media on a usb stick to the engineers. All you have to do is drag and drop everything to import window. 😰. Guess ill be on v16 until this gets addressed.

LongIslanderrr wrote on 9/1/2019, 1:02 PM

Bump

j-v wrote on 9/1/2019, 1:29 PM

You don't send need me those files to test, but I have almost the same software you have, look to my signature.
No problem with my HEVC 4K HEVC 50p files from my GOPro 7 which, if needed, I can show you on screencapture file.
I like to know (see) the exact MediaInfo of your trouble file and I will make my own GOPro 7 HEVC files with those settings to prove on both of my hardware with VP7.

redpaw wrote on 9/1/2019, 1:46 PM

@LongIslanderrr is it still happening if you turn off the thumbnails on timeline?

j-v wrote on 9/1/2019, 1:49 PM

@LongIslanderrr

Here is the video loading and playing my GOPro HEVC 4K 50p into VP17, I show you also my taskmanager during and after that import

adis-a3097 wrote on 9/1/2019, 1:55 PM

@michael-p3508

Try deleting FFCache_x64_1033 file in C:\Users\Peck\AppData\Local\VEGAS Pro\17.0 folder.

Sylk wrote on 9/1/2019, 2:37 PM

@LongIslanderrr Perhaps select this option:

Checking the first checkbox you can see on picture also can help.

LongIslanderrr wrote on 9/3/2019, 1:05 AM

@LongIslanderrr Perhaps select this option:

Checking the first checkbox you can see on picture also can help.

Enabling NVDEC was the FIX for me! Thanks. For some reason when intel was selected there was HUGE page file/memory usage that was resulting in my crash. All is back to normal. and my projects are opening super fast now! 😄

Sylk wrote on 9/3/2019, 9:38 AM

@LongIslanderrr

You're welcome. Please "solved" it.

LongIslanderrr wrote on 9/5/2019, 3:05 AM

Well I CAN edit now but when splitting clips I have HUGE hangs that was once again not present in v16. Using Intel QSV in v17 uses massive amounts of page file causing a crash.

Sylk wrote on 9/5/2019, 3:44 AM

Can you able to open "30GB of Gopro Hero 7 Footage shot in 4k60p" in VP16 to compare ?