New issue
Advanced search Search tips

Issue 789792 link

Starred by 4 users

Issue metadata

Status: WontFix
Owner:
Closed: Dec 5
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Enable Overrides under source tab in Canary crashes the browser after upgrading to MacOS High Sierra

Reported by jeff...@weather.com, Nov 30 2017

Issue description

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

Steps to reproduce the problem:
1. Enable Overrides under source tab in Canary
2. Make changes to one of the file on any site
3. Save and reload

What is the expected behavior?
When reload the changed file should be loaded

What went wrong?
Browser shuts down.

Did this work before? Yes Previous MacOS Sierra worked

Chrome version: 64.0.3280.0  Channel: canary
OS Version: OS X 10.13.1
Flash Version: 

After upgraded to High Sierra, it stopped working
 
Cc: einbinder@chromium.org
Labels: ReleaseBlock-Stable
Owner: allada@chromium.org
Status: Assigned (was: Unconfirmed)
Hm. For me even the Setup Overrides button is disabled.

Comment 2 by meh...@chromium.org, Nov 30 2017

jeff.lu@: Can you please attach the Apple crash log and/or the server id from chrome://crashes? Thanks.

Comment 3 by jeff...@weather.com, Nov 30 2017

Sure, please see attached file.
Issue789792.txt
113 KB View Download

Comment 4 by allada@chromium.org, Nov 30 2017

Owner: caseq@chromium.org
Thanks @caseq for looking into this issue.  Overrides has been a great tool in helping to debug our widgets that are hosted on third party sites.  I hope this will get resolved soon.  Meanwhile I will need to find a machine that I can test with :-)
@caseq one other thing I just encountered in Canary, Google docs don't seem to be loaded successfully.
Project Member

Comment 7 by sheriffbot@chromium.org, Dec 11 2017

Cc: pfeldman@chromium.org
This issue is marked as a release blocker with no milestone associated. Please add an appropriate milestone.

All release blocking issues should have milestones associated to it, so that the issue can tracked and the fixes can be pushed promptly.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 8 by sheriffbot@chromium.org, Feb 12 2018

This issue is marked as a release blocker with no milestone associated. Please add an appropriate milestone.

All release blocking issues should have milestones associated to it, so that the issue can tracked and the fixes can be pushed promptly.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Assigned)
Presuming this is resolved now. Please let us know if not.

Sign in to add a comment