Revert of Fix leak of RTCPeerConnectionHandler if PeerConnection.close() is called from js.

Revert of Fix leak of RTCPeerConnectionHandler if PeerConnection.close() is called from js. (patchset #3 id:40001 of https://codereview.chromium.org/1438153002/ )

Reason for revert:
Blamed for causing/surfacing a worse bug. Tentatively reverting.

crbug/555575

Original issue's description:
> Fix leak of RTCPeerConnectionHandler if PeerConnection.close() is called from js.
> This fixes a bug where RTCPeerConnectionHandler::client_ is set to null when RTCPeerConnectionHandler.stop() is called.
> RTCPeerConnectionHandler.stop() is a pretty bad name (override from blink::WebRTCPeerConnectionHandler) since it is triggered when JS or the browser process want to close a PeerConnection.
> Since client_ was set to null, RTCPeerConnectionHandler::DestructAllHandlers did not delete RTCPeerConnectionHandler.
>
> BUG=542132
>
> Committed: https://crrev.com/9596af111d9e82b0e27c9fab01fa688515623b1f
> Cr-Commit-Position: refs/heads/master@{#359334}

TBR=tommi@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=542132, 555575
Committed: https://crrev.com/3b988e383919f9d99cc66c3c691342cbc2c1c063
Cr-Commit-Position: refs/heads/master@{#359559}

[perkj_chrome, 2015-11-13 16:19:10]

Created Revert of Fix leak of RTCPeerConnectionHandler if PeerConnection.close()
is called from js.

[perkj_chrome, 2015-11-13 16:19:35]

Description was changed from

==========
Revert of Fix leak of RTCPeerConnectionHandler if PeerConnection.close() is
called from js. (patchset #3 id:40001 of
https://codereview.chromium.org/1438153002/ )

Reason for revert:
Blamed for causing/surfacing a worse bug. Tentatively reverting.

crbug/555575

Original issue's description:
> Fix leak of RTCPeerConnectionHandler if PeerConnection.close() is called from
js.
> This fixes a bug where RTCPeerConnectionHandler::client_ is set to null when
RTCPeerConnectionHandler.stop() is called.
> RTCPeerConnectionHandler.stop() is a pretty bad name (override from
blink::WebRTCPeerConnectionHandler) since it is triggered when JS or the browser
process want to close a PeerConnection.
> Since client_ was set to null, RTCPeerConnectionHandler::DestructAllHandlers
did not delete RTCPeerConnectionHandler.
> 
> BUG=542132
> 
> Committed: https://crrev.com/9596af111d9e82b0e27c9fab01fa688515623b1f
> Cr-Commit-Position: refs/heads/master@{#359334}

TBR=tommi@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=542132
==========

to

==========
Revert of Fix leak of RTCPeerConnectionHandler if PeerConnection.close() is
called from js. (patchset #3 id:40001 of
https://codereview.chromium.org/1438153002/ )

Reason for revert:
Blamed for causing/surfacing a worse bug. Tentatively reverting.

crbug/555575

Original issue's description:
> Fix leak of RTCPeerConnectionHandler if PeerConnection.close() is called from
js.
> This fixes a bug where RTCPeerConnectionHandler::client_ is set to null when
RTCPeerConnectionHandler.stop() is called.
> RTCPeerConnectionHandler.stop() is a pretty bad name (override from
blink::WebRTCPeerConnectionHandler) since it is triggered when JS or the browser
process want to close a PeerConnection.
> Since client_ was set to null, RTCPeerConnectionHandler::DestructAllHandlers
did not delete RTCPeerConnectionHandler.
> 
> BUG=542132
> 
> Committed: https://crrev.com/9596af111d9e82b0e27c9fab01fa688515623b1f
> Cr-Commit-Position: refs/heads/master@{#359334}

TBR=tommi@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=542132,555575
==========

[commit-bot: I haz the power, 2015-11-13 16:19:40]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1442063002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1442063002/1

[commit-bot: I haz the power, 2015-11-13 16:20:40]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-11-13 16:21:14]

Patchset 1 (id:??) landed as
https://crrev.com/3b988e383919f9d99cc66c3c691342cbc2c1c063
Cr-Commit-Position: refs/heads/master@{#359559}