void AddRef() const { #if DCHECK_IS_ON()
DCHECK(!in_dtor_); // This RefCounted object is created with non-zero reference count. // The first reference to such a object has to be made by AdoptRef or // MakeRefCounted.
DCHECK(!needs_adopt_ref_); if (ref_count_ >= 1) {
DCHECK(CalledOnValidSequence());
} #endif
AddRefImpl();
}
// Returns true if the object should self-delete. bool Release() const {
ReleaseImpl();
if (ref_count_ >= 1) {
DCHECK(CalledOnValidSequence());
} if (ref_count_ == 1) {
sequence_checker_.DetachFromSequence();
} #endif
return ref_count_ == 0;
}
// Returns true if it is safe to read or write the object, from a thread // safety standpoint. Should be DCHECK'd from the methods of RefCounted // classes if there is a danger of objects being shared across threads. // // This produces fewer false positives than adding a separate SequenceChecker // into the subclass, because it automatically detaches from the sequence when // the reference count is 1 (and never fails if there is only one reference). // // This means unlike a separate SequenceChecker, it will permit a singly // referenced object to be passed between threads (not holding a reference on // the sending thread), but will trap if the sending thread holds onto a // reference, or if the object is accessed from multiple threads // simultaneously. bool IsOnValidSequence() const { #if DCHECK_IS_ON() return ref_count_ <= 1 || CalledOnValidSequence(); #else returntrue; #endif
}
// Release and AddRef are suitable for inlining on X86 because they generate // very small code sequences. // // ARM64 devices supporting ARMv8.1-A atomic instructions generate very little // code, e.g. fetch_add() with acquire ordering is a single instruction (ldadd), // vs LL/SC in previous ARM architectures. Inline it there as well. // // On other platforms (e.g. ARM), it causes a size regression and is probably // not worth it. #ifdefined(ARCH_CPU_X86_FAMILY) || defined(__ARM_FEATURE_ATOMICS) // Returns true if the object should self-delete. bool Release() const { return ReleaseImpl(); } void AddRef() const { AddRefImpl(); } void AddRefWithCheck() const { AddRefWithCheckImpl(); } #else // Returns true if the object should self-delete. bool Release() const; void AddRef() const; void AddRefWithCheck() const; #endif
ALWAYS_INLINE void AddRefImpl() const { #if DCHECK_IS_ON()
DCHECK(!in_dtor_); // This RefCounted object is created with non-zero reference count. // The first reference to such a object has to be made by AdoptRef or // MakeRefCounted.
DCHECK(!needs_adopt_ref_); #endif
CHECK_NE(ref_count_.Increment(), std::numeric_limits<int>::max());
}
ALWAYS_INLINE void AddRefWithCheckImpl() const { #if DCHECK_IS_ON()
DCHECK(!in_dtor_); // This RefCounted object is created with non-zero reference count. // The first reference to such a object has to be made by AdoptRef or // MakeRefCounted.
DCHECK(!needs_adopt_ref_); #endif int pre_increment_count = ref_count_.Increment();
CHECK_GT(pre_increment_count, 0);
CHECK_NE(pre_increment_count, std::numeric_limits<int>::max());
}
// ScopedAllowCrossThreadRefCountAccess disables the check documented on // RefCounted below for rare pre-existing use cases where thread-safety was // guaranteed through other means (e.g. explicit sequencing of calls across // execution sequences when bouncing between threads in order). New callers // should refrain from using this (callsites handling thread-safety through // locks should use RefCountedThreadSafe per the overhead of its atomics being // negligible compared to locks anyways and callsites doing explicit sequencing // should properly std::move() the ref to avoid hitting this check). // TODO(tzik): Cleanup existing use cases and remove // ScopedAllowCrossThreadRefCountAccess. class BASE_EXPORT ScopedAllowCrossThreadRefCountAccess final { public: #if DCHECK_IS_ON()
ScopedAllowCrossThreadRefCountAccess();
~ScopedAllowCrossThreadRefCountAccess(); #else
ScopedAllowCrossThreadRefCountAccess() {}
~ScopedAllowCrossThreadRefCountAccess() {} #endif
};
// // A base class for reference counted classes. Otherwise, known as a cheap // knock-off of WebKit's RefCounted<T> class. To use this, just extend your // class from it like so: // // class MyFoo : public base::RefCounted<MyFoo> { // ... // private: // friend class base::RefCounted<MyFoo>; // ~MyFoo(); // }; // // Usage Notes: // 1. You should always make your destructor non-public, to avoid any code // deleting the object accidentally while there are references to it. // 2. You should always make the ref-counted base class a friend of your class, // so that it can access the destructor. // // The ref count manipulation to RefCounted is NOT thread safe and has DCHECKs // to trap unsafe cross thread usage. A subclass instance of RefCounted can be // passed to another execution sequence only when its ref count is 1. If the ref // count is more than 1, the RefCounted class verifies the ref updates are made // on the same execution sequence as the previous ones. The subclass can also // manually call IsOnValidSequence to trap other non-thread-safe accesses; see // the documentation for that method. // // // The reference count starts from zero by default, and we intended to migrate // to start-from-one ref count. Put REQUIRE_ADOPTION_FOR_REFCOUNTED_TYPE() to // the ref counted class to opt-in. // // If an object has start-from-one ref count, the first scoped_refptr need to be // created by base::AdoptRef() or base::MakeRefCounted(). We can use // base::MakeRefCounted() to create create both type of ref counted object. // // The motivations to use start-from-one ref count are: // - Start-from-one ref count doesn't need the ref count increment for the // first reference. // - It can detect an invalid object acquisition for a being-deleted object // that has zero ref count. That tends to happen on custom deleter that // delays the deletion. // TODO(tzik): Implement invalid acquisition detection. // - Behavior parity to Blink's WTF::RefCounted, whose count starts from one. // And start-from-one ref count is a step to merge WTF::RefCounted into // base::RefCounted. // #define REQUIRE_ADOPTION_FOR_REFCOUNTED_TYPE() \ using RefCountPreferenceTag = ::base::subtle::StartRefCountFromOneTag
template <class T, typename Traits> class RefCounted;
void Release() const { if (subtle::RefCountedBase::Release()) { // Prune the code paths which the static analyzer may take to simulate // object destruction. Use-after-free errors aren't possible given the // lifetime guarantees of the refcounting system.
ANALYZER_SKIP_THIS_PATH();
// Forward declaration. template <class T, typename Traits> class RefCountedThreadSafe;
// Default traits for RefCountedThreadSafe<T>. Deletes the object when its ref // count reaches 0. Overload to delete it on a different thread etc. template<typename T> struct DefaultRefCountedThreadSafeTraits { staticvoid Destruct(const T* x) { // Delete through RefCountedThreadSafe to make child classes only need to be // friend with RefCountedThreadSafe instead of this struct, which is an // implementation detail.
RefCountedThreadSafe<T,
DefaultRefCountedThreadSafeTraits>::DeleteInternal(x);
}
};
// // A thread-safe variant of RefCounted<T> // // class MyFoo : public base::RefCountedThreadSafe<MyFoo> { // ... // }; // // If you're using the default trait, then you should add compile time // asserts that no one else is deleting your object. i.e. // private: // friend class base::RefCountedThreadSafe<MyFoo>; // ~MyFoo(); // // We can use REQUIRE_ADOPTION_FOR_REFCOUNTED_TYPE() with RefCountedThreadSafe // too. See the comment above the RefCounted definition for details. template <class T, typename Traits = DefaultRefCountedThreadSafeTraits<T> > class RefCountedThreadSafe : public subtle::RefCountedThreadSafeBase { public: using RefCountPreferenceTag = subtle::StartRefCountFromZeroTag;
// // A thread-safe wrapper for some piece of data so we can place other // things in scoped_refptrs<>. // template<typename T> class RefCountedData
: public base::RefCountedThreadSafe< base::RefCountedData<T> > { public:
RefCountedData() : data() {}
RefCountedData(const T& in_value) : data(in_value) {}
RefCountedData(T&& in_value) : data(std::move(in_value)) {} template <typename... Args> explicit RefCountedData(absl::in_place_t, Args&&... args)
: data(std::forward<Args>(args)...) {}
Die Informationen auf dieser Webseite wurden
nach bestem Wissen sorgfältig zusammengestellt. Es wird jedoch weder Vollständigkeit, noch Richtigkeit,
noch Qualität der bereit gestellten Informationen zugesichert.
Bemerkung:
Die farbliche Syntaxdarstellung und die Messung sind noch experimentell.