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

Issue 6681040: Prevent memory leak for ChromeContentBrowserClient. (Closed)

Created:
9 years, 9 months ago by Charlie Reis
Modified:
9 years, 7 months ago
Reviewers:
jam
CC:
chromium-reviews, jam, brettw-cc_chromium.org, Paweł Hajdan Jr., dhollowa
Visibility:
Public.

Description

Prevent memory leak for ChromeContentBrowserClient. BUG=none TEST=Memory tests / Heapcheck Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=78101

Patch Set 1 #

Patch Set 2 : Fix BrowserWithTestWindowTest. #

Patch Set 3 : Let ContentClient own browser client. #

Unified diffs Side-by-side diffs Delta from patch set Stats (+8 lines, -3 lines) Patch
M chrome/test/browser_with_test_window_test.cc View 1 2 3 chunks +4 lines, -0 lines 0 comments Download
M content/common/content_client.h View 1 2 3 chunks +4 lines, -3 lines 0 comments Download

Messages

Total messages: 5 (0 generated)
Charlie Reis
9 years, 9 months ago (2011-03-14 18:17:08 UTC) #1
Charlie Reis
Second round of memory leak fix. Had to update BrowserWithTestWindowTest to get BrowserCommandsTest et all ...
9 years, 9 months ago (2011-03-14 19:04:59 UTC) #2
jam
nit: why not just make ContentClient own the pointer?
9 years, 9 months ago (2011-03-14 19:22:51 UTC) #3
Charlie Reis
On 2011/03/14 19:22:51, John Abd-El-Malek wrote: > nit: why not just make ContentClient own the ...
9 years, 9 months ago (2011-03-14 19:35:10 UTC) #4
jam
9 years, 9 months ago (2011-03-14 19:36:52 UTC) #5
lgtm

Powered by Google App Engine
This is Rietveld 408576698