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

Unified Diff: base/memory/weak_ptr.h

Issue 7677028: Make WeakPtr thread-safe, i.e. allow cross-thread copying of WeakPtr (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: address comments, add a unit test Created 9 years, 4 months 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
« no previous file with comments | « no previous file | base/memory/weak_ptr.cc » ('j') | base/memory/weak_ptr.cc » ('J')
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: base/memory/weak_ptr.h
diff --git a/base/memory/weak_ptr.h b/base/memory/weak_ptr.h
index abda1af2eaa7e0abf54a9a79bd0d9f7a4a526538..9a39696f2c44e1f8e2ace42927384ab6fffe1cd9 100644
--- a/base/memory/weak_ptr.h
+++ b/base/memory/weak_ptr.h
@@ -45,8 +45,18 @@
// dereferencing the Controller back pointer after the Controller has been
// destroyed.
//
-// WARNING: weak pointers are not threadsafe!!! You must only use a WeakPtr
-// instance on thread where it was created.
+// Thread-safety notes: Weak pointers may only be dereferenced on the thread
darin (slow to review) 2011/08/18 20:29:52 This passage is a bit complicated. I think you mi
+// on which the object being pointed to will be deleted. However, WeakPtr
+// references themselves may be be passed, copied and destroyed across threads.
+// Whenever there are no weak references, the thread on which the first
+// reference is created initializes the thread-safety checks with respect
+// to querying and invalidating the reference.
+// Getting the initial reference and querying HasWeakPtrs()/HasRefs() also
+// should only be done on the owning thread and the user has to avoid races.
+// Again, note that you can however create an object on one thread, and
+// then transfer ownership to another thread on which it will be deleted.
+// When transferring ownership, all previous weak references must first be
+// released.
#ifndef BASE_MEMORY_WEAK_PTR_H_
#define BASE_MEMORY_WEAK_PTR_H_
@@ -69,7 +79,7 @@ class BASE_EXPORT WeakReference {
// via base::WeakPtr::~WeakPtr().
class Flag : public RefCountedThreadSafe<Flag> {
public:
- explicit Flag(Flag** handle);
+ explicit Flag();
void Invalidate();
bool IsValid() const;
@@ -82,17 +92,17 @@ class BASE_EXPORT WeakReference {
~Flag();
ThreadChecker thread_checker_;
- Flag** handle_;
+ bool is_valid_;
};
WeakReference();
- WeakReference(Flag* flag);
+ WeakReference(const Flag* flag);
~WeakReference();
bool is_valid() const;
private:
- scoped_refptr<Flag> flag_;
+ scoped_refptr<const Flag> flag_;
};
class BASE_EXPORT WeakReferenceOwner {
@@ -103,7 +113,7 @@ class BASE_EXPORT WeakReferenceOwner {
WeakReference GetRef() const;
bool HasRefs() const {
- return flag_ != NULL;
+ return flag_.get() && !flag_->HasOneRef();
}
void Invalidate();
@@ -114,7 +124,7 @@ class BASE_EXPORT WeakReferenceOwner {
}
private:
- mutable WeakReference::Flag* flag_;
+ mutable scoped_refptr<WeakReference::Flag> flag_;
};
// This class simplifies the implementation of WeakPtr's type conversion
« no previous file with comments | « no previous file | base/memory/weak_ptr.cc » ('j') | base/memory/weak_ptr.cc » ('J')

Powered by Google App Engine
This is Rietveld 408576698