Chrome crashes when you command-w from a full-screen video.
Reported by
along...@gmail.com,
Mar 22 2018
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36 Steps to reproduce the problem: 1. Play a video and put it fullscreen; YouTube videos work fine though. 2. Press Command-W. 3. What is the expected behavior? It will crash. What went wrong? It crashed. Crashed report ID: How much crashed? Just one tab Is it a problem with a plugin? N/A Did this work before? N/A Chrome version: 65.0.3325.181 Channel: stable OS Version: OS X 10.13.3 Flash Version:
,
Mar 22 2018
Sorry, I didn't mean one tab. I meant that by pressing command-w without exiting the fullscreen will cause all of Google Chrome to crash. If I press escape then press command-w, everything would be fine. It just crashes when you don't exit fullscreen.
,
Mar 22 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 22 2018
Thanks for following up. Do you have a crash ID? Check chrome://crashes - you're looking for the server crash ID (not the local crash ID).
,
Mar 22 2018
,
Mar 22 2018
This crash seems to only occur when you command-w on a video that is live-streaming, such as WatchESPN or another live-streaming website. I don't know what the server crash ID is, but this is what I see (Uploaded Crash Report ID a34f9053d032d390 (Local Crash ID: d8c0f989-af9f-4de0-9c1c-3599cc2f2f39)). I've also pasted the crash information below. Chrome Version: 65.0.3325.181 Operating System: Mac OS X 10.13.3 URL (if applicable) where crash occurred: Can you reproduce this crash? What steps will reproduce this crash? (If it's not reproducible, what were you doing just before the crash?) 1. 2. 3. ****DO NOT CHANGE BELOW THIS LINE**** Crash ID: crash/a34f9053d032d390
,
Mar 22 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 22 2018
Got it, thanks - "a34f9053d032d390" was the crash ID we needed. That ID reveals that this is a known bug: issue 673728. I'm marking this issue as a duplicate of that one. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ellyjo...@chromium.org
, Mar 22 2018