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

Issue 765974 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

Chrome crashing when using Command+W (closing tab), not always, but like 3 on 10 times

Reported by domi...@bluebeetle.me, Sep 17 2017

Issue description

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

Steps to reproduce the problem:
Chrome crashing when using Command+W (closing tab), not always, but like 3 on 10 times

What is the expected behavior?
Chrome crashing when using Command+W (closing tab), not always, but like 3 on 10 times

What went wrong?
Chrome crashing when using Command+W (closing tab), not always, but like 3 on 10 times

Crashed report ID: 

How much crashed? Whole browser

Is it a problem with a plugin? No 

Did this work before? N/A 

Chrome version: 61.0.3163.91  Channel: stable
OS Version: OS X 10.12.6
Flash Version: newest
 

Comment 1 by meh...@chromium.org, Sep 17 2017

Can you please attach the Apple crash log and/or the recent server crash ID from chrome://crashes ?

Thanks.
Labels: Needs-Triage-M61
Cc: sc00335...@techmahindra.com
Components: IO>Keyboard
Labels: Triaged-ET Needs-Feedback
Tested the issue on 61.0.3163.91 and on latest canary 63.0.3218.0 using Mac 10.12.1 and is not reproducible with steps mentioned in comment#0.

@Reporter: Could you please check the steps by creating fresh profile which don't have any extensions.If issue still persists could you install latest canary and check the issue. You can download canary builds from the below link https://www.chromium.org/getting-involved/dev-channel 


Comment 4 by shrike@chromium.org, Oct 20 2017

Status: WontFix (was: Unconfirmed)
[macbugtriage] No response from bug reporter for over 30 days so closing out. Please reopen if you have info per c#1.

Sign in to add a comment