queue2 sends eos unexpectedly

Lajos Okos lajos.okos at gmail.com
Fri Jan 27 10:53:23 UTC 2023


Dear Gstreamer Team,

The below pipeline terminates with EOS after running fine for roughly an
hour. The incoming stream is continous and I have no idea why the queue2
element  sudenly fails to send the next buffer saying non-regular file hits
EOS. The actual pipeline that you can recreate the problem is:

srtsrc localport=7001 mode=2 ! queue2 name=rate-buffer
temp-template=/tmp/buffer_XXXXXX ring-buffer-max-size=10000000000
max-size-buffers=0 ! decodebin ! fakesink

and the relevant lines from the log:

0:51:21.979851772 4113939 0x55ce5efd8d80 DEBUG             mpegtsbase
mpegtsbase.c:1731:mpegts_base_loop: Pulling data from 1410056400
0:51:21.979883759 4113939 0x55ce5efd8d80 DEBUG                 queue2
gstqueue2.c:3587:gst_queue2_get_range:<rate-buffer> Getting range: offset
1410056400, length 18800
0:51:21.979922312 4113939 0x55ce5efd8d80 INFO                  queue2
gstqueue2.c:3563:gst_queue2_update_upstream_size:<rate-buffer> upstream
size: -1
0:51:21.979952064 4113939 0x55ce5efd8d80 INFO                  queue2
gstqueue2.c:3563:gst_queue2_update_upstream_size:<rate-buffer> upstream
size: -1
0:51:21.979981677 4113939 0x55ce5efd8d80 DEBUG                 queue2
gstqueue2.c:1562:gst_queue2_create_read:<rate-buffer> Reading 18800 bytes
from 1410056400
0:51:21.980012896 4113939 0x55ce5efd8d80 DEBUG                 queue2
gstqueue2.c:1426:gst_queue2_have_data:<rate-buffer> looking for offset
1410056400, len 18800
0:51:21.980058433 4113939 0x55ce5efd8d80 DEBUG                 queue2
gstqueue2.c:651:find_range:<rate-buffer> found range for 1410056400:
[0-1410057152]
0:51:21.980103132 4113939 0x55ce5efd8d80 INFO                  queue2
gstqueue2.c:1435:gst_queue2_have_data:<rate-buffer> cur_level.bytes 752
(max 2097152)
0:51:21.980147621 4113939 0x55ce5efd8d80 DEBUG                 queue2
gstqueue2.c:1439:gst_queue2_have_data:<rate-buffer> we have a range
0x55ce5ef7cc80, offset 0, writing_pos 1410057152
0:51:21.980187221 4113939 0x55ce5efd8d80 DEBUG                 queue2
gstqueue2.c:1449:gst_queue2_have_data:<rate-buffer> Need more data (18048
bytes more)
0:51:21.980232199 4113939 0x55ce5efd8d80 DEBUG                 queue2
gstqueue2.c:1584:gst_queue2_create_read:<rate-buffer> reading 1410056400,
writing 1410057152, level 752, max 2097152
0:51:21.980297361 4113939 0x55ce5efd8d80 DEBUG                 queue2
gstqueue2.c:1612:gst_queue2_create_read:<rate-buffer> update current
position [1410056400-1410056400]

.......
0:51:22.017116844 4113939 0x55ce5efd8d80 DEBUG                 queue2
gstqueue2.c:1449:gst_queue2_have_data:<rate-buffer> Need more data (940
bytes more)
0:51:22.017143035 4113939 0x55ce5efd8d80 DEBUG                 queue2
gstqueue2.c:1584:gst_queue2_create_read:<rate-buffer> reading 1410056400,
writing 1410074260, level 17860, max 2097152
0:51:22.017166920 4113939 0x55ce5efd8d80 DEBUG                 queue2
gstqueue2.c:1612:gst_queue2_create_read:<rate-buffer> update current
position [1410056400-1410056400]
0:51:22.017190457 4113939 0x55ce5efd8d80 DEBUG                 queue2
gstqueue2.c:1360:update_cur_pos:<rate-buffer> updating max_reading_pos from
1410056400 to 1410056400
0:51:22.017210711 4113939 0x55ce5efd8d80 DEBUG                 queue2
gstqueue2.c:1622:gst_queue2_create_read:<rate-buffer> waiting for add
0:51:22.018841724 4113939 0x55ce5efd89e0 DEBUG                 queue2
gstqueue2.c:2882:gst_queue2_is_filled:<rate-buffer> max bytes 2097152, rb
size 10000000000, cur bytes 17860
0:51:22.018903184 4113939 0x55ce5efd89e0 DEBUG                 queue2
gstqueue2.c:911:apply_buffer:<rate-buffer> position updated to
0:51:21.990832456
0:51:22.018939153 4113939 0x55ce5efd89e0 DEBUG                 queue2
gstqueue2.c:765:update_time_level:<rate-buffer> sink 0:51:21.990832456, src
0:00:00.000000000
0:51:22.018976798 4113939 0x55ce5efd89e0 DEBUG                 queue2
gstqueue2.c:1306:update_in_rates:<rate-buffer> rates: in 577832.113865,
time 0:00:00.030908631
0:51:22.019004106 4113939 0x55ce5efd89e0 DEBUG                 queue2
gstqueue2.c:1974:gst_queue2_create_write:<rate-buffer> Writing 1316 bytes
to 8852
0:51:22.019077858 4113939 0x55ce5efd89e0 INFO                  queue2
gstqueue2.c:2113:gst_queue2_create_write:<rate-buffer> writing 1316 bytes
to range [0-1410074260] (rb wpos 8852)
0:51:22.019105865 4113939 0x55ce5efd89e0 INFO                  queue2
gstqueue2.c:2188:gst_queue2_create_write:<rate-buffer> wrote 1316 bytes to
8852 (0 bytes remaining to write)
0:51:22.019129821 4113939 0x55ce5efd89e0 INFO                  queue2
gstqueue2.c:2237:gst_queue2_create_write:<rate-buffer> cur_level.bytes
19176 (max 2097152)
0:51:22.019232069 4113939 0x55ce5efd8d80 DEBUG                 queue2
gstqueue2.c:1426:gst_queue2_have_data:<rate-buffer> looking for offset
1410056400, len 18800
0:51:22.019290177 4113939 0x55ce5efd8d80 DEBUG                 queue2
gstqueue2.c:651:find_range:<rate-buffer> found range for 1410056400:
[0-1410075576]
0:51:22.019318673 4113939 0x55ce5efd8d80 INFO                  queue2
gstqueue2.c:1435:gst_queue2_have_data:<rate-buffer> cur_level.bytes 19176
(max 2097152)
0:51:22.019344514 4113939 0x55ce5efd8d80 DEBUG                 queue2
gstqueue2.c:1439:gst_queue2_have_data:<rate-buffer> we have a range
0x55ce5ef7cc80, offset 0, writing_pos 1410075576
0:51:22.019390051 4113939 0x55ce5efd8d80 DEBUG                 queue2
gstqueue2.c:1533:gst_queue2_read_data_at_offset: non-regular file hits EOS
0:51:22.019412330 4113939 0x55ce5efd8d80 DEBUG                 queue2
gstqueue2.c:1704:gst_queue2_create_read:<rate-buffer> we have a read error
0:51:22.019445156 4113939 0x55ce5efd8d80 DEBUG             mpegtsbase
mpegtsbase.c:1756:mpegts_base_loop:<tsdemux0> Pausing task, reason eos

Do you think this is a bug in queue2 or should I use different parameters
for queue2 to make it work?

Many thanks for your advise!

Have a nice day,
Lajos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20230127/00b3e25e/attachment.htm>


More information about the gstreamer-devel mailing list