diff options
| author | ananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-06-23 21:21:05 +0000 |
|---|---|---|
| committer | ananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-06-23 21:21:05 +0000 |
| commit | b5fa7fdbad352f5679cc772afd923f74d34456a1 (patch) | |
| tree | 140c83a39b4fe70625e767e97623dd5281053e5a /chrome_frame/function_stub_unittest.cc | |
| parent | fc1926184af3507865502a92b5102e12680b7c21 (diff) | |
| download | chromium_src-b5fa7fdbad352f5679cc772afd923f74d34456a1.zip chromium_src-b5fa7fdbad352f5679cc772afd923f74d34456a1.tar.gz chromium_src-b5fa7fdbad352f5679cc772afd923f74d34456a1.tar.bz2 | |
Ensure that the AtExitManager instance is initialized before the renderer client is initialized in the
ChromeFrame net test suite. This addresses DCHECKs which fire in debug builds making it hard for debugging
test failures.
This CL also ensures that we don't register the browser local state preference twice thus causing dchecks
to fire in debug builds of the chrome frame net test suite.
Other changes include the following:-
1. Turn off the metrics service preference for chrome frame net tests and always return
NULL when asked for the metrics service instance in our implementation of the BrowserProcess
interface
2. Initialize the test timeouts which addresses DCHECKs in debug builds.
With these changes in chrome frame net tests now run in debug builds which should make it easier for
debugging failures.
Fixes bug http://code.google.com/p/chromium/issues/detail?id=87074
BUG=87074
Review URL: http://codereview.chromium.org/7247014
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@90267 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome_frame/function_stub_unittest.cc')
0 files changed, 0 insertions, 0 deletions