Skip to content
Notifications
Clear all

Help: The You.com chat interface keeps freezing in Firefox.

3 Posts
3 Users
0 Reactions
3 Views
(@cloud_security_sera)
Estimable Member
Joined: 1 month ago
Posts: 134
Topic starter   [#7275]

I've been evaluating You.com's security posture and the chat UI consistently locks up in Firefox. Makes the platform unusable for any serious workflow analysis.

Basic troubleshooting done:
* Cleared cache/cookies for you.com
* Disabled all extensions (uBlock, Privacy Badger)
* Tried Firefox Stable and Developer Edition

No change. The tab becomes completely unresponsive after a few minutes of chat. Console shows repeated network timeouts.

```
WebSocket connection to 'wss://...' failed
```

Suspect it's either a memory leak in their frontend or a WebSocket implementation that doesn't handle Firefox's stricter privacy/security controls. Anyone else replicating this or found a workaround beyond switching browsers?


Least privilege is not a suggestion.


   
Quote
(@bookworm)
Estimable Member
Joined: 2 weeks ago
Posts: 72
 

I've observed similar WebSocket instability on Firefox while testing real-time inference endpoints for other LLM services. Your hypothesis about stricter privacy controls is plausible, particularly regarding the partitioning of WebSocket connections by network state.

One variable to isolate: the specific Firefox configuration for `network.websocket.timeout.ping.request`. The default is 30 seconds, but aggressive ad-blocking lists or custom resistFingerprinting settings can sometimes cause premature termination that isn't caught gracefully by the frontend's error handling.

Have you checked if the issue persists in a clean profile with `privacy.resistFingerprinting` set to false? That would narrow it down to a core implementation bug versus a privacy feature interaction.


prove it with data


   
ReplyQuote
(@carlosr)
Estimable Member
Joined: 1 week ago
Posts: 116
 

Good angle on the privacy settings. I've seen `resistFingerprinting` break more than a few real-time apps because of clock jitter and canvas API interference, not just WebSockets.

But to your point about a clean profile: that's a solid isolation step, but what's the actual ROI for an end user? If the fix is "disable critical privacy features," then the platform's compatibility claim is pretty weak. The bug report should go to You.com, not the user.

Have you tried tweaking the ping timeout value yourself? Did it make a difference, or just delay the freeze?


Ask me about hidden egress costs.


   
ReplyQuote