RESOLVED CONFIGURATION CHANGED 241224
MediaStreamTrack randomly ends due to a capture failure
https://bugs.webkit.org/show_bug.cgi?id=241224
Summary MediaStreamTrack randomly ends due to a capture failure
btham
Reported 2022-06-02 06:05:00 PDT
Hi, I am filing this bug on behalf of someone else who is experiencing this issue. She is able to reproduce it often on her 2.6 GHz 6-Core Intel Core i7 MacBook Pro (16-inch, 2019) using macOS Big Sur Version 11.6 and Safari Version 15.0 (16612.1.29.41.4, 16612), though it seems to occur randomly. The issue is that during a Webex meeting, she will often get this error: "A MediaStreamTrack ended due to a capture failure". When this error occurs, she won't be able to see either the other attendees' video content (it turns black) or screen sharing content (it turns blank). It seems to be similar to https://bugs.webkit.org/show_bug.cgi?id=220998 which was a bug with Safari 14. Perhaps it has reappeared? Someone in https://bugs.webkit.org/show_bug.cgi?id=221192 has also mentioned they are experiencing a similar issue in Safari 15. Please let me know if you need more information and I can ask for it. Thanks!
Attachments
youenn fablet
Comment 1 2022-06-02 06:06:30 PDT
Can you send me a sysdiagnose (youenn@apple.com) with a rough time of the failure, ideally using the latest Safari Tech Preview or latest MacOS release?
btham
Comment 2 2022-06-06 06:02:08 PDT
Hi Youenn, after some further investigation on our end, we've found that the issue seems to only happen on Mac OS 11.6 + Safari 15.0. Do you still want me to send you the sysdiagnose for it?
Radar WebKit Bug Importer
Comment 3 2022-06-09 06:06:07 PDT
youenn fablet
Comment 4 2022-06-13 09:37:20 PDT
(In reply to btham from comment #2) > Hi Youenn, after some further investigation on our end, we've found that the > issue seems to only happen on Mac OS 11.6 + Safari 15.0. Do you still want > me to send you the sysdiagnose for it? Let’s close this bug then. Please reopen if you can reproduce on latest OS versions.
Note You need to log in before you can comment on or make changes to this bug.