diff options
| author | phajdan.jr@chromium.org <phajdan.jr@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-11-19 09:11:39 +0000 |
|---|---|---|
| committer | phajdan.jr@chromium.org <phajdan.jr@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-11-19 09:11:39 +0000 |
| commit | 4ea927b886af2654b5a193278c0bfb6c25b56fc7 (patch) | |
| tree | 81c0a1916e2b683b687ed6538386fcdbc9261c11 /chrome/common/chrome_constants.cc | |
| parent | d10852ddcea9285a2808a1fa0caeddf4c5e221e0 (diff) | |
| download | chromium_src-4ea927b886af2654b5a193278c0bfb6c25b56fc7.zip chromium_src-4ea927b886af2654b5a193278c0bfb6c25b56fc7.tar.gz chromium_src-4ea927b886af2654b5a193278c0bfb6c25b56fc7.tar.bz2 | |
Isolate tests by running AtExit callbacks between them.
For now, this is only for base_unittests. The plan is to enable
it for all unit tests. This should finally fix mysterious
problems cause by Singletons surviving after one test etc.
This change also adapts LazyInstance so that it can be reused
after being destroyed. It is used very frequently, for example
each time a MessageLoop is used. It is also worth noting that
we had some problems in the past related to the MessageLoop
being destroyed and re-instantiated in the same test executable.
This patch should also fix that.
TEST=none
BUG=12710
Review URL: http://codereview.chromium.org/372057
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@32507 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/common/chrome_constants.cc')
0 files changed, 0 insertions, 0 deletions