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

Issue 700402 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

an extension, through contentSettings API, can crash Chrome.

Reported by rglee...@londontrustmedia.com, Mar 10 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.98 Safari/537.36

Steps to reproduce the problem:
1. Create a new extension.
2. block access to microphone from background script (all URLS).
3. block access to location from background script (all URLS).
4. block access to camera from background script (all URLS).
5. visit a page, for example https://github.com
6. click "Secure" beside the github.com address.
7. Observe that the extension is blocking all three items from above.
8. Now, open a browserAction popup page that will set "ask" permission on any of those three items.
9. Click "Secure" again, and Chrome will crash.

What is the expected behavior?
The expected behaviour is that while a contentSetting is changed after a tab has loaded and clicking 'Security' beside the address will not crash Chrome.

What went wrong?
Chrome crashed.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 57.0.2987.98  Channel: stable
OS Version: OS X 10.12.3
Flash Version:

 

Comment 1 by meh...@chromium.org, Mar 10 2017

Can you please attach the Apple crash log or/and the Chrome crash id from chrome://crashes ?

Thanks.
Cc: pbomm...@chromium.org
Components: Platform>Extensions
Labels: M-57 Needs-Feedback
rgleeson@ can you please provide us the Extension which you are using in Step1, since I wasn't able to reproduce the issue on MAC OSX 10.12.3 with Chrome version 57.0.2987.98. 
Cc: kkaluri@chromium.org
rgleeson@ could you please respond to the comment #1 and #2.

Thank You...
Hi everyone,
I will try to create a reproduction extension when I have the free time. 
Project Member

Comment 5 by sheriffbot@chromium.org, Mar 20 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "pbommana@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
Hi everyone,
Attached is an extension that reproduces the crash for me.
Here are the steps I took to reproduce:
1) Load extension
2) Visit https://www.google.com
3) Open browseraction icon, click link.
4) Close browseraction popup, click "Secure" beside address bar.
5) Chrome crashes.

This happens all the time for me, on OSX.
I created a blank profile to do the test, with no other extensions installed.

bug700402.zip
12.9 KB Download
meh...@chromium.org - yes, if the extension doesn't reproduce for you I can do that. I can see the crash on that page, but i think i need to enable crash reports to see anything. 

Comment 8 by meh...@chromium.org, Mar 20 2017

Cc: rsesek@chromium.org
Labels: Stability-Crash
Status: Untriaged (was: Unconfirmed)
Thanks, I can reproduce the crash.

crash id: 7613dc22-d40c-4d81-937f-4a351698a228
Cc: rdevlin....@chromium.org
Labels: Needs-Bisect
Status: Available (was: Untriaged)
rgleeson@ thank you for the extension and detail steps.

Able to reproduce the issue based on steps provided in comment#6 on previous stable as well i.e, 56.0.2924.87 and latest stable 57.0.2987.110 on Mac(Unable to reproduce the issue on Windows 7 and 10)
Cc: ranjitkan@chromium.org
Labels: -Needs-Bisect Needs-Feedback
Rechecked this issue again on MAC 10.12.5 using chrome stable version 59.0.3071.109, Beta 60.0.3112.60 & Canary 61.0.3136.0. Unable to reproduce the crash. Installed the extension, navigated to google.com, clicked on the link "Click me to set "ask" permission for microphone. " from the extension icon and then clicked on "Secure" chrome chip from omnibox. No crashes are observed.

Removing bisect label, please add again if required.

@ rgleeson: Can you please try this on the latest available stable and let us know if the issue still persists.



Thanks.!
unable to reproduce on v59. seems fixed.

Status: WontFix (was: Available)

Sign in to add a comment