| [21868:21882:336417980872:ERROR:net/socket/ssl_client_socket_nss.cc(1418)] handshake failed; NSS error code -12229, net_error -107 | |||||||
| Reported by bugabu...@gmail.com, Jul 13 2010 | Back to list | ||||||
Chrome Version : 6.0.464.0 (52070) Built on Ubuntu 9.10, running on Debian unstable URLs (if applicable) : http://ourdoings.com/person.html Other browsers tested: Add OK or FAIL after other browsers where you have tested this issue: Safari 4: Firefox 3.x: IE 7: IE 8: What steps will reproduce the problem? 1. access http://ourdoings.com/person.html 2. pop up from ISA Server shows up for SSL redirect 3. enter credencials What is the expected result? Login as regular What happens instead? crash Please provide any additional information below. Attach a screenshot if possible.
,
Jul 13 2010
Thank you for the bug report.
The crash.txt file you attached shows Chromium crashed after
getting a handshake failure:
[21868:21882:336417980872:ERROR:net/socket/ssl_client_socket_nss.cc(1418)] handshake failed; NSS error code -12229, net_error -107
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffea364710 (LWP 21882)]
0x0000000000000000 in ?? ()
(gdb) bt full
#0 0x0000000000000000 in ?? ()
No symbol table info available.
#1 0x0000000000c49490 in net::HttpNetworkTransaction::DoReadHeadersComplete (this=0x4570a80, result=0) at net/http/http_network_transaction.cc:1379
ssl_socket = 0x4ebd340
rv = <value optimized out>
In r51387 and r52001 of http_network_transaction.cc, line 1379 is:
1376 if (using_ssl_) {
1377 SSLClientSocket* ssl_socket =
1378 reinterpret_cast<SSLClientSocket*>(connection_->socket());
1379 ssl_socket->GetSSLInfo(&response_.ssl_info);
1380 }
Most likely, connection_->socket() is not an SSLClientSocket at that point.
,
Jul 13 2010
It sounds like it requires an ISA server to reproduce (directly) ? BUGabundo: can you help debug this problem by checking wtc's assumption as to the cause? After the segfault enter these commands into gdb and report the output: p /a (* (void***)ssl_socket)[0] p /a (* (void***)ssl_socket)[1] p /a (* (void***)ssl_socket)[2] p /a (* (void***)ssl_socket)[3] p /a (* (void***)ssl_socket)[4]
,
Jul 13 2010
vandebo: yes, I'm afraid that an ISA server is the best way to reproduce this crash. We can also try configure a Squid proxy server to request Negotiate or NTLM auth. I tried that once before, but couldn't get it to work. One special property of Negotiate/NTLM is that it is connection-based, which means only the very first HTTP request on the connection needs authentication. Subsequent HTTP requests on the same connection don't need any authentication header. This may be relevant to this crash.
,
Jul 13 2010
Would a combination of HttpNetworkTransactionTest.RestartAfterTLSDecompressionFailure and HttpProxyClientSocketPoolTest.HaveAuth be likely to trigger the same code paths in HttpNetworkTransaction?
,
Jul 15 2010
,
Jul 15 2010
,
Jul 16 2010
vandebo sorry for the lack of early reply. i was without access to may email client. its weekend, so i dont have access to the ISA server. will try to retest on Monday. Sorry once again for the delay, and thanks for the quick reply
,
Jul 19 2010
i tried very hard, but could not reproduce this but with 6.0.471.0 (52879) Built on Ubuntu 9.10, running on Debian unstable with both ISA server 2003 and 2010, today.
,
Jul 19 2010
BUGabundo: did you build Chromium from source code yourself? I'm curious why you're running on Debian unstable Chromium binaries built on Ubuntu 9.10.
,
Jul 19 2010
Issue 45987 has been merged into this issue.
,
Jul 19 2010
wtc i have not. I'm just using Ubuntu daily PPA at work (as I do at home, in ubuntu 10.10). I know now theres a repo for debian, but there wasnt one when i first installed chromium in debian. if you think thats the root cause for some of my problems, i'll gladly follow your instructions to run a trunk version appropriated to my office OS.
,
Jul 19 2010
BUGabundo: it should be fine to run Ubuntu daily PPA on Debian unstable. I'm going to mark this bug WontFix (for "cannot reproduce") based on your comment 9. Please post a comment if this crash comes back. Thanks!
,
Oct 12 2012
This issue has been closed for some time. No one will pay attention to new comments. If you are seeing this bug or have new data, please click New Issue to start a new bug.
,
Mar 10 2013
,
Mar 13 2013
,
Jul 1 2015
Issue 505988 has been merged into this issue. |
|||||||
| ► Sign in to add a comment | |||||||
Status: Assigned