jason_haar@ Thanks for the issue.

Request you to provide a URL where this issue can be reproduced which will help in further triaging of the issue.

Thanks..

(Ignore comment #2. We are clearly not going to be able to reproduce this as it's an intranet thing.)

If Chrome is unresponsive altogether, that suggests something especially odd is going on. Maybe some messed up PKCS#11 module, or maybe a bug in our UI code.

Could you follow the instructions here, but use the PID of the browser process? (Given Chrome is unresponsive I imagine you'll need to use your system process manage to get the PID. Or you can look up the PID before reproducing.)
https://www.chromium.org/for-testers/bug-reporting-guidelines/hanging-tabs

Thanks!

It's been a week before this problem occurred again. I cannot debug it for you - it's obviously a race condition that occurs under very specific circumstances and I have no idea how to replicate them

ie the web app is a client-cert protected graylog server. That uses tonnes of javascript to give a realtime graphical dashboard of our logging infrastructure. So what I think happens is it is continually sending data refreshes to the browser, and then a network change occurs so that the DNS value for our graylog server suddenly flips from intranet (10.X) to Internet for a few moments due to a VPN tunnel change (which involves changing DNS server settings - which is how the DNS name changes from intranet to internet). During that small window, the browser starts refreshing via the Internet and the client cert validation occurs. But I am off asleep/somewhere else and so don't deal with that popup, and seconds/minutes later the VPN changes again and now the DNS name resolves to the non-client cert protected intranet IP. I am guessing at that point Chrome has become confused: it still has this client cert prompt open awaiting input for a decision-event that no longer exists? 

End result is I can be happily in a different tab within Chrome working just fine, but when I eventually click over to the graylog tab and see the client cert prompt, it's game over. At that point Chrome is locked and doesn't respond - I can't change to a working tab, etc. I can't even kill it through the Ubuntu/gnome window manager (ie the "x" button doesn't work) and instead I get a shell up and kill the process id instead.

Jason

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

As per comment #4, this issue is out of scope of triaging at TE end. Hence adding 'TE-NeedsTriageHelp' label and requesting someone from Internals>Network>SSL team to look into the issue and help in further triaging.

Thanks..

That sounds like there's an issue showing the prompt. If Chrome is completely locked, that suggests the UI thread is stuck, which puts it rather far from the TLS and certificate bits proper. I think we're really going to need the instructions here followed to be able to diagnose.
https://www.chromium.org/for-testers/bug-reporting-guidelines/hanging-tabs

[jason_haar]:  Could you please response to comment #8?  Since we don't have a repro, we'll need more information to make any progress here.

I have got as far as getting the task manager component running, and so have been waiting for the bug to happen again. I have had at least 2 Chrome updates since reporting this bug, so maybe it's been fixed? I'll let you know if it triggers again for sure :-)

Jason

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

(Reverting sheriffbot's incorrect triage.)

I'm going to go ahead and archive out this issue, since there's been no problems since Comment #10.