Closed Bug 2054513 Opened 4 months ago Closed 2 months ago

chatgpt.com - Connection is lost after 30 seconds when using voice

Categories

(Web Compatibility :: Site Reports, defect, P2)

Product:
Web Compatibility
Component:
Site Reports
Version:
Firefox 154
Platform:
Desktop
Windows
Type:
defect

Tracking

(Webcompat Priority:P1, Webcompat Score:8, firefox152 wontfix, firefox153 wontfix, firefox154 wontfix, firefox156 fixed, firefox157 verified, firefox158 fixed)

Status:
VERIFIED FIXED
Milestone:
156 Branch
Project Flags:
Webcompat Priority P1
Webcompat Score 8
Tracking Flags:
Tracking Status
firefox152 --- wontfix
firefox153 --- wontfix
firefox154 --- wontfix
firefox156 --- fixed
firefox157 --- verified
firefox158 --- fixed

People

(Reporter: ctanase, Assigned: wmcd, NeedInfo)

References

(
URL
)

Details

(Keywords: webcompat:platform-bug, webcompat:site-report, Whiteboard: [webcompat-source:product][autowebcompat:processed][webcompat:sightline][webcompat:japan][webcompat:core][autowebcompat:repro-failed])

User Story

platform:windows,mac,linux,android
impact:feature-broken
configuration:general
affects:all
branch:release
diagnosis-team:video-conferencing
user-impact-score:900
autowebcompat-repro-status:failed

Attachments

(1 file)

image.png
74.38 KB, image/png
Details
Attached image image.png —

Environment:
Operating system: Windows
Firefox version: Firefox 152.0.5 (release)/154

Preconditions:

  • Clean profile
  • Must be logged in

Steps to reproduce:

  1. Navigate to: https://chatgpt.com/c/6a48458f-ebf0-83eb-add5-fa9d5fb64d25
  2. Start a new chat.
  3. Click on "Use Voice" button on the chat.
  4. Interact with the AI for over 30 seconds.

Expected Behavior:
The connection is stable and voice chat works.

Actual Behavior:
Connection is lost after 30 seconds.

Notes:

  • Reproducible on the latest Firefox Release and Nightly
  • Reproducible regardless of the ETP setting
  • Works as expected using Chrome

Created from webcompat-user-report:d898becc-1cc3-4b3f-bdbb-94c9f80c3604

Whiteboard: [webcompat-source:product] → [webcompat-source:product][autowebcompat:processed]

Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.

status-firefox153: --- → affected
Whiteboard: [webcompat-source:product][autowebcompat:processed] → [webcompat-source:product][autowebcompat:processed][webcompat:sightline][webcompat:japan][webcompat:core]

We had bug 2036757 before, it might be a regression on their end?

Jib or Jeff, can you have a look at this and reach out to them if needed?

Severity: -- → S2
User Story: (updated)
Webcompat Priority: --- → P2
Webcompat Score: --- → 7
Flags: needinfo?(jmuizelaar)
Flags: needinfo?(jib)
Keywords: webcompat:needs-diagnosis
Priority: -- → P2
Whiteboard: [webcompat-source:product][autowebcompat:processed][webcompat:sightline][webcompat:japan][webcompat:core] → [webcompat-source:product][autowebcompat:processed][webcompat:sightline][webcompat:japan][webcompat:core][autowebcompat:repro-failed]
User Story: (updated)
Webcompat Priority: P2 → P1
Webcompat Score: 7 → 8

30s sounds like some type of ICE connection-status timeout

User Story: (updated)
Flags: needinfo?(docfaraday)

This sounds exactly like bug 2036757.

Flags: needinfo?(docfaraday)
See Also: → 2036757

Firefox is violating ICE nomination requirements when communicating with an ICE-lite endpoint. RFC 5245 §8.1.1 explicitly states that a controlling agent must use regular nomination when its peer is ICE-lite, and RFC 8445 §8.1.1 requires selecting and nominating a single candidate pair. Firefox instead sends USE-CANDIDATE on multiple paths simultaneously, even though the server advertises a=ice-lite. This causes Firefox and the server to select different equal-priority paths: Firefox keeps sending media and consent checks on the first path while the server switches to a later nomination, resulting in ICE disconnect after approximately six seconds and session failure after approximately 30 seconds.

-- from Codex

Flags: needinfo?(jmuizelaar) → needinfo?(docfaraday)

OpenAI has switched to using ice-lite? That's bug 1034964, something we've wanted to do for years, but will likely require significant work in nICEr. We've begun the process of making nICEr more memory-safe, so maybe it is not quite as risky to do significant work in there now, but anything that alters the timing/lifecycle in there (like bug 1034964 will) is still going to be dicey.

Flags: needinfo?(docfaraday)
User Story: (updated)
Webcompat Priority: P1 → P2
Webcompat Score: 8 → 7
Depends on: 1034964
Keywords: webcompat:needs-diagnosis → webcompat:platform-bug
User Story: (updated)
Webcompat Priority: P2 → P1
Webcompat Score: 7 → 8
User Story: (updated)

Bug 1034964 is now fixed, this needs to be verified.

User Story: (updated)
Flags: needinfo?(docfaraday)

Calin, can you still reproduce this with nightly?

Flags: needinfo?(ctanase)

This is working on latest Nightly now.

Flags: needinfo?(ctanase)
Status: NEW → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED
status-firefox157: --- → fixed
status-firefox158: --- → fixed
Assignee: nobody → wmcd
status-firefox152: affected → wontfix
status-firefox153: affected → wontfix
status-firefox154: affected → wontfix
status-firefox156: --- → fixed
Target Milestone: --- → 156 Branch

Verified, the issue no longer reproduces.

Tested with:

  • Browser / Version: Firefox 157.0-candidate build 1
  • Operating System: Windows 10
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: