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

Issue 802972 link

Starred by 1 user
Status: Duplicate
Merged: issue 802159
Owner:
michae...@chromium.org
Closed: Jan 2018
Cc:
█ abdulsyed@chromium.org
gov...@chromium.org
nyerramilli@chromium.org
rbasuvula@chromium.org
katie@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression : Unable to share screen in Hangouts.

Reported by rp...@etouch.net, Jan 17 2018 
Chrome Version: 65.0.3322.3 (Official Build)Revision 8758ca55b13d4f2082b2ed9269fce8f37f37c577-refs/branch-heads/3322@{#6}(32/64-bit)
OS: Windows (7,8,8.1,10),Linux (14.04 LTS),Mac OS X(10.12.6,10.13.1,10.13.3)

What steps will reproduce the problem?
1. Launch Chrome , navigate to https://hangouts.google.com/ click on video call option
2. Now click on more options iron icon and select Share screen,observe

Actual Result: Unable to share screen in Hangouts
Expected Result : Should be able to share screen in Hangouts

This is regression issue, broken in ‘M 65’ and will soon update other info :
Good build: 65.0.3319.0  
Bad build: 65.0.3320.0
Actual_video.mov
806 KB Download
Expected_video.mov
857 KB Download

Comment 1 by rp...@etouch.net, Jan 17 2018

Labels: hasbisect-per-revision
Owner: katydek@google.com
Status: Assigned (was: Unconfirmed)
Pre condition : Sign in to browser with valid credentials

Using the per-revision bisect providing the bisect results
Good build: 65.0.3319.0 (Revision: 528845).
Bad build: 65.0.3320.0 (Revision: 529150).

You are probably looking for a change made after 529082 (known good), but no later than 529083 (first known bad).

CHANGELOG URL:

The script might not always return single CL as suspect as some perf builds might get missing due to failure.

https://chromium.googlesource.com/chromium/src/+log/fbd27c963ee5a09eb24d60b0aa3dff3e58cdfbbd..5b0879c77d86676a28d6e4334c3bdca0f005f6cb

Suspect : https://chromium.googlesource.com/chromium/src/+/5b0879c77d86676a28d6e4334c3bdca0f005f6cb

From the CL above, assigning the issue to the concern owner 

@katydek- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

Comment 2 by nyerramilli@chromium.org, Jan 17 2018

Cc: abdulsyed@chromium.org gov...@chromium.org
Labels: RegressedIn-65 Target-65 FoundIn-65
marking as RBD, please change if required.

Comment 3 by nyerramilli@chromium.org, Jan 17 2018

Labels: ReleaseBlock-Dev

Comment 4 by katie@chromium.org, Jan 17 2018

Cc: katie@chromium.org
Owner: michae...@chromium.org
I think it's pretty unlikely to be due to magnification controller. I tried re-running the bisect and got a build just slightly different -- maybe the first bisect had a typo?

You are probably looking for a change made after 529085 (known good), but no later than 529086 (first known bad).
CHANGELOG URL:
The script might not always return single CL as suspect as some perf builds might get missing due to failure.
  https://chromium.googlesource.com/chromium/src/+log/4bb5c126de58ace430863b605ed361d2051ccbb2..010fad40d12a9c85211312d4a9735171787806fe

Suspect change: https://chromium.googlesource.com/chromium/src/+/010fad40d12a9c85211312d4a9735171787806fe

This is a commit related to Hangouts, so it makes more sense to be the culprit. Adding Michael -- can you investigate from here?

Comment 5 by michae...@chromium.org, Jan 18 2018

Mergedinto: 802159
Status: Duplicate (was: Assigned)
Yep, this was broken by crrev.com/c/863103 for issue 753850. Already reverted yesterday, so the bug is fixed on ToT and shouldn't be included in today's branch.

Comment 6 by nyerramilli@chromium.org, Feb 2 2018

Labels: ET-MUM-Reported
►

Sign in to add a comment