summaryrefslogtreecommitdiffstats
path: root/base/file_util_unittest.cc
diff options
context:
space:
mode:
authorerg@google.com <erg@google.com@0039d316-1c4b-4281-b951-d872f2087c98>2010-07-01 23:16:16 +0000
committererg@google.com <erg@google.com@0039d316-1c4b-4281-b951-d872f2087c98>2010-07-01 23:16:16 +0000
commit087265a55269a513eb9e0f9d6410374296829873 (patch)
tree26d3c5ad205ee1ad939f69d22d28e1054b749313 /base/file_util_unittest.cc
parentd9344f42fd5240fc0920905ea48d83b65b9c3965 (diff)
downloadchromium_src-087265a55269a513eb9e0f9d6410374296829873.zip
chromium_src-087265a55269a513eb9e0f9d6410374296829873.tar.gz
chromium_src-087265a55269a513eb9e0f9d6410374296829873.tar.bz2
Reland r51414: "GTK: Fix sorting in content exception window."
Don't use scoped_ptr in unit test. Manually delete the dailog (which deletes ContentExceptionsWindowGtk.) First Review URL: http://codereview.chromium.org/2876032 BUG=47841 TEST=ContentExceptionsWindowGtkUnittest.* + see bug. Ran valgrind on several gtk tests including new ones and fixed the memory errors. Review URL: http://codereview.chromium.org/2881009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@51450 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'base/file_util_unittest.cc')
0 files changed, 0 insertions, 0 deletions