tree 67c05c8e4649820e4f4a4868054cc5cdae67ef95
parent bb9dd07499bade5030acdb1f7735c81eb542bd23
author jam@chromium.org <jam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> 1257142230 +0900
committer Qijiang Fan <fqj@google.com> 1591232446 +0900

Add the ability for objects which derive from RefCountedThreadSafe to specify a destructor trait.  This allows browser objects to specify which thread they're terminated on.  The benefit is we avoid the need to do manual ref counting when an object posts tasks to itself on different threads, if an object must be destructed on a specific thread.

This patch adds initial support and only shows one example with ResourceMessageFilter.  I will do the rest in a follow-up patch to keep things small.

BUG=25354
TEST=added unit tests
Review URL: http://codereview.chromium.org/338065

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@30688 0039d316-1c4b-4281-b951-d872f2087c98


CrOS-Libchrome-Original-Commit: f671062f8c572d6729173c4ac7f058a1a89b5a1d