Try transcoding a raw file to a compressed x264.<div>If the file is 20 to 3 times the size of your ram it will run out of memory.</div><div>Can't we put a limit on how much memory x264 can use?</div><div><br></div><div>
I'll screen capture this if it helps so you know what I am talking about.<br><br><div class="gmail_quote">On Tue, Jul 6, 2010 at 7:20 AM, Loren Merritt <span dir="ltr"><<a href="mailto:lorenm@u.washington.edu">lorenm@u.washington.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On Tue, 6 Jul 2010, Tomek Lenik wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
It transcode really slowly as its building up ram (like 2-5% cup usage)<br>
until it gets to be 1 or 2 gb of ram then it spikes to 70% cpu usage and<br>
then it runs out of memory.<br>
</blockquote>
<br>
What OS do you have installed? Is it Windows? Is your x264 build 32-bit?<br>
<br>
Loren, does x264 map files in memory?<br>
</blockquote>
<br></div>
No, and even if it did that wouldn't require more physical memory than any other method of file I/O.<br>
<br>
I have no idea what Dylan screwed up to trigger his symptoms.<br><font color="#888888">
<br>
--Loren Merritt</font><div><div></div><div class="h5"><br>
_______________________________________________<br>
x264-devel mailing list<br>
<a href="mailto:x264-devel@videolan.org" target="_blank">x264-devel@videolan.org</a><br>
<a href="http://mailman.videolan.org/listinfo/x264-devel" target="_blank">http://mailman.videolan.org/listinfo/x264-devel</a><br>
</div></div></blockquote></div><br></div>