Index: content/browser/ssl/ssl_error_handler.cc |
diff --git a/content/browser/ssl/ssl_error_handler.cc b/content/browser/ssl/ssl_error_handler.cc |
index e3eceabddc6fdc51013e0f3da97ad09c0a3a8b8b..fc448382508dac17d340215892312d6ff8ae7ace 100644 |
--- a/content/browser/ssl/ssl_error_handler.cc |
+++ b/content/browser/ssl/ssl_error_handler.cc |
@@ -135,7 +135,7 @@ void SSLErrorHandler::CompleteCancelRequest(int error) { |
net::URLRequest* request = |
resource_dispatcher_host_->GetURLRequest(request_id_); |
- if (request) { |
+ if (request && request->is_pending()) { |
darin (slow to review)
2012/02/27 19:26:25
oh, hmm...
have you considered cancelling the req
tpayne
2012/02/27 19:30:51
I haven't seen any instances where the request had
wtc
2012/02/28 20:02:12
tpayne: do you know why the request may be not pen
tpayne
2012/02/28 21:53:58
The state that is causing the flakiness is request
tpayne
2012/02/29 01:15:11
The original cancel is occurring with this stack:
tpayne
2012/02/29 01:58:24
One more level up, it turns out that NavigateToPen
|
// The request can be NULL if it was cancelled by the renderer (as the |
// result of the user navigating to a new page from the location bar). |
DVLOG(1) << "CompleteCancelRequest() url: " << request->url().spec(); |