New issue
Advanced search Search tips

Issue 672624 link

Starred by 4 users

Issue metadata

Status: Untriaged
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Wifi keeps dropping on Pixel 1 device

Project Member Reported by esprehn@chromium.org, Dec 8 2016

Issue description

Google Chrome	54.0.2840.101 (Official Build) (64-bit)
Revision	0
Platform	8743.85.0 (Official Build) stable-channel link

I'm in a google hangout and the wifi keeps dropping.
 
net-internals-log.json
7.5 MB View Download
Components: Internals>Network>QUIC
[Adding QUIC since the connection is over QUIC, but I'm not yet asserting that this problem is a QUIC problem.]

Thanks for the net-internals dump!  When you say "Wifi keeps dropping", what's the actual symptom?  I'm not seeing anything in the net-internals dump suggesting dropped connections, and the QUIC connections specifically are not showing any substantial dropped packets, so I'm trying to figure out what symptom I should be trying to connect to a network level problem.  


Labels: Needs-Feedback
Does the problem still exists? Is it reproducible? If yes, does the wifi disconnect only when hangouts is used? Could you provide the additional information requested above to help the investigation? Thanks!
This seems to happen a lot on my pixel device in the SF office, it doesn't seem specific to hangouts. :/

Comment 5 by mmenke@chromium.org, Dec 28 2016

esprehn:  Could you please response to comment #1?  What do you mean by "WiFi keeps dropping"?  Getting network errors (If so, what error?), system UI says wifi offline, etc?
What I mean is that the little wifi icon in the system tray (where the clock is) starts blinking and saying it's reconnecting. It does this pretty often, Google-A drops it's connection and the machine then reconnects automatically.

How do I figure out why the machine is reconnecting constantly?
Components: -Internals>Network>QUIC -Internals>Network OS>Systems>Network
Labels: -Needs-Feedback
This sounds like the relevant component is Chrome OS networking code, not the Chrome network stack.
Labels: Enterprise-Triaged

Sign in to add a comment