Support needed to measure user and service traffic in Chrome.

chrome/browser/profiles/profile_manager.cc

Index: chrome/browser/profiles/profile_manager.cc
diff --git a/chrome/browser/profiles/profile_manager.cc b/chrome/browser/profiles/profile_manager.cc
index 1337b660518f900c4762c19bbbc2140b850de314..de946352615a770b42ab8a79712fcfba8e34e5b1 100644
--- a/chrome/browser/profiles/profile_manager.cc
+++ b/chrome/browser/profiles/profile_manager.cc
@@ -459,6 +459,9 @@ void ProfileManager::CreateProfileAsync(
 }
 
 bool ProfileManager::IsValidProfile(Profile* profile) {
+  // The profile_manager() returns NULL when running unit tests.
+  if (!g_browser_process->profile_manager())

[Lei Zhang, 2015/09/02 18:14:43]

Curious, why is this even needed? What happens if you leave the method as it
was?

[amohammadkhan, 2015/09/03 04:31:19]

It was causing segmentation fault in tests. It seems in tests profileManager is
not instantiated, so profiles_info_ in next line should not be reached.

[Lei Zhang, 2015/09/03 04:47:11]

I'm skeptical this is the right thing to do.
ProfileManager::ShutdownSessionServices() is the only other place that checks to
see if a ProfileManager exists, but that's because it dereferences the
ProfileManager pointer. You are not doing that here, so it's not obvious that
this is correct.

Can you be specific about what tests crashed?

[amohammadkhan, 2015/09/03 23:10:35]

ChromeNetworkDelegateTest.DataUseMeasurementUserTest was crashing. This crash
didn't happen in similar tests because they don't attach
content::ResourceRequestInfo to request but this test does. The difference is
that in this function
(https://code.google.com/p/chromium/codesearch#chromium/src/chrome/browser/net...)
other tests return but the crashing test runs BrowserThread::PostTask. 
At first I had used a negative processID and I was checking the processID to see
if its negative to return in that functions but later I changed it later to
current implementation based on checking in ProfileManager because I wasn't sure
that checking for negative processID is a good idea or not.

[Lei Zhang, 2015/09/04 01:18:06]

The right fix is to do the check in the caller, which is
NotifyEPMRequestStatus() in
chrome/browser/net/chrome_extensions_network_delegate.cc, or alternatively, to
create a ProfileManager in your test.

I don't know which is "more correct" so ask the networking code experts.

[amohammadkhan, 2015/09/04 17:25:11]

Done.

+    return false;
   for (ProfilesInfoMap::iterator iter = profiles_info_.begin();
        iter != profiles_info_.end(); ++iter) {
     if (iter->second->created) {