-
Notifications
You must be signed in to change notification settings - Fork 636
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Live Stream/End Stream with WebRTC took almost 100% machine resources on Safari browser on MacOS of Apple chip #5656
Comments
Hi @trunghm, Thank you very much for creating the issue. We plan to handle this issue as a support perspective. I'm putting this to the backlog. Regards |
@trunghm I tested Safari 16.6 on a Mac M1 using the latest version of Ant Media Server and didn't experience any issues. I also tried https://antmedia.io/live-demo with no issues. Can you try using https://antmedia.io/live-demo and tell me if you still experience any problems with Safari and Mac? |
Hello @timantmedia , Thank you for looking into the issue. I've checked the site https://antmedia.io/live-demo, and noticed the issue has been improved compared to what I saw earlier, but it's still there. There are two things that I think may be helpful for you to check
Please let me know if you need further info. |
@e-vural Device: Macbook Pro 16 , Apple M1 Max, 32 GB Ram, 1 TB Safari: Ekran.Kaydi.2023-10-20.16.12.41.movChrome: Ekran.Kaydi.2023-10-20.16.14.43.mov |
We couldn't reproduce the problem and merge the implementation. So I am closing the issue now. Anyone can re-open the issue if encounter the same problem. |
Short description
Live Stream/End Stream with WebRTC took almost 100% machine resources and hung the browser for 5-15 seconds on Safari browser on MacOS of Apple chip.
Environment
Steps to reproduce
Expected behavior
The video appears after 1-2 seconds, same as what the standard webRTC takes - see example at https://webrtc.github.io/samples/src/content/getusermedia/gum/
Actual behavior
The browser hung from when I clicked on the Allow button to allow the camera until the cam appeared. The app appeared to take almost 100% CPU and network resources for about 5-15 seconds. The hung time period is to 15 seconds on Apple M1 Mac Pro, down to 5 seconds on Apple M2 Mac Pro. This issue is only observed on the Safari browser on Mac OS with an Apple chip. It's not happening on other browsers on the same machine, nor the Safari browser of Intel Mac
Ask your questions on Ant Media Github Discussions
The text was updated successfully, but these errors were encountered: