Revert of Fixing potential AsyncInvoker deadlock that occurs for "reentrant" invocations.

Revert of Fixing potential AsyncInvoker deadlock that occurs for "reentrant" invocations. (patchset #3 id:40001 of https://codereview.webrtc.org/2885143006/ )

Reason for revert:
Causes a new TSan race warning. Will reland after fixing. Note this is the same race as will be fixed by https://codereview.webrtc.org/2876273002/.

Original issue's description:
> Fixing potential AsyncInvoker deadlock that occurs for "reentrant" invocations.
> 
> The deadlock occurs if the AsyncInvoker is destroyed on thread A while
> a task on thread B is running, which AsyncInvokes a task back on thread
> A.
> 
> This was causing pending_invocations_ to end up negative, because
> an AsyncClosure that's never added to a thread's message queue (due to
> the "destroying_" flag) caused the count to be decremented but not
> incremented.
> 
> BUG=None
> 
> Review-Url: https://codereview.webrtc.org/2885143006
> Cr-Commit-Position: refs/heads/master@{#18225}
> Committed: https://chromium.googlesource.com/external/webrtc/+/ef37ca5fb3431864130de3c2fd0ff865f9eb47dd

TBR=nisse@webrtc.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=None

Review-Url: https://codereview.webrtc.org/2904543003
Cr-Commit-Position: refs/heads/master@{#18248}
Committed: https://chromium.googlesource.com/external/webrtc/+/aea9293fd45bced832862d544f34888c07d7bf65

[Taylor Brandstetter, 2017-05-23 19:54:53]

The CQ bit was checked by deadbeef@webrtc.org

[Taylor Brandstetter, 2017-05-23 19:54:54]

Created Revert of Fixing potential AsyncInvoker deadlock that occurs for
"reentrant" invocations.

[commit-bot: I haz the power, 2017-05-23 19:54:58]

CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.webrtc.org/...

[commit-bot: I haz the power, 2017-05-23 19:55:03]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1495569293510150, "parent_rev":
"b34f6a8520de5e4813e7f3e7cd2d2d7cb7d8c01f", "commit_rev":
"aea9293fd45bced832862d544f34888c07d7bf65"}

[commit-bot: I haz the power, 2017-05-23 19:55:07]

Description was changed from

==========
Revert of Fixing potential AsyncInvoker deadlock that occurs for "reentrant"
invocations. (patchset #3 id:40001 of https://codereview.webrtc.org/2885143006/
)

Reason for revert:
Causes a new TSan race warning. Will reland after fixing. Note this is the same
race as will be fixed by https://codereview.webrtc.org/2876273002/.

Original issue's description:
> Fixing potential AsyncInvoker deadlock that occurs for "reentrant"
invocations.
> 
> The deadlock occurs if the AsyncInvoker is destroyed on thread A while
> a task on thread B is running, which AsyncInvokes a task back on thread
> A.
> 
> This was causing pending_invocations_ to end up negative, because
> an AsyncClosure that's never added to a thread's message queue (due to
> the "destroying_" flag) caused the count to be decremented but not
> incremented.
> 
> BUG=None
> 
> Review-Url: https://codereview.webrtc.org/2885143006
> Cr-Commit-Position: refs/heads/master@{#18225}
> Committed:
https://chromium.googlesource.com/external/webrtc/+/ef37ca5fb3431864130de3c2f...

TBR=nisse@webrtc.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=None
==========

to

==========
Revert of Fixing potential AsyncInvoker deadlock that occurs for "reentrant"
invocations. (patchset #3 id:40001 of https://codereview.webrtc.org/2885143006/
)

Reason for revert:
Causes a new TSan race warning. Will reland after fixing. Note this is the same
race as will be fixed by https://codereview.webrtc.org/2876273002/.

Original issue's description:
> Fixing potential AsyncInvoker deadlock that occurs for "reentrant"
invocations.
> 
> The deadlock occurs if the AsyncInvoker is destroyed on thread A while
> a task on thread B is running, which AsyncInvokes a task back on thread
> A.
> 
> This was causing pending_invocations_ to end up negative, because
> an AsyncClosure that's never added to a thread's message queue (due to
> the "destroying_" flag) caused the count to be decremented but not
> incremented.
> 
> BUG=None
> 
> Review-Url: https://codereview.webrtc.org/2885143006
> Cr-Commit-Position: refs/heads/master@{#18225}
> Committed:
https://chromium.googlesource.com/external/webrtc/+/ef37ca5fb3431864130de3c2f...

TBR=nisse@webrtc.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=None

Review-Url: https://codereview.webrtc.org/2904543003
Cr-Commit-Position: refs/heads/master@{#18248}
Committed:
https://chromium.googlesource.com/external/webrtc/+/aea9293fd45bced832862d544...
==========

[commit-bot: I haz the power, 2017-05-23 19:55:08]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/external/webrtc/+/aea9293fd45bced832862d544...