Issue metadata
Sign in to add a comment
|
All new tabs crash, existing tabs are able to open tabs that work (granted they are for the same domain)
Reported by
parasdee...@gmail.com,
Nov 1 2016
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2902.0 Safari/537.36 Steps to reproduce the problem: It's difficult to reproduce, as I'm not aware of any initial conditions that might cause it but this is definitely not the first time I've seen it. It tends to happen after prolonged use of the browser (not closing it for days on end) What is the expected behavior? Click on new tab --> opens a new tab What went wrong? The tab icon turns to a crash icon. Tab's becomes a dark gray background with no clickability. I'm not able to see the typical "something went wrong..." window Address bar becomes just as redundant. Crashed report ID: No, since it's only a tab crash How much crashed? Just one tab Is it a problem with a plugin? N/A Did this work before? No Chrome version: 56.0.2902.0 Channel: dev OS Version: 10.0 Flash Version: Shockwave Flash 23.0 r0 If I already have some opened tabs, they will function as expected (if I accidently close them, I can't bring them back). I can even open new tabs via the already opened tabs ONLY if the new tab wants to access a website from the same domain as the source tab. Hack: Have google.com opened, if the tabs crash, simple google search the site you want to access and open that in a new tab. Since all links are redirected through Google servers; the new tab opens regardless of destination.
,
Nov 2 2016
I've tried to collect data whenever it happens but fail to do so as I'm not familiar with chrome's internal crash reporters. Could you guide me on where I can access some kind of stats when the crash happens again (so I can find a way to reproduce it). Also, I forgot to mention that when this happens, chrome seems to jump back to normal functionality after a while (20-30 mins or so) and tabs function as normal.
,
Nov 9 2016
Thank you for providing more feedback. Adding requester "tkonchada@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 15 2016
parasdeep29@, can you please follow the link below and provide us with the Crash ID or the crash data file so that we can take at it at our end ? https://www.chromium.org/for-testers/bug-reporting-guidelines/reporting-crash-bug
,
Nov 15 2016
,
Dec 7 2016
,
Dec 13 2016
parasdeep29@ Could you please respond on comment #4. Thank You!
,
Dec 13 2016
Apologies. Yeah I've been trying to catch a bug report but it's really difficult to reproduce it. I'll spend more effort on it and see if that yields me something.
,
Dec 20 2016
parasdeep29@ Could you please confirm are you still facing this issue on latest chrome version ?
,
Dec 20 2016
I haven't observed it in the recent build (57.0.2950.4 dev) but I've positively seen it in the previous build.
,
Dec 20 2016
UPDATE: I've just observed a similar crash in the recent build. It happened when I used the middle click button on an http hyperlink, missing the "www" prefix from the link pointing to a location that redirects (the link in the accepted answer in this (http://stackoverflow.com/questions/11854772/how-can-i-quickly-and-effectively-debug-cloudformation-templates) SO post). The crash did not affect other newly opened tabs, but it conformed to the crashes observed earlier. Additionally, the crashes ceased once I typed the full address (with the "www") and the site was able to reach the redirected destination. Again, this might not be the actual cause because I could only produce it for the link twice (while trying other links which worked as expected); I thought it's worth a mention though. No, I don't have crash data, since this is a work computer
,
Dec 28 2016
Thank you for providing more feedback. Adding requester "pucchakayala@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 3 2017
Unable to reproduce the issue on win10 chrome version 57.0.2950.4 and canary 57.0.2969.0 - mouse middle click on any hyperlink opens the related webpage in new tab as expected Could you please upgrade to latest chrome version and see if issue still exists
,
Jan 3 2017
,
Jan 8 2017
No crash observed in the latest version. Please note, this was not a sure way of producing the crash. Just happen to work in a particular circumstance. I'll be sure to post more updates as things progress.
,
Jan 12 2017
Restoring this to the triage queue.
,
Jan 12 2017
Tested on chrome latest canary #57.0.2978.0 on win 10.0 and not able to reproduce the issue. As per comment #16 we need to check the issue on more latest builds.So not changing the status. Thank You!
,
Jan 19 2017
It still occurs as of M56, though I've not seen it (yet) on today's update (which instead introduced https://bugs.chromium.org/p/chromium/issues/detail?id=682404 ). I've tried to generate a crash ID for it, but Chrome doesn't record crash IDs for this. Even though earlier today there were at least 20 "tab crashes" (since I restarted the browser without fully exiting, and every reload crashed), the crash reporter shows 0 recent crashes.
,
Jan 26 2017
Thank you for providing more feedback. Adding requester "tkonchada@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 30 2017
parasdeep29@Could you please confirm are you still facing the issue on latest stable 56.0.2924.76? Please provide us any sample URL or crash id for triaging the issue further. Thanks,
,
Feb 1 2017
Thanks for the report. De-duping all of these into a bug with more details. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by tkonch...@chromium.org
, Nov 2 2016