summaryrefslogtreecommitdiffstats
path: root/ipc/ipc_logging.cc
diff options
context:
space:
mode:
authordarin@chromium.org <darin@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-09-28 18:12:55 +0000
committerdarin@chromium.org <darin@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-09-28 18:12:55 +0000
commit13f383ff5fc8ff095501794d4ce758f0067ff9b5 (patch)
treeceb1d08f38759bf8805ede009924a990bae496e5 /ipc/ipc_logging.cc
parentf61f331824ac9c98684a886be0d918aefe69d3ce (diff)
downloadchromium_src-13f383ff5fc8ff095501794d4ce758f0067ff9b5.zip
chromium_src-13f383ff5fc8ff095501794d4ce758f0067ff9b5.tar.gz
chromium_src-13f383ff5fc8ff095501794d4ce758f0067ff9b5.tar.bz2
Assert that thread-safe reference counting is used with
cross-thread NewRunnableMethod. This assertion caught such an error in VisitedLinkMaster! My approach, modify RunnableMethodTraits<T> to assert that when ReleaseCallee happens on a different thread from RetainCallee that the type supports thread-safe reference counting. I do this by adding a static method to both RefCounted<T> and RefCountedThreadSafe<T>. This results in a little ugliness in cases where people implement AddRef and Release by hand (to make the no-ops). There may be a nicer way to deal with those few cases. R=brettw BUG=none TEST=none Review URL: http://codereview.chromium.org/251012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@27379 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'ipc/ipc_logging.cc')
-rw-r--r--ipc/ipc_logging.cc4
1 files changed, 2 insertions, 2 deletions
diff --git a/ipc/ipc_logging.cc b/ipc/ipc_logging.cc
index 9d4f4bb..e1684d7 100644
--- a/ipc/ipc_logging.cc
+++ b/ipc/ipc_logging.cc
@@ -36,8 +36,8 @@ using base::Time;
// special retention program.
template <>
struct RunnableMethodTraits<IPC::Logging> {
- static void RetainCallee(IPC::Logging*) {}
- static void ReleaseCallee(IPC::Logging*) {}
+ void RetainCallee(IPC::Logging*) {}
+ void ReleaseCallee(IPC::Logging*) {}
};
namespace IPC {