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

Issue 644400 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 644795
Owner:
Closed: Sep 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Some delay(~10 seconds) in loading the sign-in window.

Project Member Reported by abod...@chromium.org, Sep 6 2016

Issue description

Chrome Version:  54.0.2840.13
Chrome OS Version:8743.13.0
<b>Chrome OS Platform: <Make/model of computer running Chrome OS></b>
<b>Network info: <network, encryption type, router model (if known)></b>

Please specify Cr-* of the system to which this bug/feature applies (add
the label below).

Steps To Reproduce:
(1)Click on " Add person" and close the sign-in window without user name.
(2)and click on " Add person" one more time.


Expected Result:
Sign in window should be load immediately.
 
Actual Result:
Some delay(~ 10 seconds) in the loading sign-in window.
Its not reproduced on M53( 8530.79.0/53.0.2785.96)

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)
Always.

What is the impact to the user, and is there a workaround? If so, what is
it?

Please provide any additional information below. Attach a screen shot or
log if possible.

 
Labels: Needs-Feedback
Owner: abod...@chromium.org
Status: Assigned (was: Untriaged)
Is this reproducible?  Could be caused by a network issue?
Labels: -Needs-Feedback
Owner: ----
its always reproducible and same results with both wifi and Ethernet network.  
Cc: dchan@chromium.org krishna...@chromium.org
Components: Enterprise
Labels: -Pri-2 Pri-1
Could repro in Enrolled Devices too.Response on few buttons is too slow apprx more than 10 sec.Buttons like 'Add person',Done button after enrollment etc.

Comment 4 by dskaram@google.com, Sep 8 2016

Cc: afakhry@chromium.org
Components: -Enterprise
+afakhry, any ideas what could be happening?
Cc: xiy...@chromium.org
I can't repro this on ToT. +xiyuan if he's aware of any recent changes.
Yes. TOT looks good but still reproduced on M54 Chrome:54.0.2840.15/ChromeOS:8743.20.0 

Comment 7 by trapti@chromium.org, Sep 13 2016

Cc: -krishna...@chromium.org scunning...@chromium.org
Components: Enterprise
Build response is really bad for few keys esp in enrolled devices...keys like "Done" button after enrollment and add person is way too slow.


Candy 
Columns
M	ChromeOS	Chrome	ARC	Type	Channel
54	8743.25.0	54.0.2840.24	3264590	release	dev

Comment 8 by xiy...@chromium.org, Sep 13 2016

Repro'd on ToT as well (55.0.2858.0)

We show Gaia after cleaning the browser data of the sign in profile to ensure that new user sign-in is under a clear context. The delay is caused by plugin data removal time out (which is 10s).

[1291:1731:0913/131341:ERROR:plugin_data_remover_impl.cc(126)] Timed out

Not sure why though. 

Comment 9 by xiy...@chromium.org, Sep 13 2016

Did we change how pepper flash is bundled? 

Plugin data removal because the flash is not present:

[1246:1689:0913/134436:VERBOSE2:ppapi_plugin_process_host.cc(492)] ppapi plugin process launched.
[8724:8724:0913/134437:ERROR:ppapi_thread.cc(301)] Failed to load Pepper module from internal-not-yet-present (error: internal-not-yet-present: cannot open shared object file: No such file or directory)

Owner: waff...@chromium.org
waffles@, this is related to CL: https://codereview.chromium.org/2284053002

The fake Flash plugin shadows the one used by ChromeOS (passed via --ppapi-flash-path) and causing the failure.

Could you take a look?
Cc: -scunning...@chromium.org trapti@chromium.org
Cc: waff...@chromium.org
Owner: kerrnel@chromium.org
waffles@ pointed me to this CL https://codereview.chromium.org/2340643002/ and it fixes the long delay problem as well. Passing to CL owner kerrnel@.
Mergedinto: 644795
Status: Duplicate (was: Assigned)
Project Member

Comment 15 by bugdroid1@chromium.org, Sep 19 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/cf804457306e0facdb59124fa38b5315493e1da7

commit cf804457306e0facdb59124fa38b5315493e1da7
Author: kerrnel <kerrnel@chromium.org>
Date: Mon Sep 19 18:38:10 2016

Do not reference non-existant bundled flash on Chrome OS.

Chrome on Chrome OS is incorrectly building against the Flash player
bundled in third_party/. However, on Chrome OS, flash player is loaded
from the root partition and passed to Chrome via command line. So Chrome
should not be referencing the versions in flapper_version.h. In
addition, this means the bundled flash player loading code is unused.

BUG= 644795 , 644400 

Review-Url: https://codereview.chromium.org/2340643002
Cr-Commit-Position: refs/heads/master@{#419513}

[modify] https://crrev.com/cf804457306e0facdb59124fa38b5315493e1da7/chrome/common/chrome_content_client.cc
[modify] https://crrev.com/cf804457306e0facdb59124fa38b5315493e1da7/third_party/adobe/flash/BUILD.gn

Project Member

Comment 16 by bugdroid1@chromium.org, Sep 22 2016

Labels: merge-merged-2840
The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/00777c52ac61dba4cd3d9047ede488f337d4a9a5

commit 00777c52ac61dba4cd3d9047ede488f337d4a9a5
Author: Greg Kerr <kerrnel@chromium.org>
Date: Thu Sep 22 22:38:28 2016

Do not reference non-existant bundled flash on Chrome OS.

Chrome on Chrome OS is incorrectly building against the Flash player
bundled in third_party/. However, on Chrome OS, flash player is loaded
from the root partition and passed to Chrome via command line. So Chrome
should not be referencing the versions in flapper_version.h. In
addition, this means the bundled flash player loading code is unused.

BUG= 644795 , 644400 

Review-Url: https://codereview.chromium.org/2340643002
Cr-Commit-Position: refs/heads/master@{#419513}
(cherry picked from commit cf804457306e0facdb59124fa38b5315493e1da7)

Review URL: https://codereview.chromium.org/2366693003 .

Cr-Commit-Position: refs/branch-heads/2840@{#501}
Cr-Branched-From: 1ae106dbab4bddd85132d5b75c670794311f4c57-refs/heads/master@{#414607}

[modify] https://crrev.com/00777c52ac61dba4cd3d9047ede488f337d4a9a5/chrome/common/chrome_content_client.cc
[modify] https://crrev.com/00777c52ac61dba4cd3d9047ede488f337d4a9a5/third_party/adobe/flash/BUILD.gn

Project Member

Comment 17 by bugdroid1@chromium.org, Oct 27 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/00777c52ac61dba4cd3d9047ede488f337d4a9a5

commit 00777c52ac61dba4cd3d9047ede488f337d4a9a5
Author: Greg Kerr <kerrnel@chromium.org>
Date: Thu Sep 22 22:38:28 2016

Do not reference non-existant bundled flash on Chrome OS.

Chrome on Chrome OS is incorrectly building against the Flash player
bundled in third_party/. However, on Chrome OS, flash player is loaded
from the root partition and passed to Chrome via command line. So Chrome
should not be referencing the versions in flapper_version.h. In
addition, this means the bundled flash player loading code is unused.

BUG= 644795 , 644400 

Review-Url: https://codereview.chromium.org/2340643002
Cr-Commit-Position: refs/heads/master@{#419513}
(cherry picked from commit cf804457306e0facdb59124fa38b5315493e1da7)

Review URL: https://codereview.chromium.org/2366693003 .

Cr-Commit-Position: refs/branch-heads/2840@{#501}
Cr-Branched-From: 1ae106dbab4bddd85132d5b75c670794311f4c57-refs/heads/master@{#414607}

[modify] https://crrev.com/00777c52ac61dba4cd3d9047ede488f337d4a9a5/chrome/common/chrome_content_client.cc
[modify] https://crrev.com/00777c52ac61dba4cd3d9047ede488f337d4a9a5/third_party/adobe/flash/BUILD.gn

Sign in to add a comment