diff options
| author | lipalani@chromium.org <lipalani@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-05-05 02:08:19 +0000 |
|---|---|---|
| committer | lipalani@chromium.org <lipalani@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-05-05 02:08:19 +0000 |
| commit | f9486289464b51ffedba0541bf0fbeefc5d53f39 (patch) | |
| tree | 6152f28b4884a303491e70932ae07eb170ddc805 /chrome/browser/ui/collected_cookies_infobar_delegate.cc | |
| parent | a74b92b2c60e0d76db8d08c68377715a2c505a9b (diff) | |
| download | chromium_src-f9486289464b51ffedba0541bf0fbeefc5d53f39.zip chromium_src-f9486289464b51ffedba0541bf0fbeefc5d53f39.tar.gz chromium_src-f9486289464b51ffedba0541bf0fbeefc5d53f39.tar.bz2 | |
Increasing the chance of the race condition bug to occur by disabling logging. VLOG(0) is used only in conditions that are guaranteed to trigger this bug. Other places are now VLOG(1).
There are 2 VLOG(0) that will still print in normal scenario. They are:
1. SyncShare is about to be called.
2. DTM is informing sync configure is done.
I think the above 2 cases are after the bug, meaning the bug happens before either of the above 2 conditions are hit. This will prove that or disprove it.
BUG=
TEST=
Review URL: http://codereview.chromium.org/6933018
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@84194 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/ui/collected_cookies_infobar_delegate.cc')
0 files changed, 0 insertions, 0 deletions