Suppress some Dr. Memory INVALID HEAP reports on UI tests

tools/valgrind/drmemory/suppressions.txt

 ############################
 # Known reports on the third party we have no control over.
 UNINITIALIZED READ
 ...
 *!deflate_*
 *!MOZ_Z_deflate
 
 # http://code.google.com/p/drmemory/issues/detail?id=406
 # TODO(timurrrr): check if these frames change when NT_SYMBOLS are present.
 LEAK
@@ skipping 586 matching lines @@
 UNINITIALIZED READ
 ntdll.dll!RtlpNtOpenKey
 ntdll.dll!RtlMakeSelfRelativeSD
 ntdll.dll!RtlAbsoluteToSelfRelativeSD
 ADVAPI32.dll!MakeSelfRelativeSD
 
 UNINITIALIZED READ
 ...
 CRYPT32.dll!I_CertSyncStore
 
+INVALID HEAP ARGUMENT
+name=http://crbug.com/103365
+ppapi_tests.dll!*

[Derek Bruening, 2011/11/08 15:29:24]

how do you know this isn't a false positive?  were the drmem bits checked in to
3rd-party ever rolled back or is this using the broken drmem?

[Timur Iskhodzhanov, 2011/11/08 15:48:18]

It's on r579 you've pushed.
FP or not these guys happen very often on ui_tests and make it hard to find
other stuff.
After all, I've added it to "investigate this" section.

+...
+ppapi_tests.dll!*
+base::internal::Invoker2<*>::DoInvoke
+
 ############################
 # Intentional errors in Chromium tests (ToolsSanityTests)
 LEAK
 name=sanity test 01 (memory leak)
 base_unittests.exe!operator new
 base_unittests.exe!operator new[]
 base_unittests.exe!base::ToolsSanityTest_MemoryLeak_Test::TestBody
 
 # "..." is needed due to http://code.google.com/p/drmemory/issues/detail?id=666
 UNADDRESSABLE ACCESS
@@ skipping 157 matching lines @@
 *!scoped_ptr<_TOKEN_USER>*
 
 INVALID HEAP ARGUMENT
 name=http://crbug.com/101717 (1)
 *!scoped_ptr<_TOKEN_DEFAULT_DACL>*
 
 INVALID HEAP ARGUMENT
 name=http://crbug.com/101717 (2)
 *!sandbox::PolicyBase::~PolicyBase
 
+INVALID HEAP ARGUMENT
+name=http://crbug.com/101717 (3)
+*!scoped_ptr<_UNICODE_STRING>::~scoped_ptr<_UNICODE_STRING>
+*!sandbox::GetHandleName
+
+INVALID HEAP ARGUMENT
+name=http://crbug.com/101717 (4)
+*!scoped_ptr<_OBJECT_NAME_INFORMATION>::~scoped_ptr<_OBJECT_NAME_INFORMATION>
+*!sandbox::GetPathFromHandle
+
 ############################
 # Real issues in Chromium
 
 # http://crbug.com/32085
 LEAK
 ...
 chrome.dll!NotificationRegistrar::Add
 
 # http://crbug.com/32623
 LEAK
@@ skipping 117 matching lines @@
 *!operator new
 *!views::NativeWidgetWin::OnCreate
 
 # http://crbug.com/96010
 UNADDRESSABLE ACCESS
 ...
 *!NotificationService::Notify
 
 # Empty line at EOF - workaround for
 # http://code.google.com/p/drmemory/issues/detail?id=41