New issue
Advanced search Search tips

Issue 637083 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner:
Closed: Aug 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Disable QUIC on XP

Project Member Reported by rch@chromium.org, Aug 11 2016

Issue description

QUIC does not work correctly on Windows XP. Since chrome is no longer supported on XP we *should* have no users on XP, but it turns out we actually have some who have managed to get m50, 51 or 52 installed. Let's just explicitly disable QUIC for these folks.
 

Comment 1 by mmenke@chromium.org, Aug 15 2016

Hrm...  I'm not sure we should be keeping XP-specific code around, let alone adding more of it.  We've already started removing XP workaround, and at some point, I'm going to remove the XP socket pool logic, so we have consistent behavior across platforms, which means we can BSOD in XP under some cases (May be XP SP2 or earlier, not sure).

Comment 2 by rch@chromium.org, Aug 15 2016

Status: WontFix (was: Started)
Ah, ok. That works for me. It's baffling that we have a bunch of users running m52 on XP, but I'm happy to drop this if we're, say, OK with BSOD'ing them.  Thanks.

Comment 3 by mmenke@chromium.org, Aug 15 2016

You may want to file a bug about our install/deployment stuff (I don't know the correct label), to see if we can figure out why/how XP people are running M52, but ending XP support should mean just that.

Sign in to add a comment