streaming

描述(Description)

描述你遇到了什么问题

用户点播视频，PC端使用WebRtc播放，当用户关闭视频后，云服务器利用回调函数，主动踢掉用户播放的视频流，该过程进行十几次后，云服务器的CPU一直处于98%的状态，即使没有任何推流操作，cpu也无法得到释放。

1. SRS版本(Version): v 4.0.198

重现(Replay)

重现Bug的步骤(How to replay bug?)

1. 本地推流到SRS云服务器
2. PC端成功播放视频后，主动关闭视频，云服务器使用回调函数，进行主动踢流
3. 重复十几次后，CPU处于98%的状态

期望行为(Expect)

描述你期望发生的事情(Please describe your expectation)

频繁推流、拉流、

Logstash information:

Please include the following information:

1. Logstash version: 7.16.3 (with unverified reports of similar behaviour on 7.15)

   Looking through our case history there were examples of this issue happening after upgrading to 7.15 and higher. The odd behavior is this appears to be intermittent in most cases, and the cases closed out without resolution. Confirmed

current return queueOfferResult == QueueOfferResult.enqueued();

Summa

Hello! I'm curious if there have been discussions on releasing a native m1 build?

Thanks!

it's becoming more time-consuming and error-prone to manually re-test all the demos following internal refactorings and API adjustments.

now that the API is fleshed out a bit, it's possible to test a large amount of code (non-granularly) without having to simulate all interactions via Puppeteer or similar.

a lot of code can already be regression-tested by simply running all the demos and val

https://github.com/XGSClear7/real-url-api

We need a page to display where users can find source and binaries that have been successfully passed a vote.

We aslo need a security page on our podling site for any security issues that may arise. See http://tomcat.apache.org/security.html for an example.