twilio
"AbortError: Timeout starting video source" when calling createLocalTracks in Chrome v123 on Windows 10
Summary
Since January 19th, we have observed AbortError: Timeout starting video source exceptions when calling await video.createLocalTracks(). In some cases, the tracks are successfully created approximately 5 seconds after the exception is thrown.
All users have a user-agent string of Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.0.0 Safari/537.36
Given that Chrome v123 was released on January 14th, the timing of this issue aligns with the update. Additionally, all affected user-agent strings match Chrome v132, leading us to believe this issue is related to an incompatibility between Chrome v123 and this library. Prior to January 19th we have not seen any instance of this issue.
This issue has not been reproducible from our end, but we can see via session monitoring that users are experiencing this issue.
We are looking for any insights or reports of similar behavior. Has anyone encountered this issue or has any information regarding potential causes?
Environment Browser(s): Chrome 132 Operating System: Windows 10 Library Version: twilio-video.js 2.21.1
@nardonef We're not using Twilio but I am also seeing this issue when calling getUserMedia and it only started appearing a few days ago on 2/3 and it's very hard to reproduce. Quick clarification, did you mean Chrome V132? We're also seeing this on the same version of Edge. Please update with any info if you find out anything else.
Has anyone found a way to mitigate this in any way? It seems like Chromium is not prioritizing this bug...
Started seeing this error intermittently after upgrading twilio-video from 2.29.0 to 2.33.0.
