All three SafeBrowsingBlockingQuietPageTests fail under CrOS ASan. Right now unit_tests isn't running on CrOS ASan trybot. I am trying to get unit_tests running on it again and this is blocking that.

GN args:
dcheck_always_on = true
is_asan = true
is_component_build = false
is_debug = false
is_lsan = true
strip_absolute_paths_from_debug_symbols = true
symbol_level = 1
target_os = "chromeos"
use_goma = true

$ export ASAN_OPTIONS="detect_leaks=1 symbolize=1 external_symbolizer_path=./third_party/llvm-build/Release+Asserts/bin/llvm-symbolizer"
$ ninja -C out/asan unit_tests
$ out/asan/unit_tests --gtest_filter=SafeBrowsingBlockingQuietPageTest.*

There ares lots of leaks but I think it all has to do with LocalSafeBrowsingDatabaseManager::database_ not getting deleted? Here is one example.

Indirect leak of 784 byte(s) in 2 object(s) allocated from:
    #0 0xac8572 in operator new(unsigned long) (/usr/local/google/data/chrome/src/out/asan/unit_tests+0xac8572)
    #1 0x16ac9a26 in make_unique<safe_browsing::SafeBrowsingDatabaseNew, const scoped_refptr<base::SequencedTaskRunner> &, safe_browsing::SafeBrowsingStoreFile *, safe_browsing::SafeBrowsingStoreFile *, safe_browsing::SafeBrowsingStoreFile *, safe_browsing::SafeBrowsingStoreFile *, safe_browsing::SafeBrowsingStoreFile *, safe_browsing::SafeBrowsingStoreFile *, safe_browsing::SafeBrowsingStoreFile *, safe_browsing::SafeBrowsingStoreFile *, safe_browsing::SafeBrowsingStoreFile *> buildtools/third_party/libc++/trunk/include/memory:3065:28
    #2 0x16ac9a26 in MakeUnique<safe_browsing::SafeBrowsingDatabaseNew, const scoped_refptr<base::SequencedTaskRunner> &, safe_browsing::SafeBrowsingStoreFile *, safe_browsing::SafeBrowsingStoreFile *, safe_browsing::SafeBrowsingStoreFile *, safe_browsing::SafeBrowsingStoreFile *, safe_browsing::SafeBrowsingStoreFile *, safe_browsing::SafeBrowsingStoreFile *, safe_browsing::SafeBrowsingStoreFile *, safe_browsing::SafeBrowsingStoreFile *, safe_browsing::SafeBrowsingStoreFile *> base/memory/ptr_util.h:25
    #3 0x16ac9a26 in safe_browsing::SafeBrowsingDatabaseFactoryImpl::CreateSafeBrowsingDatabase(scoped_refptr<base::SequencedTaskRunner> const&, bool, bool, bool, bool, bool, bool, bool) chrome/browser/safe_browsing/safe_browsing_database.cc:292
    #4 0x16aa9ce8 in safe_browsing::SafeBrowsingDatabase::Create(scoped_refptr<base::SequencedTaskRunner> const&, bool, bool, bool, bool, bool, bool, bool) chrome/browser/safe_browsing/safe_browsing_database.cc:330:20
    #5 0x16a854e3 in safe_browsing::LocalSafeBrowsingDatabaseManager::GetDatabase() chrome/browser/safe_browsing/local_database_manager.cc:826:52
    #6 0x1092e3e5 in Run base/callback.h:91:12
    #7 0x1092e3e5 in base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*) base/debug/task_annotator.cc:59
    #8 0x10aa9cfb in base::internal::TaskTracker::PerformRunTask(std::__1::unique_ptr<base::internal::Task, std::__1::default_delete<base::internal::Task> >, base::internal::Sequence*) base/task_scheduler/task_tracker.cc:335:28
    #9 0x10aab2a9 in base::internal::TaskTrackerPosix::PerformRunTask(std::__1::unique_ptr<base::internal::Task, std::__1::default_delete<base::internal::Task> >, base::internal::Sequence*) base/task_scheduler/task_tracker_posix.cc:22:16
    #10 0xe3535ca in base::test::ScopedTaskEnvironment::TestTaskTracker::PerformRunTask(std::__1::unique_ptr<base::internal::Task, std::__1::default_delete<base::internal::Task> >, base::internal::Sequence*) base/test/scoped_task_environment.cc:237:49
    #11 0x10aa83ab in base::internal::TaskTracker::RunNextTask(base::internal::Sequence*) base/task_scheduler/task_tracker.cc:251:5
    #12 0x10bc50ac in base::internal::SchedulerWorker::Thread::ThreadMain() base/task_scheduler/scheduler_worker.cc:73:34
    #13 0x10ac20e2 in base::(anonymous namespace)::ThreadFunc(void*) base/threading/platform_thread_posix.cc:75:13
    #14 0x7f5426b4d183 in start_thread /build/eglibc-SvCtMH/eglibc-2.19/nptl/pthread_create.c:312

+edwardjung can you help triage? It looks like |database_| is supposed to be destroyed on another thread but I'm not sure how that interacts with the tests.