Autofill heapcheck and valgrind leak in PersonalDataManager unit test fixed

tools/heapcheck/suppressions.txt

 # There are three kinds of suppressions in this file.
 # 1. third party stuff we have no control over
 #
 # 2. intentional unit test errors, or stuff that is somehow a false positive
 # in our own code, or stuff that is so trivial it's not worth fixing
 #
 # 3. Suppressions for real chromium bugs that are not yet fixed.
 # These should all be in chromium's bug tracking system (but a few aren't yet).
 # Periodically we should sweep this file and the bug tracker clean by
 # running overnight and removing outdated bugs/suppressions.
@@ skipping 1036 matching lines @@
    Heapcheck:Leak
    fun:base::BaseTimer::Start
    fun:ReloadButtonGtk::OnClicked
    fun:ReloadButtonGtk::OnClickedThunk
    fun:g_closure_invoke
    fun:ReloadButtonGtkTest_*_Test::TestBody
    fun:testing::HandleExceptionsInMethodIfSupported
    fun:testing::Test::Run
 }
 {
-   bug_61988_a
-   Heapcheck:Leak
-   ...
-   fun:PersonalDataManagerTest_Refresh_Test::TestBody
-}
-{
-   bug_61988_b
-   Heapcheck:Leak
-   ...
-   fun:TestingProfile::CreateWebDataService
-}
-{
    bug_62078
    Heapcheck:Leak
    fun:__gnu_cxx::new_allocator::allocate
    fun:std::string::_Rep::_S_create
    fun:std::string::_S_construct
    fun:std::string::_S_construct_aux
    fun:std::string::_S_construct
    fun:basic_string
    fun:remoting::protocol::JingleSession::OnInitiate
    fun:remoting::protocol::JingleSession::OnSessionState
    fun:sigslot::_connection2::emit
    fun:sigslot::signal2::operator
    fun:cricket::BaseSession::SetState
    fun:cricket::Session::OnInitiateMessage
    fun:cricket::Session::OnIncomingMessage
    fun:cricket::SessionManager::OnIncomingMessage
    fun:remoting::SessionManagerPair::DeliverMessage
    fun:remoting::SessionManagerPair::DoProcessMessage
    ...
    fun:remoting::JingleThread::JingleMessagePump::OnMessage
 }