New issue
Advanced search Search tips

Issue 594080 link

Starred by 2 users

Issue metadata

Status: Archived
Owner: ----
Closed: May 2018
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

ARC Welder: timeout for Google Drive request if response is delayed

Reported by marcin.e...@gmail.com, Mar 11 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.116 Safari/537.36
Platform: Platform 7647.84.0 (Official Build) stable-channel link

Example URL:

Steps to reproduce the problem:
1. Open attached program. 
2. Start it using ARC Welder with specific metadata ( field "Any other comments").
3. Click "List Folder"

What is the expected behavior?
Drive files are listed in console. There is no exception.

What went wrong?
Read timeout exception is raised.

Did this work before? Yes In version < 48.0.2564.116

Chrome version: 48.0.2564.116  Channel: stable
OS Version: 
Flash Version: 20.0.0.306-r2

Hello,

We are developing ExplainEverything application. It is android app and it is running at ARC Welder. Since 48.xxx Chrome OS update we have 
strange problems with Google Drive. Before this update it was working ok. In 49.x beta it is not working as well. For example files listing request is not ok. 
Response is never received and there is read time out. On tablet it always works. 

In the attached file there is test program which demonstrates the problem. It uses account picker. After authentication is done folder listing 
is started. Request is sent but no response comes around. On tablet it is working correctly. The problem most often happens if network quality
is wrong. If response comes around with about 5, 10, 15 seconds delay it is working on tablet but not on Chrome.

I created test program which uses v3 drive API but the result is the same: read timeout.

Test program is logging data to console. For testing purposes please open it with ARC Welder with following data:

OAuth Client ID:
1047317725790-osdmeho764slt50gjs3bbk0mpn2b6529.apps.googleusercontent.com

Metadata:
{
"usePlayServices": ["plus"],
"crx_key": "MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuWEVPN1RorBoRBHNEnvb8Y4XsguNGmJW0oC+nLiR44wOUKl8se3fNgzQHDagY7W91rfwgcRjw5Wp7D2cBngC147aktWk9dBdEHfWh3gs6UpxC1wE2KCn3mDJ80t4FjjaKd4QsRfyd5OQAhrFOMhob9nb4mWAxz9yiGz/1phVOZoZORFQEPpIVFJ2GwHiywg7J06XCTFYJTT2XQHnlsrdTAMXDFOjGAQMt8J6F8dZEXZeSHXzn+WdH7ZY4f2AlZSvuT5OVmpGVxwDO556UK39yNeB1hxUkkn2jwXPronKzCV+hhe4ppEVTahHm8qCEPu8jUfOcwqiYsFRKRmcEAz+DwIDAQAB"
}

Chrome version: 48.0.2564.116
Platform 7647.84.0 (Official Build) stable-channel link
 
GoogleDriveTestProgram.zip
16.4 MB Download
Components: -Internals>Network Platform>ARC
The problem was solver by adding back off strategy to GoogleAccountCredential object. 
Project Member

Comment 3 by bugdroid1@chromium.org, May 12 2016

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/arc/arc/+/767c037a9b6aded3870e25e36214905a1fbaa3d9

commit 767c037a9b6aded3870e25e36214905a1fbaa3d9
Author: Victor Hsieh <victorhsieh@google.com>
Date: Thu May 12 05:21:03 2016

Project Member

Comment 4 by bugdroid1@chromium.org, May 12 2016

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/arc/arc/+/e67fd6b814e9dcdf2c5fabcb3e5041f8fb03441d

commit e67fd6b814e9dcdf2c5fabcb3e5041f8fb03441d
Author: Victor Hsieh <victorhsieh@google.com>
Date: Thu May 12 20:12:04 2016

Comment 5 by uekawa@chromium.org, May 11 2017

Labels: ARCWelder
Project Member

Comment 6 by sheriffbot@chromium.org, May 11 2018

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment