-
Notifications
You must be signed in to change notification settings - Fork 79
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
macOS version crashes after a few seconds of sending video frames #38
Comments
Follow up: if I limit my frame sizes I send to max 540 pixels (in either width or height), then it runs fine. |
More info: specifying "VP8" (or "VP9") as the preferred encoder solves the issue.
|
@ldenoue I've been using version M96 on a production app for a few months with H264 with no issues (on iOS however)... until a few weeks ago where the H264 encoder started to fail. |
@anthonynevo I'm on macOS Monterey 12.4 (21F79) and iOS 15.4.1 (on iOS H264 works). |
Can you try to reproduce the issue on the latest WebRTC version M103? Maybe it was fixed by the WebRTC folks |
I updated my package to use the latest 103.0.0 but it still does not work unless I explicitly specify VP8 in |
Im having exactly the same problem w/ M103... crash in h264 encode on macOS, same app working fine on iOS. The backtrace is very similar it appears to be a message send to a zombie object. running with zombies enabled seems to confirm:
|
Still reproduce, even set VP8 doesn't help. |
I have a fix, trying to figure out how to submit to webrtc now, if anyone is interested in building from source I can send a diff |
Yes please 😩 |
any updates?
can u send? |
my bug report is here, the fix is submitted, you can fine it linked in the comments. hopefully it will land soon. |
I am using a custom video capturer that creates RTCVideoFrame(s) from a CGImage converted to a CVPixelBuffer (to initialize the RTCVideoFrame):
After a few seconds (might happen when the video resolution changes to 640x360) but not sure, then I get this crash (hard to debug for me).
Any idea?
By the way, a very similar code works great using your iOS demo sample.
Do you have a macOS version of that sample?
Laurent
The text was updated successfully, but these errors were encountered: