New
#11
The Performance tab is of greatest importance. A process listing is of only minor interest.
ok I finally finished my next project to render, and this is what happened in task manager
had to "empty system working sets" with rammap again toclear 4 GB of phantom RAM (in use)
below is a screenshot of the requested task manager tab when the phantom ussage happened
I see that the commit limit is 7673 MB with 7658 MB RAM. The commit limit is RAM size plus pagefile size minus a small overhead. This tells me that the pagefile is very small, too small to be of any real benefit. This will impair the system in making optimum use of your RAM.
I would suggest setting the pagefile to system managed.
Edit: In a 64 bit OS the file cache can be a major contributor to memory usage. I suspect that is the case here. Nothing in Task Manager or Resource Monitor will tell you about this. This memory is not included in what is labeled "Cached".
I rarely use it, unless I am doing small, high speed captures. when I have it open, which is never used in conjunction with sony vegas open, it is 512MB, if set it to 1.4 gigs or higher, the system proceeds to consume 8 GB of RAM.
though my main issue is being unable to export video edits due to system working set eating up all the ram and crashing sony vegas when the ram gets full
I should add that this ram issue also happens in safe mode under the same condition (rendering a video in sony vegas)
EDIT: I am really confused now it isnt flooding RAM now, it was also alternating between flooding ram and not a few weeks ago back in early july, it would flood ram, then late july through early august, it would behave, then recently it flooded ram again and even in safe mode, now its not. rebooting also doesn't fix the flooding
EDIT2: and its doing it again =(
EDIT 3:
OK I believe i traced the problem to something unsolvable,
I have observed that the system working set on behalf of sony vegas during random project renders (on a project to project basis (carries over veg saved projects)) steadily climbs in usage at a consistent rate until the ram fills up and crashes the computer
additionally, the faster the render is able to go, the faster this RAM consumption climb spikes
example: if I use CPU rendering, the rate the frames process is about 5FPS and the RAM reaches 100% in about 10 minutes, vegas crashes (with its own crash screen) or system blue screens
if i use GPU rendering on the same project, it processes at a rate at which the frame renders process is 40 FPS, and the ram reaches 100% in under a minute, vegas crashes (with its own crash screen) or system blue screens
If I render at 480p when the source clips are MPEG4, the ram spike happens too slowly to crash the render or computer (or isnt happening at all) i don't notice here
source files in the render it's happening with is AVI which fraps created during a PC game capture source AND output render is 720p using AVC MP4 4MBPS
the issue with RAMDisk is when the "disk size" for the ramdisk is set above 1GB, shuting down the ramdisk drive (ejecting it in the process) does NOT lower ram usage and a reboot is required to purge it in this case
isn't this a memory leak? and how do I fix this?
that's about all the info about the abnormal ram usage issues I can dig up from my system
Last edited by Diddy7Kong; 20 Sep 2014 at 04:50.
ok so thanks guys for helpign me with tips, I managed to figure out exactly how the ram issue is happening when i tried to mass convert and combine the source clips into one MP4 and the fraps codec threw a memory map attempt failure error claiming insufficient memory, so I converted everything one by one into MP4s and vegas didn't leak memory.
issue was encoder using fraps decoder demanded more than 32GB of memory, not releasing memory or reusing memory when parts were no longer needed
ROOT: AVI files compressed with fraps video codec