CookieStore: Remove reference counting.

net/url_request/url_request_http_job_unittest.cc

Index: net/url_request/url_request_http_job_unittest.cc
diff --git a/net/url_request/url_request_http_job_unittest.cc b/net/url_request/url_request_http_job_unittest.cc
index a6fc7eb720532d16b7336e0ee43b5b5561143935..5cef19cf979177c387750d021cce9acb40e3151e 100644
--- a/net/url_request/url_request_http_job_unittest.cc
+++ b/net/url_request/url_request_http_job_unittest.cc
@@ -544,7 +544,8 @@ TEST_F(URLRequestHttpJobWithMockSocketsTest, BackoffHeaderCachedResponse) {
 }
 
 TEST_F(URLRequestHttpJobTest, TestCancelWhileReadingCookies) {
-  context_.set_cookie_store(new DelayedCookieMonster());
+  DelayedCookieMonster cookie_monster;
+  context_.set_cookie_store(&cookie_monster);

[Randy Smith (Not in Mondays), 2016/03/01 20:48:43]

Same issue mentioned elsewhere about a context raw pointer outliving the object
pointed to (by a little bit).  I'm inclined to suggest that you set the cookie
store to null (or save the pointer and reset it) in this routine, since I think
of the destructor of the URLRequestContext likely being more stable than the
destructor of a random test class.  

[mmenke, 2016/03/01 22:44:45]

What I think is uglier than the lifetime issue here is that we're modifying a
"live" URLRequestContext, after initialization.  I'd really like the
TestURLRequestContext to be able to take ownership of stuff, before we call its
initialization function, so it can wire everything up as needed.

Anyhow, I addressed both issues by just creating a new TestURLRequestContext for
this test.

 
   TestDelegate delegate;
   scoped_ptr<URLRequest> request = context_.CreateRequest(