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

Issue 648523 link

Starred by 6 users

Issue metadata

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



Sign in to add a comment

Flash regression issues from beta 54.0.2840.24

Project Member Reported by gbirtchnell@chromium.org, Sep 20 2016

Issue description

Chrome OS Version: beta 54.0.2840.24

NOTE: Potentially a side-affect of  crbug.com/644795 

Impact:
Updated on beta channel has caused Flash behaviour issues on customer SAP site (flash heavy) rendering unusable - 200k users at with impacted user.

1. 1st login is not recognised and you get sent back to login page, where on 2nd login is successful
2. Flash sections of the page do not correctly, displaying XXX boxes instead of the information, See the attached image. 

We don't currently have a publicly accessible site that is excreting this behaviour.

This is affecting multiple users on beta on different model devices. 
1 device we tested on v53 stable before updating to Dev v55, was working fine

Symptoms of potential related cause  crbug.com/644795 :

The Flash version on the device under chrome://plugins is reporting as 23.0.0.151, but when you head to a flash site that reports your flash version, it comes back as 23.0.0.162

In our testing on the Dev channel, we could see the flash version was 23.0.0.162 in the plugins and reporting the same on the flash site, and we could log into our page, however not all the information is displaying. 

Cannot be repro'd on Windows Chrome browser v54.0.2840.27. We have the same initial login issue, but after that, we are able to access all areas that use flash. Chrome Beta flash is on 23.0.0.173

Logs:
https://drive.google.com/drive/folders/0B9a1yrkxazgMbExHczBtaVVjWTg?usp=sharing
 
flash_broken_image.png
91.9 KB View Download

Comment 1 by ihf@chromium.org, Sep 20 2016

Cc: rohi...@chromium.org lafo...@chromium.org
Does this happen on M-55? If not then it is likely  issue 635030 .
Cc: blumberg@chromium.org georgesak@chromium.org dskaram@chromium.org
Cc: hsiangc@chromium.org vsu...@chromium.org
WOCR for M-55 testing within their corp SAP environment.
Initial response yesterday was it could be reproduced also on M-55.
Cc: viktorv@chromium.org sdavern@chromium.org
In 55.0.2858.0 on lumpy (FP 23.0.0.162) it no longer shows the garbage XXXX characters shown in c1 flash_broken_image.png, but instead in other cases it has removed some text containers within flash.

While M-54 would show containers with garbage characters (XXXX) - M-54-SAP-Flash.png
Now M-55 shows some containers entirely removed - M-55-SAP-Flash.png

@ihf do you think this should be merged to  issue 635030  ? They certainly appear connected.

55.0.2858.0 on lumpy log: https://drive.google.com/open?id=0B9a1yrkxazgMcHdiLWhiV3kwcmc
M-52-vs-M55.png
739 KB View Download
M-54-SAP-Flash.png
162 KB View Download
M-55-SAP-Flash.png
293 KB View Download
Labels: -Pri-2 ReleaseBlock-Beta Pri-1
Great that we caught this early. Adding release block beta and raising priority.

Is this really only happening on Chrome OS?
Customer advised it cannot be reproduces on Win Chrome browser stable or beta 54.0.2840.27.

Note - win chrome beta 54.0.2840.27 has Flash Player 23.0.0.173.

Currently only the customer can test the SAP flash environment described in c5.
Hi All, 

The issue is only on chrome OS. However we have another issue with this site as of v54 Beta on Chrome Browser and Chrome OS. 1st login to this site always fails (Starts to log you in and then takes you back to screen for credentials). 2nd login is successful. On device running v53 of Chrome OS, it worked. After updating to v54 and v55, the login prompt issue started. It may be connected. Happy to jump on a hangout and demo it. 

Comment 9 by laforge@google.com, Sep 21 2016

It might be worthwhile to try a 54.0.2840.x build that has a patch level >.32.  

We landed a fix for a loading issue  crbug.com/645028 , which was cross platform.  The fix for that might address the second issue that's being referenced in this bug.
@laforge,  crbug.com/645028  I'm unable to access - Is the bug number correct and the labels on it right for me to be blocked? I'm not the only internal that doesn't have permission.
@laforge, I have just loaded Chrome browser Beta v54.0.2840.34 onto my Win 7 PC, and I am no longer able to reproduce the 2nd login issue. Please let us know when this same fix comes to Chrome OS and we will confirm it for you. Thanks
Sorry the correct issue is  crbug.com/641028  (copying and pasting based on the last 28 digits doesn't always work).

@srcrew - Thank you for confirming, glad to hear that resolves the second half of the issue.
@laforge @ihf, do you have any insight into the larger issue here detailed in my c5?

Pleases advise where we can assist investigate.
Owner: ihf@chromium.org
Status: Assigned (was: Unconfirmed)
ihf@, any updates here?

Comment 15 by ihf@chromium.org, Sep 27 2016

Labels: -ReleaseBlock-Beta ReleaseBlock-Stable
Polite ping for any updates/progress, as this is high impact ~200k users with this customer.
can you elaborate on the requirements to have this customer on beta channel?
Ping for any updates. Thanks
Can repo on beta  54.0.2840.43 (Platform version: 8743.44.0).
Cc: bustamante@chromium.org
I can reproduce in beta 54.0.2840.43 (Platform version: 8743.44.0) in our product Wixie. This was reported by an end user who is running the beta channel in their classroom. The potential impact is ~50,000 k-6 students.

See attached screenshot.

Steps to reproduce:

Go to http://static.wixie.com/evaluation
Click the Try Wixie button
Observe text labels are unreadable.
Screenshot 2016-10-05 at 12.26.11 PM.png
237 KB View Download

Comment 22 by ihf@chromium.org, Oct 7 2016

Mergedinto: 635030
Status: Duplicate (was: Assigned)
Nice repro case in #21.

Sign in to add a comment