search

Kurento / bugtracker

[ARCHIVED] Contents migrated to monorepo: https://github.com/Kurento/kurento
46 stars 10 forks source link

Trouble with release() of rtpEndpoint #21

Open Lisitskiy opened 8 years ago

Lisitskiy commented 8 years ago

KMS Version: 6.2.1~6.g9d55178 Found modules: Module: 'core' version '6.2.1~17.g6c37842' Module: 'elements' version '6.2.1~31.g18f2840' Module: 'filters' version '6.2.1~1.gda6c417'

Os - ubuntu

When i create rtpEdnpoint for presenter by connecting to webRtcEndpoint - rtp encoding starts, and processor in hi load, all Ok. But when I stop only rtpEndpoint (webRtcEndpoint leave alive) by calling rtpEndpont.release(). Processor still in hi load, and encoding still alive.

I cant find any errors in kurento logs.

Example for demonstration trouble is here (based on node one2many call titorial) - https://github.com/Lisitskiy/kurento-one2many-call

  1. Click - Presenter
  2. Click - Start Presenter Rtp
  3. Click - Stop Presenter Presenter
igracia commented 8 years ago

@dfernandezlop David, could you please check this?

jcaden commented 8 years ago

The problem it's that agnosticbin in previous endpoint is not releasing the resources got for transcoding because it's something that is not implemented. This is why encoding is still being done. I guess it's not a bug but something not implemented.

This implementation is something that should be thought carefully because we have to decide when the encoder is not going to be used anymore, this is why it is not implented yet.

igracia commented 8 years ago

Ok, will mark it as enhancement then. I´ll milestone this for v7, as I don´t think it will be in 6.2.1, right?

jcaden commented 8 years ago

Thanks Ivan. Version 7 is fine we can change it if we finally do it for a previous version and it does not imply an API change

lfzawacki commented 7 years ago

This bug might be affecting us, do you have some estimate of when you'll get to work on it? Or is there some workaround?