Re: Issue 120941 in chromium: Chrome To Mobile: An error occured while sending the page.

[chro...@googlecode.com]

Comment #1 on issue 120941 by astra...@chromium.org: Chrome To Mobile: An
error occured while sending the page.
http://code.google.com/p/chromium/issues/detail?id=120941

+1 to better error messages ( and to fixing the spelling for occurred)
Given that the fixes are somewhat long to explain -- we may be better
served by having a "help" link that links to "how to resolve your error" ?

[chro...@googlecode.com]

Comment #2 on issue 120941 by bbois...@google.com: Chrome To Mobile: An

error occured while sending the page.
http://code.google.com/p/chromium/issues/detail?id=120941

I am seeing the error (Version 19.0.1084.1 dev, on Debian 64bit). Any way
to debug it?

[chro...@googlecode.com]

Comment #3 on issue 120941 by bugdro...@chromium.org: Chrome To Mobile: An

error occured while sending the page.

http://code.google.com/p/chromium/issues/detail?id=120941#c3

The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=131305

------------------------------------------------------------------------
r131305 | m...@chromium.org | Sun Apr 08 00:38:29 PDT 2012

Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/app/generated_resources.grd?r1=131305&r2=131304&pathrev=131305

Correct occured->occurred in generated_resources.grd.
(simple change to cycle the tree, what happened to our whitespace file?)

TBR=sky
BUG=120941
TEST=Occurred spelled correctly in Chrome To Mobile error messages, code
comments.

Review URL: https://chromiumcodereview.appspot.com/10020007
------------------------------------------------------------------------

[chro...@googlecode.com]

Comment #4 on issue 120941 by puntodif...@gmail.com: Chrome To Mobile: An

error occured while sending the page.
http://code.google.com/p/chromium/issues/detail?id=120941

In my experience, sending to mobile works fine when Chrome has just been
opened. After some time (let's say an hour, but I could be wrong), trying
to send a page will result in this error message being displayed after a
short delay (likely indicating network communication is happening). Any
further attempt at sending a page will result in the error message being
shown instantly upon clicking send. Closing and re-opening the browser will
fix it every time, and it's the only solution I found. I tried signing out
of Chrome Sync and signing back in several times, both on desktop and
mobile, to no avail.

Right now I'm on Chrome 20.0.1105.2 Win7SP1 x64 + CrMo 0.18.4409.2396
Galaxy Nexus with stock Android 4.0.4, but it has been the same for the
past couple of weeks.

[chro...@googlecode.com]

Updates:
Labels: -Mstone-21

Comment #6 on issue 120941 by m...@chromium.org: Chrome To Mobile: An error

occured while sending the page.
http://code.google.com/p/chromium/issues/detail?id=120941

Removing milestone until we have some actual plans for this feature :(

[chro...@googlecode.com]

Updates:
Labels: Mstone-23

Comment #9 on issue 120941 by srika...@chromium.org: Chrome To Mobile: An

error occured while sending the page.
http://code.google.com/p/chromium/issues/detail?id=120941

I can see this consistently on one of my 3 devices that are connected on my
account. The other 2 devices seem to be work fine. Happy to send out logs
etc as necessary. I am on Chrome Canary on OSX

[chro...@googlecode.com]

Comment #10 on issue 120941 by m...@chromium.org: Chrome To Mobile: An error

occured while sending the page.
http://code.google.com/p/chromium/issues/detail?id=120941

Your help/info would be invaluable! What OS/Chrome does your device have?
(chrome://version)
Please apply http://codereview.chromium.org/10913089 and check your logs
after a send error.
(look for "INFO:chrome_to_mobile_service.cc(576)] ChromeToMobile send
failed (XXX): <response string>")
Or debug ChromeToMobileService::HandleSubmitResponse |data| and |
source->GetResponseCode()| on send errors.
Or wait for the patch to hit ToT/Canary (but I'd greatly appreciate your
help asap).

Is there anything about the device that might distinguish it? Did you
install a pre-release Chrome?
Can you check if "Chrome to Mobile" is on from "Settings"->"Basics"->"<your
sync email>"?
*After* gathering sample failure response info, try toggling that option
off and back on and re-trying.

[chro...@googlecode.com]

Comment #11 on issue 120941 by srika...@chromium.org: Chrome To Mobile: An

error occured while sending the page.
http://code.google.com/p/chromium/issues/detail?id=120941

Chrome for Android is ToT from the m/m18 release branch (18.0.1025306 as of
the last test).

Don't have a development setup - so if you need the logs from the desktop
client, will likely need it to hit ToT/Canary. Where do I pick up the logs
from on the desktop ?

As far as what is installed on the devices, I have typically been moving
forward pretty actively with new revs of Chrome for Android across all my
devices (for understandable reasons). And sync is always turned on and just
made sure C2M is on as well. I am seeing the error message when I send to
my Samsung S3 but none when I send to my Nexus7.

Not sure if this is a red herring, but on the google.com/cloudprint
interface, I see all the jobs that were sent to the Samsung S3 as "Queued".

[chro...@googlecode.com]

Comment #12 on issue 120941 by m...@chromium.org: Chrome To Mobile: An error

occured while sending the page.
http://code.google.com/p/chromium/issues/detail?id=120941

Tommy, might this be the same as your queued jobs issue?
Can we compare queued jobs numbers with UMA failure rates (maybe they're
similar)?

Srikanth, do you have 15min to let me debug a send response to your device?
I can do so from my desktop, but need you to either share your device with
me:
(http://www.google.com/cloudprint#printers -> "Share" with
msw.c...@gmail.com)
or login to sync in my dev build (I'd obviously trash the profile after
debugging).

We may have a workaround to fix your problem, but I'd like a sample
response first.

[chro...@googlecode.com]

Comment #13 on issue 120941 by srika...@chromium.org: Chrome To Mobile: An

error occured while sending the page.
http://code.google.com/p/chromium/issues/detail?id=120941

Just shared the device (named "enceladus") with your @gmail address.

Let me know if you want me to check on anything (but will be a bit offline
this afternoon)

[chro...@googlecode.com]

Updates:
Status: Started

Comment #14 on issue 120941 by m...@chromium.org: Chrome To Mobile: An error

occured while sending the page.
http://code.google.com/p/chromium/issues/detail?id=120941

Thanks for your help, I was able to collect an example failure response!
I filed Issue 146685 to track the root cause, and I'll add some UMA logging.

If possible, please un-share that device with me now and try this
workaround:
1) Go into Chrome's settings on your device.
2) Click your sync email under "Basics".
3) Disable (un-check) "Chrome To Mobile", wait a second and re-enable
(re-check) it.
Now try sending a page to the device (please let us know if this works).

For reference, the cloud print job submission URLFetcher response data
contained:
{
"success": false,
"message": "Print job added but failed to notify printer about the new
job.",
"errorCode": 407,
...<irrelevant/identifiable information redacted, the rest looked fine>...
}

[chro...@googlecode.com]

Updates:
Blockedon: chromium:146685

Comment #15 on issue 120941 by srika...@chromium.org: Chrome To Mobile: An

error occured while sending the page.
http://code.google.com/p/chromium/issues/detail?id=120941

glad to help. Unshared device but let me know if you need it back.. I am
going to to leave the device in the state where it triggers this error in
case we want to debug more.

Marking this as blocked on crbug.com/146685 in case we have followups on
the desktop client for M23 based on changes on the mobile client etc

[chro...@googlecode.com]

Updates:
Cc: ydol...@chromium.org rltosc...@chromium.org

Comment #16 on issue 120941 by m...@chromium.org: Chrome To Mobile: An error

occured while sending the page.
http://code.google.com/p/chromium/issues/detail?id=120941

Hey Yuri or Robert, should Chrome temporarily un-list devices returning
errorCode 407?
They'd reappear on the next device list update, so it's a poor experience
either way.

[chro...@googlecode.com]

Comment #17 on issue 120941 by srika...@chromium.org: Chrome To Mobile: An

error occured while sending the page.
http://code.google.com/p/chromium/issues/detail?id=120941

Incidentally, I did try the workaround from #14 but still getting the
error. Looks like turning of Chrome2Mobile and turning it back on did
re-register the device (it is not listed under the default name from the
device - I had changed it 'enceladus' in the Cloud Print interface) but
still seeing the "An error occurred while sending the page"

Feel free to merge the different issues here into one if it is easier to
track these issues differently.

[chro...@googlecode.com]

Comment #18 on issue 120941 by m...@chromium.org: Chrome To Mobile: An error

occured while sending the page.
http://code.google.com/p/chromium/issues/detail?id=120941

Darn, I can check if you get the same 407 error if you share the device
again :-/

[chro...@googlecode.com]

Comment #19 on issue 120941 by srika...@chromium.org: Chrome To Mobile: An

error occured while sending the page.
http://code.google.com/p/chromium/issues/detail?id=120941

no worries...shared again - this time the device should come across as
GT-I9300

[chro...@googlecode.com]

Comment #20 on issue 120941 by m...@chromium.org: Chrome To Mobile: An error

occured while sending the page.
http://code.google.com/p/chromium/issues/detail?id=120941

Darn, same cloud print job submission response error from Comment #14.
I guess that workaround doesn't work... Tommy, ideas for another workaround?

[chro...@googlecode.com]

Comment #21 on issue 120941 by bugdro...@chromium.org: Chrome To Mobile: An

error occured while sending the page.

http://code.google.com/p/chromium/issues/detail?id=120941#c21

The following revision refers to this bug:

http://src.chromium.org/viewvc/chrome?view=rev&revision=155317

------------------------------------------------------------------------
r155317 | m...@chromium.org | 2012-09-07T05:33:42.234353Z

Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/chrome_to_mobile_service.cc?r1=155317&r2=155316&pathrev=155317
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/chrome_to_mobile_service.h?r1=155317&r2=155316&pathrev=155317

Adjust ChromeToMobile error logging and mitigation.

Increase kMaxRetries for URLFetcher to 5 (common elsewhere).
Decrease kDelayHours for URLFetcher to 1hr (w/exp backoff).

Clear |access_token_| with new kGaiaOAuth2LoginAccessToken.
Clear |access_token_| *and devices* on OnGetTokenFailure().
Handle invalid login refresh tokens as OnGetTokenFailure().
Clear token, devices, retry on 403 (auth) search responses.

Add and log some new BAD_* UMA Metric enum values.
(407 related to Issue 146685 and perhaps Issue 137267)
LOG (Chrome, not UMA) send response data on failure.

Corresponding src/tools/histograms/histograms.xml change:
https://chromereviews.googleplex.com/4782033

BUG=102709,120941,146685
TEST=Less Chrome To Mobile failures, additional insightful logging.

Review URL: https://chromiumcodereview.appspot.com/10913089
------------------------------------------------------------------------

[chro...@googlecode.com]

Comment #22 on issue 120941 by bugdro...@chromium.org: Chrome To Mobile: An

error occured while sending the page.

http://code.google.com/p/chromium/issues/detail?id=120941#c22

The following revision refers to this bug:

http://src.chromium.org/viewvc/chrome?view=rev&revision=155364

------------------------------------------------------------------------
r155364 | erikw...@chromium.org | 2012-09-07T12:34:01.673003Z

Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/chrome_to_mobile_service.cc?r1=155364&r2=155363&pathrev=155364
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/chrome_to_mobile_service.h?r1=155364&r2=155363&pathrev=155364

Revert 155317 - Adjust ChromeToMobile error logging and mitigation.

See
http://build.chromium.org/p/chromium/builders/Win7%20Sync/builds/25157/steps/sync_integration_tests/logs/stdio .

Specifically:

Sendin[1920:3900:0907/000156:407089812:FATAL:url_request_context.cc(99)]
Check failed: false. Leaked 2 URLRequest(s). First URL:
https://www.google.com/cloudprint/search?requestor=chrome-to-mobile.
[1920:3900:0907/000156:407089812:FATAL:url_request_context.cc(99)] Check
failed: false. Leaked 2 URLRequest(s). First URL:
https://www.google.com/cloudprint/search?requestor=chrome-to-mobile.

My suspicion is that by increasing retries, it ended up that a request was
still going when the browser is shutting down.

Verify that these requests are being properly stopped/destroyed before the
context they are using goes away.

------

Increase kMaxRetries for URLFetcher to 5 (common elsewhere).
Decrease kDelayHours for URLFetcher to 1hr (w/exp backoff).

Clear |access_token_| with new kGaiaOAuth2LoginAccessToken.
Clear |access_token_| *and devices* on OnGetTokenFailure().
Handle invalid login refresh tokens as OnGetTokenFailure().
Clear token, devices, retry on 403 (auth) search responses.

Add and log some new BAD_* UMA Metric enum values.
(407 related to Issue 146685 and perhaps Issue 137267)
LOG (Chrome, not UMA) send response data on failure.

Corresponding src/tools/histograms/histograms.xml change:
https://chromereviews.googleplex.com/4782033

BUG=102709,120941,146685
TEST=Less Chrome To Mobile failures, additional insightful logging.

Review URL: https://chromiumcodereview.appspot.com/10913089

TBR=m...@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10909115
------------------------------------------------------------------------

[chro...@googlecode.com]

Comment #25 on issue 120941 by dan...@staticfish.com: Chrome To Mobile: An

error occured while sending the page.
http://code.google.com/p/chromium/issues/detail?id=120941

Let me know if I can be of assistance? The issue happens to me all the
time, with the exact error happening after chrome has been open for a while.

[chro...@googlecode.com]

Comment #26 on issue 120941 by nyqu...@chromium.org: Chrome To Mobile: An

error occured while sending the page.
http://code.google.com/p/chromium/issues/detail?id=120941

daniel@: Which version of Chrome are you seeing this on?

[chro...@googlecode.com]

Comment #27 on issue 120941 by m...@chromium.org: Chrome To Mobile: An error

occured while sending the page.
http://code.google.com/p/chromium/issues/detail?id=120941

Thanks Daniel. That sounds like auth expiry, which I just fixed in
http://crrev.com/156108

If you get an error on Dev/Canary (with that fix), check the logs
for: "ChromeToMobile send failed (...)".
Post here (or send me) that output and I'll investigate. Remember to redact
any personal info; thanks!

[chro...@googlecode.com]

Updates:
Labels: -Mstone-23 Mstone-24

Comment #28 on issue 120941 by m...@chromium.org: Chrome To Mobile: An error

occured while sending the page.
http://code.google.com/p/chromium/issues/detail?id=120941

I've made good progress and this isn't blocking M23, but there's still more
to do.
Search/send #s are better, but auth token generation still fails
frequently. Example one-day UMA:
https://gfsviewer.corp.google.com/cns/pa-d/home/uma-data/public/dashboards/histograms.html?dayCount=1&endDate=09-21-2012&version=24.0.1273.0-W&group=ChromeToMobile&histogram=Service&otherVersions=10
This unexpectedly shows "Send Success"(22) > "Sending URL"(15) + "Sending
Snapshot"(3).
I have a speculative fix for that at
https://codereview.chromium.org/10970054

[chro...@googlecode.com]

Comment #31 on issue 120941 by c.brueggemann94: Chrome To Mobile: An error

occured while sending the page.
http://code.google.com/p/chromium/issues/detail?id=120941

I've got the same issue for quite some time now. If I can help in any way,
please let me know.

[chro...@googlecode.com]

Comment #32 on issue 120941 by m...@chromium.org: Chrome To Mobile: An error

occured while sending the page.
http://code.google.com/p/chromium/issues/detail?id=120941

c.brueggemann94, Try to repro on Dev/Canary with --v=1, check your logs
for: "ChromeToMobile send failed"...

[chro...@googlecode.com]

Updates:
Status: WontFix

Comment #40 on issue 120941 by m...@chromium.org: Chrome To Mobile: An error

occured while sending the page.
http://code.google.com/p/chromium/issues/detail?id=120941

Closing this WontFix as per Issue 260121. This issue should be revived if
CTM desktop integration is revived.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings