This has already happened to me three times in the last few weeks. This is outrageous.

Unable to reproduce the issue on windows 7, Ubuntu 14.04 and Mac 10.12.3 using chrome version 56.0.2924.87 and canary 58.0.3026.0.Tab closed when clicked on X button without any freeze.

teo8976@ Request you once try the issue on new profile without any extensions/flags and if the issue still persists please provide us the crash id from chrome://crashes.

Thanks,

@3 have you even read the fucking report???

1. "Unable to reproduce"?? What have you done to try to "reproduce" an issue that happens sporadically and randomly?
2. how am I supposed to "try the issue" on a new profile? Use the new clean profile for months and if it doesn't happen in like a year I assume it doesn't reproduce the issue??
3. which crash report?? It doesn't crash, if freezes.


P.S. just happened again.

Thank you for providing more feedback. Adding requester "kavvaru@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

@5: I understand you're frustrated, but please don't abuse people trying to help triage bugs.  Chromium's code of conduct ( https://www.chromium.org/conduct ) applies here.

You noted that you've seen this issue three times now in a matter of days.  It seems, then, like using a new profile for a couple of days would provide a fairly strong signal.

I would have naively expected to get a crash dump if you kill the Chrome process while it's hung.  Is that not the case?

Rechecked using chrome stable version 59.0.3071.109 & beta# 60.0.3112.32 on Ubuntu 14.04, opened multiple tabs, played videos, left chrome idle for couple of hours, closed tabs and every time chrome responded well. Did not observe any freeze or crashes on chrome.

@ teo8976: Can you please use the upgraded chrome version and let us know if you are still facing any issues. if observed any crashes, it can be viewed at chrome://crashes. Please update us with the complete crash ID's.

Removing bisect label, as issue do not have a concrete repro steps.

Thanks.!

I do still observe the issue from time to time.
Obviously it's almost impossible to reproduce at will.
My current version is 59.0.3071.86

chrome://crashes is always empty

Thank you for providing more feedback. Adding requester "ranjitkan@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Request you to update chrome to the latest stable available and provide us with your inputs.

Note: rechecked on latest chrome stable 59.0.3071.115 on Ubuntu 14.04 and unable to reproduce the crash.

Thanks.!

> Note: rechecked on latest chrome stable 59.0.3071.115 on Ubuntu 14.04 and unable to reproduce the crash.

It's not something you can reproduce at will in any known way.


> Request you to update chrome to the latest stable available

I did and I keep observing the issue from time to time.

Now maybe my version is not the latest anymore, I'll update it, and by the time I observe the issue again, it won't be the latest version either.

Could we please get off this ridiculous loop and assume the issue is not fixed until something is at least done to try and fix it??


> I would have naively expected to get a crash dump if you kill the Chrome process while it's hung.  Is that not the case?

Apparently it is not.

I forgo to mention the obvious: I was commenting because I have just suffered from the issue again.

Thank you for providing more feedback. Adding requester "ranjitkan@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

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

What the fuck??