Fix DelegatedFrameResourceCollection thread safety

Fix DelegatedFrameResourceCollection thread safety

Don't keep a ref to DelegatedFrameResourceCollection inside the return resources
callback, because it is called from a thread.

BUG=None
R=danakj@chromium.org

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=231915

[danakj, 2013-10-30 16:28:46]

LGTM

weakptr didnt work in the DRLayer, but it does work in the collection since the
RWHV needs to hold onto the collection as long as it wants to return resources
anyway.

[commit-bot: I haz the power, 2013-10-30 16:29:59]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/piman@chromium.org/47703005/1

[piman, 2013-10-30 16:31:12]

On 2013/10/30 16:28:46, danakj wrote:
> LGTM
> 
> weakptr didnt work in the DRLayer, but it does work in the collection since
the
> RWHV needs to hold onto the collection as long as it wants to return resources
> anyway.

Yep, that was my thought. If the client doesn't keep a reference to othe
collection, whether we return the resources into it or not doesn't matter
anymore, since it can't pick them up.

[commit-bot: I haz the power, 2013-10-30 19:15:56]

Retried try job too often on win_rel for step(s) browser_tests
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win_rel&nu...

[commit-bot: I haz the power, 2013-10-30 19:19:10]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/piman@chromium.org/47703005/1

[piman, 2013-10-30 20:35:23]

Committed patchset #1 manually as r231915 (presubmit successful).