Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(752)

Issues Search
    My Issues | Starred     Open | Closed | All

Unified Diff: chrome/browser/chrome_thread.cc

Issue 345037: Fifth patch in getting rid of caching MessageLoop pointers. (Closed) Base URL: svn://chrome-svn/chrome/trunk/src/
Patch Set: '' Created 11 years, 1 month ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« chrome/browser/browsing_data_remover.h ('K') | « chrome/browser/chrome_thread.h ('k') | chrome/browser/google_update.cc » ('j') | chrome/browser/renderer_host/resource_dispatcher_host.cc » ('J')
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: chrome/browser/chrome_thread.cc
===================================================================
--- chrome/browser/chrome_thread.cc (revision 30691)
+++ chrome/browser/chrome_thread.cc (working copy)
@@ -54,9 +54,6 @@
// static
bool ChromeThread::CurrentlyOn(ID identifier) {
- // chrome_threads_[identifier] will be NULL if none is running. This is often
- // true when running under unit tests. This behavior actually works out
- // pretty conveniently but it's worth noting here.
AutoLock lock(lock_);
DCHECK(identifier >= 0 && identifier < ID_COUNT);
return chrome_threads_[identifier] &&
« chrome/browser/browsing_data_remover.h ('K') | « chrome/browser/chrome_thread.h ('k') | chrome/browser/google_update.cc » ('j') | chrome/browser/renderer_host/resource_dispatcher_host.cc » ('J')

Powered by Google App Engine
This is Rietveld 408576698