Open ywcai opened 4 years ago
Could you please test with the branch bionic-gstreamer
? Instructions here: Kurento 7.0 moving to GStreamer 1.14 in Bionic
You can choose between apt-get
or Docker image. Docker is better.
If you choose apt-get
, make sure you uninstall properly all packages (Local Upgrade).
thanks , i guess my I problem is same to #433
@ywcai Were you able to upgrade to solve this by upgrading to the newest version of Kurento (inclusive of PR 22)?
@ywcai Were you able to upgrade to solve this by upgrading to the newest version of Kurento (inclusive of PR 22)?
No , we don't upgrade kurento . The bug is because my rtsp stream is disconnect and we auto repeat it , It's use the playEndpoint will cause this bug . Now i use the rtpEndpoint assemble the rtsp protocol to pull the camera stream , it's ok !
Related:
Prerequisites
Issue description
if i use PlayEndpoint play a rtsp url , it will report some alarm in the log like below:
I watch the kurento-meida-server' memory use the interface of serverManager.getUsedMemory()
the memory will keep increasing, 2 cameras will occupy about 1.8GB memory .
I guess the memory keep increasing, Is it whether related to the alarm log information I release the playEndpoint object, but the memory can not decline . so if after a certain period of time, my memory will be exhausted, and kurento will crash. I need to restart the all server
Context
I wish the playEndpoint release , the memory can release. And the endpoint not increasing, the memory is not increasing .
I need to confirm if this is a known problem.
How to reproduce?
1 Create mediaPipeline ; 2 Create a playendpoint to read a rtsp url or mp4 (the case is same), and the encode is H.264 3 Remind the memory stauts 4 see the kurento-media-server ' log , it will report above log info .
the main code
Expected & current behavior
not report error log info , and the memory not increasing i think, one playEndpoint should not occupy so much memory
(Optional) Possible solution
I try to release the playEndpoint obejct and destory the kurentoclient obejct ,but no effect Unless we restart the kurento service, memory never drops
INFO about your environment
Commands output
cat /etc/lsb-release
kurento-media-server --version
dpkg -l | grep -Pi 'kurento|kms-|gst.*1.5|nice'