[MPlayer-users] mencoder uses up all my ram after "moving" to new hardware

[justin case]

Hi,

after moving my bttv-card to another pc (1,5 ghz duron, 384mb ram, redhat9
on 2.6.0 kernel with all modules compiled into kernel), the below mencoder
script eats up all ram within minutes @ approx. 60% load. then it keeps
encoding with around 4000k free memory.
mplayer version is: 1.0pre3-3.2.2, it used to be far older on my old
machine, but i'd assume, things to get better with the time ;)

strangely i also get the following kernel-message repeatedly:
i googled a little and found some ppl reporting similar messages using
dvb-cards and others that answered, they shouldn't worry..
----------------------------------------------------------------------------
---
Jan  3 19:58:16 atom kernel: i2c_adapter i2c-0: sendbytes: error - bailout.
Jan  3 19:58:16 atom kernel: msp34xx: I/O error #1 (read 0x12/0x18)
----------------------------------------------------------------------------
---

here the output of top:
----------------------------------------------------------------------------
---
CPU states:  65.0% user   5.8% system   0.0% nice   0.0% iowait  29.1% idle
Mem:   385212k av,  381172k used,    4040k free,       0k shrd,    2536k
buff
       216188k active,             148424k inactive
Swap:  257032k av,       0k used,  257032k free                  338288k
cached
----------------------------------------------------------------------------
---

..and here's the script (any further suggestions to improve?):
----------------------------------------------------------------------------
---
mencoder tv:// -oac mp3lame \
-lameopts cbr:br=112:aq=1  \
-ovc lavc -lavcopts vcodec=mpeg4:vbitrate=1800:keyint=300 \
-tv
driver=v4l2:amode=1:width=576:height=432:device=/dev/video0:volume=43:channe
l=25  \
-vop pp=lb,crop=576:320:0:56 \
-o /home/video/TV/capture_`date +%Y-%m-%d_%H-%M`.avi \
-endpos 02:20:00 \
----------------------------------------------------------------------------
---


on my old machine (1ghz duron, 128mb ram, redhat9, 2.4.20 kernel w. modules)
this didn't happen.

does anybody have an idea?


kind regards,
/jc