New issue
Advanced search Search tips

Issue 753814 link

Starred by 3 users

Issue metadata

Status: Duplicate
Owner: ----
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Chrome crashes when trying to signin inside Chrome with installed VPN extension

Reported by oleksand...@gmail.com, Aug 9 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36

Steps to reproduce the problem:
1. Install VPN extension (e.g. https://chrome.google.com/webstore/detail/windscribe-free-vpn-and-a/hnmpcagpplmpfojmgmnngilcnanddlhb)
2. Login to it
3. Try to signin to your user account at Chrome

What is the expected behavior?
It should not crash. If Chrome fails to connect to desired resources for the signin - write about it to user.

What went wrong?
Chrome crashed

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 59.0.3071.115  Channel: stable
OS Version: 16.04
Flash Version: 

Provided extension uses onAuthRequired event to provide authorization. Requests that are fired during signin do not have this listener. Looks like it is not set and this is intended behavior.

So Chrome tries to make these requests they fail or hang up and Chrome crashes.

Requests are made to:
https://accounts.google.com
https://clients#SOME_NUMBER.google.com
https://ssl.gstatic.com
 
Cc: mmanchala@chromium.org
Labels: Needs-Feedback Needs-Milestone
Tested this Issue on Ubuntu 14.04 using reported Version # 59.0.3071.115 , latest Stable # 60.0.3112.90 and Canary # 62.0.3182.0 and unable to reproduce the issue.
Followed below Steps:

1)Installed VPN extension -> Signed in
2) Tried to signin to your user account  and observe no crash
	
oleksandr.olijnyk@ Could you please find the attachment and confirm if anything is missed in triaging the issue.Please recheck this issue by upgrading to latest Stable Version and attach Crash Id from chrome://crashes

753814.ogv
1.6 MB View Download
Hi,

made a video to demonstrate a bug:
https://www.dropbox.com/s/j6yadplr1kweoy9/proxy_bug.mp4?dl=0 

Also attaching the very simple extension that you can use to replicate the bug.
This extension only sets proxy server to one of Windscribe extension's proxy servers that require authentication.

And I have latest version of Chrome (59.0.3071.115 (Official Build) (64-bit)) and chrome://crashes does not show any crashes.

BG,
Alex
proxy_bug_demo.zip
12.5 KB Download
Project Member

Comment 3 by sheriffbot@chromium.org, Aug 14 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "mmanchala@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Components: Platform>Extensions Services>SignIn Internals>Network>Auth
Labels: -Type-Bug -Pri-2 hasbisect-per-revision ReleaseBlock-Stable M-62 OS-Mac OS-Windows Pri-1 Type-Bug-Regression
Owner: msarda@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue on Windows 10, Mac 10.12.6 and Ubuntu 14.04 using latest stable #60.0.3112.101 but the same is not reproducible using the latest canary #62.0.3191.0.

Reverse Bisect Information:
=====================
Good build: 62.0.3167.0  Revision(489499)
Bad Build : 62.0.3166.0  Revision(489161)

Change Log URL: 
https://chromium.googlesource.com/chromium/src/+log/d13299d0d6508ca8c1a53fb9ec1eac5a000d7064..0725e99fd873ec5412ef29e21c34d165ec84642d

From the above change log possible CL that fixed this issue:
Change-Id: I358a28db0bc6cf071668cc71731fb3805af18692
Reviewed-on: https://chromium-review.googlesource.com/577847

msarda@ - Could you please check and merge the fix to M62 if it is a valid candidate.
Note: Adding label ReleaseBlock-Stable as it seems to be a recent regression.

Thanks...!!
We are branching in few days. Please have a fix ASAP.

Your bug is tagged as Release block Stable. 

M62 is branching soon and we will be taking only CRITICAL merges. Please plan accordingly.

Mergedinto: 629529
Owner: ----
Status: Duplicate (was: Assigned)
The issue looks similar to issue id: 629529. hence, merging into issue id: 629529.

Thanks...!!

Sign in to add a comment