RB Newbie
8th August 2011, 09:03
I've had a couple of other reports similar to yours. I even saw it once myself. Somehow the exact same process uses ridiculous amount of memory, but when stopped and restarted it doesn't. I haven't been able to put my finger on the when-where-why-and-how of it because it is very rare and is unpredictable. Since it is highly unlikely that the same app would act differently on the same source with the same settings, I suspect it is a Windows 7 issue (likely related to disc caching).
I've been seeing the memory used steadily increase on most of my encodes lately. It happens after the audio/video stream extractions when X264 starts. Aborting the run and restarting it without quitting BD-Rebuilder fixes it every time I've seen it. Using LAVF and doing BD-5, 2 pass, highest quality, movie only, on every disc I buy and BD25 on the ones where the movie only won''t fit. Win 7 Pro x64.
It looks like this. Constant memory usage during demux, then sharp increase when x264 starts followed by a slow steady increase as x264 runs. Sharp drop when the run is aborted, increase as x264 starts again and steady as it runs.
I've been seeing the memory used steadily increase on most of my encodes lately. It happens after the audio/video stream extractions when X264 starts. Aborting the run and restarting it without quitting BD-Rebuilder fixes it every time I've seen it. Using LAVF and doing BD-5, 2 pass, highest quality, movie only, on every disc I buy and BD25 on the ones where the movie only won''t fit. Win 7 Pro x64.
It looks like this. Constant memory usage during demux, then sharp increase when x264 starts followed by a slow steady increase as x264 runs. Sharp drop when the run is aborted, increase as x264 starts again and steady as it runs.