Fixed crash on double profile delete operation.

chrome/browser/browsing_data/browsing_data_remover.cc

Index: chrome/browser/browsing_data/browsing_data_remover.cc
diff --git a/chrome/browser/browsing_data/browsing_data_remover.cc b/chrome/browser/browsing_data/browsing_data_remover.cc
index 05e0c2ed9b5fbccdb5183b0ba7a45ce8a5c9e7be..a42288e09dd368c27066f0345e6ebb8c3213cbd6 100644
--- a/chrome/browser/browsing_data/browsing_data_remover.cc
+++ b/chrome/browser/browsing_data/browsing_data_remover.cc
@@ -354,6 +354,8 @@ void BrowsingDataRemover::SetRemoving(bool is_removing) {
 void BrowsingDataRemover::Remove(const TimeRange& time_range,
                                  int remove_mask,
                                  int origin_type_mask) {
+  if (is_removing_)

[Bernhard Bauer, 2016/05/05 10:06:47]

I'm not sure if silently returning is the right thing to do here. We should
disable UI that allows clearing browsing data while that is in progress, and
then DCHECK that we are not trying to clear data twice (which already happens in
SetRemoving()).

The same probably goes for profile deletion --
ProfileManager::ScheduleProfileForDeletion() and/or
ScheduleQueueProfileDirectoryForDeletion should DCHECK that the profile isn't
already scheduled for deletion, and deleting a profile should disable the UI
while that is in progress.

+    return;
   // Any instance of BrowsingDataFilterBuilder that |IsEmptyBlacklist()|
   // is OK to pass here.
   RegistrableDomainFilterBuilder builder(