Revert of Revalidate using the same Resource, attempt #3 (patchset #2 id:20001 of https://codereview.chromium.org/1398523004/ )
Reason for revert:
Seems to have caused assertion failures on http://build.chromium.org/p/chromium.gpu/builders/Android%20Debug%20%28Nexus%206%29?numbuilds=200 as described on the original CL.
Original issue's description:
> Revalidate using the same Resource, attempt #3
>
> Currently, when we perform a revalidation, we create a new resource and put it in the MemoryCache in place of the resource being revalidated. If the revalidation results in a 304, we silently swap all of the clients of the revalidation to the now-revalidated resource and swap which Resource is in the MemoryCache.
>
> This changes the behavior to use the existing resource to revalidate itself, which simplifies the logic quite a bit. It also gives us the option of removing ResourcePtr (which is used to implement the silent client swap in the 304 case) and make Resources simply RefCounted in a future change.
>
> BUG=
>
> Committed: https://crrev.com/71adea27213b2268bda765abccd5a3bf9517b860
> Cr-Commit-Position: refs/heads/master@{#354615}
TBR=mkwst@chromium.org,japhet@chromium.org
BUG=
Review URL: https://codereview.chromium.org/1410313002
Cr-Commit-Position: refs/heads/master@{#354721}
14 files changed
