summaryrefslogtreecommitdiffstats
path: root/net/tools/testserver/run_testserver.cc
diff options
context:
space:
mode:
authorstevenjb@chromium.org <stevenjb@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-09-03 03:05:51 +0000
committerstevenjb@chromium.org <stevenjb@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-09-03 03:05:51 +0000
commit0f247aea86a7b558996df6ad5814ba96d8990c3a (patch)
tree55c1c4aad6067792023fff98c6b8c1ca33a01608 /net/tools/testserver/run_testserver.cc
parent76734d89bfd542ead4a9cb04d75abf34e6c2508c (diff)
downloadchromium_src-0f247aea86a7b558996df6ad5814ba96d8990c3a.zip
chromium_src-0f247aea86a7b558996df6ad5814ba96d8990c3a.tar.gz
chromium_src-0f247aea86a7b558996df6ad5814ba96d8990c3a.tar.bz2
Move HistogramSynchronizer initialization to BrowserMainParts.
This allows HistogramSynchronizer to be released before main_message_loop_ (which it accesses in its destructor). A change that caused BrowserParts to be destroyed explicitly before the end of BrowserMain (and thus before local variable destruction) introduced the associated crash bug. BUG=chromium:95240 TEST=Ensure Chrome exits cleanly (especially on Mac and Windows). Review URL: http://codereview.chromium.org/7832010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99522 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'net/tools/testserver/run_testserver.cc')
0 files changed, 0 insertions, 0 deletions