Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(5)

Issue 23651014: Merge "[Resource Timing] Fix potential double free problem" (Closed)

Created:
7 years, 3 months ago by Nate Chapin
Modified:
7 years, 3 months ago
Reviewers:
CC:
blink-reviews, dglazkov+blink, eae+blinkwatch, gavinp+loader_chromium.org
Visibility:
Public.

Description

Merge "[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=157836

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+1 line, -1 line) Patch
M Source/core/loader/cache/ResourceFetcher.cpp View 1 chunk +1 line, -1 line 0 comments Download

Messages

Total messages: 1 (0 generated)
Nate Chapin
7 years, 3 months ago (2013-09-16 17:57:02 UTC) #1
Message was sent while issue was closed.
Committed patchset #1 manually as r157836.

Powered by Google App Engine
This is Rietveld 408576698