"Asynchronous operation is pending" error when registering gcm listener

[Keven Wang]

We have seen an increase in this "Asynchronous operation is pending" error recently. We have received 10+ support tickets in the last 6 weeks.

The register() and deregister() call are not fired in parallel.

Deleting GCM Store folder fixes the issue.

@Filip: Just want to flag, as this issue appears to be happening more frequently.

[Filip Gorski]

Hi, Keven,

Has the number increased in proportion to your user base?

Has it been affecting specific platforms?

Thanks.

Filip

[Keven Wang]

@Filip: We didn't hear any (or close to zero) user ticket in the previous 6+ months. And within the last 2 months or so, we received 13 support tickets.

The bug reports are all on Mac. A handful of users replied with their Chrome version, and are all on 53 (latest).

[Filip Gorski]

Keven,

I am wondering if you might be exhibiting this bug: crbug.com/651863

Please try to get some of the failing client instances to check with gcm-internals and compare to that. If there are more details you can share about that, adding it there or opening a new issue will definitely be helpful.

Thanks.

Filip

[Keven Wang]

Definitely seems similar. We will reach out to users about chrome://gcm-internals/ screenshots.

One thing we do, is calling chrome.gcm.register() on webpage refresh, which could happen up to several times per day. What's the best practice there?