Why this events leak happen?

[Andrey Utkin]

2014/1/16 Thiago Santos <thiago.sousa.santos at collabora.com>:
> Hi,
>
> I tried to reproduce your issue with videotestsrc or with a ts file
> but was unable to see leaks in videodecoder.
> Perhaps it only happens with your file? Can you share it? What
> else are you doing to reproduce it? Do you let it play till the end
> or do you abort the pipeline?
> Does it happen if played with filesrc instead of from udp?

Thank you for your interest.
Doesn't happen with filesrc.
You can get the same source stream by running such commands:

either

ffmpeg \
    -re -f lavfi -i testsrc \
    -re -f lavfi -i aevalsrc="0.1*sin(2*PI*(360-2.5/2)*t) |
0.1*sin(2*PI*(360+2.5/2)*t)" \
    -re -f lavfi -i aevalsrc="sin(10*2*PI*t)*sin(880*2*PI*t)" \
    -re -f lavfi -i aevalsrc="sin(440*2*PI*t):s=44100" \
    -map 0:0 \
    -map 1:0 \
    -map 2:0 \
    -map 3:0 \
    -vcodec libx264 \
    -acodec aac \
    -strict -2 \
    -f mpegts udp://225.1.1.1:1234?localaddr=127.0.0.1

(audio streams shouldn't matter, so you should be able to leave just
"-re -f lavfi -i testsrc" input and drop audio ones)

or

while true; do wget -q -O - http://whdd.org/test.ts; done | pv -L
35000 | /usr/local/src/ffmpeg/tools/aviocat pipe:0
'udp://225.1.1.1:1234?localaddr=127.0.0.1&pkt_size=1316'

Having source up, launch above valgrind command and let it work ~20
seconds (so that h264parse "no SPS/PPS yet" warnings stop appearing).
Then interrupt valgrind with Ctrl+C.

-- 
Andrey Utkin