diff options
| author | satorux@chromium.org <satorux@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-09-13 17:42:33 +0000 |
|---|---|---|
| committer | satorux@chromium.org <satorux@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-09-13 17:42:33 +0000 |
| commit | ffe4e4dc5e0dc0d28c2ede0ebfed35f5999597cc (patch) | |
| tree | fa599b6aaedb776c4c96438139aa046df6cecd0f /ppapi/proxy/interface_proxy.cc | |
| parent | 440a0e59fefc3f2fd62fcc836b8c824aa5e2ea43 (diff) | |
| download | chromium_src-ffe4e4dc5e0dc0d28c2ede0ebfed35f5999597cc.zip chromium_src-ffe4e4dc5e0dc0d28c2ede0ebfed35f5999597cc.tar.gz chromium_src-ffe4e4dc5e0dc0d28c2ede0ebfed35f5999597cc.tar.bz2 | |
Loosen the suppression pattern for bug_46163.
I ran a ui test (AutomationProxyTest.GetBrowserWindowCount) built for Chromium OS
locally under valgrind and got the following suppression pattern, which does not
include _ZN11MessageLoop10RunHandlerEv at the end.
{
<insert_a_suppression_name_here>
Memcheck:Leak
fun:_Znw*
fun:_ZN4base19MessagePumpLibevent3RunEPNS_11MessagePump8DelegateE
fun:_ZN11MessageLoop11RunInternalEv
}
It seems that _ZN11MessageLoop10RunHandlerEv could be optimzied out
depending on the optimization settings. nkostylev was also seeing the
same issue.
BUG=46163
TEST=run AutomationProxyTest.GetBrowserWindowCount under valgrind locally and confirm that the leak is suppressed.
Review URL: http://codereview.chromium.org/7886015
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@100934 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'ppapi/proxy/interface_proxy.cc')
0 files changed, 0 insertions, 0 deletions