New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 651863 link

Starred by 5 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

GCM Connection State doesn't become Active

Reported by ser...@xtremepush.com, Sep 30 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12) AppleWebKit/602.1.50 (KHTML, like Gecko) Version/10.0 Safari/602.1.50

Steps to reproduce the problem:
No specific steps to reproduce the issue.

What is the expected behavior?

What went wrong?
Chrome suddenly stopped displaying web push notifications.

After some investigation I have found that chrome connection state was stuck on LOGGING IN. After a few days it changed to WAITING FOR BACKOFF. This information was taken from chrome://gcm-internals/

Restarting chrome, rebooting system and event mac OS update didn't help.

Previous discussion is here:
https://bugs.chromium.org/p/chromium/issues/detail?id=642139
People complaining about users becoming unavailable for sending push notification. So that might me one of the reasons. 

Did this work before? Yes 

Chrome version: <Copy from: 'about:version'>  Channel: stable
OS Version: OS X 10.12
Flash Version:
 
Chrome version is 53.0.2785.116 (64-bit)

Comment 2 by joh...@chromium.org, Sep 30 2016

Cc: peter@chromium.org zea@chromium.org
Components: Services>CloudMessaging
Thanks! zea@, have you seen anything like this before?
Cc: sureshkumari@chromium.org
Labels: Needs-Feedback
Tested the issue in Mac stable 53.0.2785.116 and 53.0.2785.143.Observed that the notifications from the site https://compare.buyhatke.com/  displayed for the first time.

Could you please confirm if this is the issue you are facing.Also please provide a screenshot/screencast for better understanding if you see in the latest version.


The issue is not related to any specific website or subscription.
Pushes are not getting through for every new or existing subscription from different websites.

Screenshot of gcm-internals page is attached. 
Connection state is flicking between LOGGING_IN and WAITING_FOR_BACKOFF. But it never becomes CONNECTED.
GCM Internals Google Chrome, Today at 2.18.02 PM.png
409 KB View Download

Comment 5 by zea@chromium.org, Oct 3 2016

Sounds like the login is failing. If you click the "start recording" button, it might be useful to see what messages are being sent/received.
Project Member

Comment 6 by sheriffbot@chromium.org, Oct 11 2016

Labels: -Needs-Feedback Needs-Review
Owner: sureshkumari@chromium.org
Thank you for providing more feedback. Adding requester "sureshkumari@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
sergey@  as per the comment-5 please click the "start recording" button, to see what messages are being sent/received.

Thanks,
I can see logs in "Connection Logs" section. No logs in other sections.
Screenshot is attached.

There is SOCKET_FAILURE error appearing approximately every minute.

There is also a few NETWORK_CHANGE messages in the middle (I was changing wi-fi, so that's not a problem).


GCM Internals Google Chrome, Today at 12.03.42 PM.png
364 KB View Download

Comment 9 by zea@chromium.org, Oct 21 2016

Sergey, could you pull up chrome://histograms and attach that dump to the bug? (there's no personal information in the histograms)
Histogram is attached
histogram.txt
3.2 MB View Download

Comment 11 by zea@chromium.org, Oct 24 2016

Looks like the initial connection is successful, but then the connection fails due to a timeout.

It would be useful to get a net-internals trace for this client. Because the connection happens at startup, you'll probably need to use the command line flag to enable the net-internals logging (see Logging on startup here: https://dev.chromium.org/for-testers/providing-network-details)
chrome_network_logs.txt
1.2 MB View Download

Comment 13 by zea@chromium.org, Oct 26 2016

Owner: zea@chromium.org
Unfortunately no smoking guns in the net-internals. There's two connection attempts, both timing out after receiving 30 bytes in response (all but one byte of which is the TLS data).

There's no checkin attempt in the log. We've received another report recently of a similar situation, and it turned out the device had failed to perform a checkin for > 9 months. I've filed  bug 659373  to add more visibility in chrome://gcm-internals about checkin info, which once fixed may help resolve this.

One other question: is this issue limited to one device? Do you see this behavior anywhere else?

Comment 14 by zea@chromium.org, Oct 26 2016

Just noticed something: your histogram log shows a successful checkin attempt. If you restart and then go to chrome://histograms, does it still show a value for GCM.CheckinRequestStatus? 

If so, that might imply we're failing to write the GCM Store for some reason (possibly a filesystem issue?).
Status: Assigned (was: Unconfirmed)
We are seeing a sudden increase in support tickets, around "Asynchronous operation is pending" error when registering gcm listener.

https://groups.google.com/forum/#!topic/gcm-for-chrome-feedback/rNbURkTjuF4
For context, we are seeing roughly 4 support tickets per week, over the last 2 months. Before, there has been close to zero support tickets on this issue.

Comment 18 by zea@chromium.org, Dec 6 2016

Hi Sergey, just following up, are you still seeing this issue? One thing that might be useful is to try with a chrome dev channel client. It now has some more debug information about checkin time that would be useful to gather (assume the issue repros there as well)
Yes, the issue is still happening for me. 
Will be happy to install dev channel client. What would be the steps then to collect debug information?

Comment 20 by zea@chromium.org, Dec 7 2016

The information from chrome://gcm-internals is the main thing I'd be interested in. In the new dev client, it will contain info about when the last checkin happened, when it's scheduled to happen, and it will start recording automatically when opened. 

If you have session restore enabled, you can open gcm-internals, then restart so that it's opened automatically as part of startup (hopefully catching any events that happen near startup).

Comment 21 by zea@chromium.org, Jan 26 2017

Labels: -Needs-Review Needs-Feedback
Hi guys.

I was able to test it with the chrome dev channel client. Issue is still appearing.

GCM internals, histogram and network logs are attached.


dev-histogram.txt
1.0 MB View Download
chrome-net-export-log.json
97.1 KB View Download
Here is GCM internals screenshots
dev-internals-2.png
344 KB View Download
dev-internals-1.png
460 KB View Download
Unfortunately, I am still facing this issue (it also has been reported to the Firebase support ticket #1-6515000014483). Attached the gcm-internals and histogram.

gcm-internals.txt
4.4 KB View Download
gcm-histogram.txt
7.4 KB View Download
The issue has been reproducible in 58.0.3029.110 (64-bit) and earlier versions as well as 60.0.3107.4 (Official Build) dev (64-bit).
The only solution I found is to delete chrome including the application data and reinstall it.

Sign in to add a comment