Callbridge incident

Chrome and Edge tabs may close unexpectedly during video meetings

Minor Resolved View vendor source →

Callbridge experienced a minor incident on July 14, 2025 affecting Video Conferencing, lasting 17d 3h. The incident has been resolved; the full update timeline is below.

Started
Jul 14, 2025, 04:25 PM UTC
Resolved
Jul 31, 2025, 07:38 PM UTC
Duration
17d 3h
Detected by Pingoru
Jul 14, 2025, 04:25 PM UTC

Affected components

Video Conferencing

Update timeline

  1. investigating Jul 14, 2025, 04:25 PM UTC

    We've identified a new issue where Chrome and Edge tabs may close unexpectedly during video meetings on our platform. We've already submitted a bug report to the Chromium team and are actively collaborating with them to investigate and resolve this as quickly as possible. In the meantime, downloading and installing our app will resolve this issue for you. https://support.callbridge.com/support/solutions/articles/42000113823-chrome-138-update

  2. monitoring Jul 28, 2025, 08:16 PM UTC

    Chrome 138 – Update on Video Freezing and Crashing Issues Two separate issues have occurred in recent weeks: video freezing/spinning, and browser crashes. After extensive analysis, both have been traced back to changes introduced in Chrome 138. 1. Video freezing or spinning: Chrome 138 was the cause of this issue. We’ve deployed updates to our video servers to resolve it. We’re confident this issue is fully addressed. 2. Browser crashing: This issue is also linked to Chrome 138. We have traced this Chrome bug to their AV1 video codec implementation, and have a working thesis that this is correct. We have disabled the AV1 codec in production, reverting to VP9. In our internal testing, this prevents Chrome from crashing. We continue monitoring this to confirm its effectiveness across all environments. 3. It’s unclear whether these issues were present in early versions of Chrome or were introduced after the stable release. Although we already test beta releases of Chrome, we are expanding our QA process to include longer, more detailed testing across a broader range of devices and browser versions to help us catch similar issues earlier in the future.

  3. resolved Jul 31, 2025, 07:38 PM UTC

    This incident has been resolved.