Public bug reported:
The following command starts the RTSP server along with the encoder:
gst-rtsp-server -p 8900 -a 10.92.171.159 -m /live \
"( videotestsrc ! video/x-raw,format=NV12,width=320,height=240,framerate=30/1 !
\
v4l2h264enc capture-io-mode=4 output-io-mode=4 ! \
h264parse config-interval=-1 ! rtph264pay name=pay0 pt=96 )"
When the following client command is executed:
gst-launch-1.0 rtspsrc location=rtsp://10.92.171.159:8900/live latency=0
! decodebin ! autovideosink
it opens a video encode instance on the QCM6490.
However, when Ctrl+C is pressed, the video encode instance is expected
to close and release all associated resources. Currently, this is not
happening. The pipeline receives the interrupt and transitions toward
the NULL state, but it gets stuck during the shutdown process and does
not fully close the encode session.
^Chandling interrupt.
Interrupt: Stopping pipeline ...
Execution ended after 0:00:04.285402674
Setting pipeline to NULL ...
The pipeline remains stuck at:
Setting pipeline to NULL ...
Ideally, the encoder session should be terminated and the corresponding
video encode instance should be released. Since this does not occur, the
encode instance remains allocated.
** Affects: gdcm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2161631
Title:
Desktop X12 variant and found that the issue is related to Ctrl+C
handling. On the QCM6490, the maximum supported encode instances are
limited to 16
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdcm/+bug/2161631/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
