summaryrefslogtreecommitdiffstats
path: root/ipc/ipc_channel_win.cc
diff options
context:
space:
mode:
authortommi@chromium.org <tommi@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2014-01-21 14:29:36 +0000
committertommi@chromium.org <tommi@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2014-01-21 14:29:36 +0000
commit88ecb5f5a813ea3e34a27228fb696aedf2d53838 (patch)
tree6bf48c3a6ec27a8b4e44c13d680b551470853236 /ipc/ipc_channel_win.cc
parentf6972deced0113df0a55ab33ebd3639ac87bc3f1 (diff)
downloadchromium_src-88ecb5f5a813ea3e34a27228fb696aedf2d53838.zip
chromium_src-88ecb5f5a813ea3e34a27228fb696aedf2d53838.tar.gz
chromium_src-88ecb5f5a813ea3e34a27228fb696aedf2d53838.tar.bz2
Changing a DCHECK to a CHECK in order to catch this error in release builds.
I managed to hit this problem locally by following reproduction steps in bug 335031. My guess is that this might be causing data corruption and several so-far unexplained crashes, so I think that a reasonable first step is to upgrade the DCHECK to a CHECK. Committing as TBR to get this in asap. BUG=335031 TBR=agl@chromium.org NOTRY=True Review URL: https://codereview.chromium.org/143443002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@246036 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'ipc/ipc_channel_win.cc')
-rw-r--r--ipc/ipc_channel_win.cc2
1 files changed, 1 insertions, 1 deletions
diff --git a/ipc/ipc_channel_win.cc b/ipc/ipc_channel_win.cc
index 418e8cb..d044ef1 100644
--- a/ipc/ipc_channel_win.cc
+++ b/ipc/ipc_channel_win.cc
@@ -372,7 +372,7 @@ bool Channel::ChannelImpl::ProcessOutgoingMessages(
return false;
}
// Message was sent.
- DCHECK(!output_queue_.empty());
+ CHECK(!output_queue_.empty());
Message* m = output_queue_.front();
output_queue_.pop();
delete m;