New issue
Advanced search Search tips

Issue 687830 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 594936
Owner: ----
Closed: Feb 2017
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Closing a full-screen video tab (Cmd-W) causes immediate SIGSEGV

Reported by blerb...@gmail.com, Feb 2 2017

Issue description

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

Steps to reproduce the problem:
1.  Have a window open with a few tabs of normal browsing on external monitor
2. Open new tab, navigate to any video site (i.e. youtube).
3.  Undock this tab, move it to built-in laptop screen
4. Fullscreen video on this tab (such that only laptop screen is fullscreened)
5. Click on video to select that tab if deselected
6. Press Cmd-W to close the tab.

What is the expected behavior?
Video exits fullscreen and tab closes; other tabs and windows remain

What went wrong?
Browser crashes
Log attached

Crashed report ID: bac04a36-dd8d-43b9-b659-9e32cd82d80d

How much crashed? Whole browser

Is it a problem with a plugin? No 

Did this work before? Yes 

Chrome version: 55.0.2883.95  Channel: stable
OS Version: OS X 10.12.3
Flash Version: Shockwave Flash 24.0 r0

 

Comment 1 by blerb...@gmail.com, Feb 2 2017

As it might be relevant—this is on a MacBookPro13,3 (2016 15" with Touch Bar, 2.7GHz)

Comment 2 by blerb...@gmail.com, Feb 2 2017

I'm able to reproduce without the external monitor; all I need to do is have the video playing in its own window that I've undocked then Cmd-W while fullscreen.
Can you provide the server crash ID (you provided the client crash ID)?
Labels: Needs-Feedback
Marking as Needs-Feedback.

Comment 5 by blerb...@gmail.com, Feb 2 2017

Server ID: 7a563b9580000000

Comment 6 by blerb...@gmail.com, Feb 3 2017

Some additional crash IDs for the same bug: 4634f2e880000000, 0b9efbc980000000 

Possibly relevant: all the crash logs I see in Console.app are segfaulting on the same address: KERN_INVALID_ADDRESS at 0x0000000000000418

Comment 7 by ajha@chromium.org, Feb 6 2017

Labels: Needs-Milestone
Mergedinto: 594936
Status: Duplicate (was: Unconfirmed)
Thanks!

Sign in to add a comment