summaryrefslogtreecommitdiffstats
path: root/net/base/completion_callback.h
diff options
context:
space:
mode:
authoreroman@chromium.org <eroman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-09-22 00:04:59 +0000
committereroman@chromium.org <eroman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-09-22 00:04:59 +0000
commit03a69dcb6cbedb76522854b8bf6bde624d5c8301 (patch)
treeddfae66028127132d1ede834aa57bf1e4a478923 /net/base/completion_callback.h
parente8c927ab11958c3d1d7c768674795bcbc8b67bbb (diff)
downloadchromium_src-03a69dcb6cbedb76522854b8bf6bde624d5c8301.zip
chromium_src-03a69dcb6cbedb76522854b8bf6bde624d5c8301.tar.gz
chromium_src-03a69dcb6cbedb76522854b8bf6bde624d5c8301.tar.bz2
Enable LeakTracker on release builds.
This is intended to be temporary, so we can get data from the dev channel on why URLRequest objects are leaking at shutdown. WARNING: it may cause a slight slowdown on page cycler. Also as part of this change, I switched the order that we check URLFetcher / URLRequest. This is simply so that if both URLFetcher and URLRequest have leaked, we will report the URLFetcher leak rather than the URLRequest leak. BUG=http://crbug.com/21199, http://crbug.com/18372 Review URL: http://codereview.chromium.org/217005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@26765 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'net/base/completion_callback.h')
0 files changed, 0 insertions, 0 deletions