[x264-devel] commit: Simplify pixel_ads (Loren Merritt )

Dylan Klebesadel dylanklebesadel at gmail.com
Tue Jul 6 17:23:45 CEST 2010


Try transcoding a raw file to a compressed x264.
If the file is 20 to 3 times the size of your ram it will run out of memory.
Can't we put a limit on how much memory x264 can use?

I'll screen capture this if it helps so you know what I am talking about.

On Tue, Jul 6, 2010 at 7:20 AM, Loren Merritt <lorenm at u.washington.edu>wrote:

> On Tue, 6 Jul 2010, Tomek Lenik wrote:
>
>  It transcode really slowly as its building up ram (like 2-5% cup usage)
>>> until it gets to be 1 or 2 gb of ram then it spikes to 70% cpu usage and
>>> then it runs out of memory.
>>>
>>
>> What OS do you have installed? Is it Windows? Is your x264 build 32-bit?
>>
>> Loren, does x264 map files in memory?
>>
>
> No, and even if it did that wouldn't require more physical memory than any
> other method of file I/O.
>
> I have no idea what Dylan screwed up to trigger his symptoms.
>
> --Loren Merritt
>
> _______________________________________________
> x264-devel mailing list
> x264-devel at videolan.org
> http://mailman.videolan.org/listinfo/x264-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/x264-devel/attachments/20100706/1b7643d7/attachment.htm>


More information about the x264-devel mailing list