[Resource Timing] Fix potential double free problem

[Resource Timing] Fix potential double free problem

  Currently, ResourceTimingInfoMap in ResourceFetcher releases a 
ResourceTimingInfo after a resource is reported.
  If when blink is in reporting a resource entry, which lead to buffer full and 
immediately invoke "window.stop()" as callback, it will dive into 
ResourceFetcher::didLoadResource again, and release the memory in a nested. 
After that,the outer double free the memory as it just report the entry.
  This patch remove ResourceTiming from map ealier and prevent the double free case.

Contributed by lifeasageek@gmail.com and pan.deng@intel.com

BUG=286414
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=157760

[abarth-chromium, 2013-09-10 16:16:19]

Makes sense to me, but japhet should probably review this CL.

[Nate Chapin, 2013-09-10 19:04:09]

Code change seems reasonable, but I'd like to see the repro from the bug
translated into a layout test if at all possible.

[pan deng, 2013-09-11 03:04:48]

On 2013/09/10 19:04:09, Nate Chapin wrote:
> Code change seems reasonable, but I'd like to see the repro from the bug
> translated into a layout test if at all possible.

A layout test is constructed according to lifeasageek's case, please review.

thanks
Pan

[pan deng, 2013-09-13 01:24:25]

@japhet,

any comments?

thanks
Pan

[Nate Chapin, 2013-09-13 16:19:07]

lgtm

[commit-bot: I haz the power, 2013-09-13 16:19:25]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/pan.deng@chromium.org/23498018/5001

[commit-bot: I haz the power, 2013-09-13 17:04:55]

Change committed as 157760