summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorjcampan@chromium.org <jcampan@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2008-11-27 01:44:44 +0000
committerjcampan@chromium.org <jcampan@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2008-11-27 01:44:44 +0000
commit9501428d2c774b2d78680c756fdb7edbc87a2f38 (patch)
tree6864d2d965ca9da39066bc8ee737631752ef2475
parent79b80c9a333b60ea08cecbf018a1bd4f8f630c39 (diff)
downloadchromium_src-9501428d2c774b2d78680c756fdb7edbc87a2f38.zip
chromium_src-9501428d2c774b2d78680c756fdb7edbc87a2f38.tar.gz
chromium_src-9501428d2c774b2d78680c756fdb7edbc87a2f38.tar.bz2
Reenabling a DCHECK that was causing the ui tests to hang on the dbg build bots, which I could not reproduce locally.
I'll try to investigate on the bots. TBR=nsylvain Review URL: http://codereview.chromium.org/10979 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@6091 0039d316-1c4b-4281-b951-d872f2087c98
-rw-r--r--chrome/browser/tab_contents.cc4
1 files changed, 1 insertions, 3 deletions
diff --git a/chrome/browser/tab_contents.cc b/chrome/browser/tab_contents.cc
index faabb54..ebd8f2b 100644
--- a/chrome/browser/tab_contents.cc
+++ b/chrome/browser/tab_contents.cc
@@ -76,9 +76,7 @@ void TabContents::CloseContents() {
}
void TabContents::Destroy() {
- // TODO(jcampan): reenable that DCHECK. It seems to cause the RendererCrash
- // ui tests to hang for some unclear reason.
- // DCHECK(!is_being_destroyed_);
+ DCHECK(!is_being_destroyed_);
is_being_destroyed_ = true;
// First cleanly close all child windows.