diff options
| author | sail@chromium.org <sail@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-04-06 20:47:09 +0000 |
|---|---|---|
| committer | sail@chromium.org <sail@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-04-06 20:47:09 +0000 |
| commit | e79d7dc73530396c27806a6794f4fcd65262926f (patch) | |
| tree | 4a0b947c47882fb922ecc64a8b6286c3f9396ade /chrome/installer/mini_installer/appid.h | |
| parent | 1299d20ea6f64717b3e66cd96e2e34a42afbffd6 (diff) | |
| download | chromium_src-e79d7dc73530396c27806a6794f4fcd65262926f.zip chromium_src-e79d7dc73530396c27806a6794f4fcd65262926f.tar.gz chromium_src-e79d7dc73530396c27806a6794f4fcd65262926f.tar.bz2 | |
Fix leak in ProfileMenuButtonTest.MenuTest
Valgrind was reporting a leak in -[ProfileMenuDelegate menuWillOpen:].
I wasn't able to reproduce this on my machine with a Debug or Release build.
As a workaround I'm simply removing that part of the test. The test now just checks that popUpContextMenu:withEvent:forView: is called. This is still pretty good since it tests the mouse down code and the pressed state drawing code.
BUG=77910
TEST=Wasn't able to reproduce the same leak but I did get some other leaks in the menu code. Applied my patch and verified that valgrind ran with no errors.
Review URL: http://codereview.chromium.org/6677169
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@80687 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/installer/mini_installer/appid.h')
0 files changed, 0 insertions, 0 deletions