memory coordinator: Purge memory under memory pressure

chrome/browser/memory/tab_manager.cc

Index: chrome/browser/memory/tab_manager.cc
diff --git a/chrome/browser/memory/tab_manager.cc b/chrome/browser/memory/tab_manager.cc
index 0cccbee9985264351bcb30aad2ee17f8b6d826cf..49ebd34b6481bc4dd0dd0e93f537fa7453409e31 100644
--- a/chrome/browser/memory/tab_manager.cc
+++ b/chrome/browser/memory/tab_manager.cc
@@ -361,15 +361,15 @@ bool TabManager::CanDiscardTab(int64_t target_web_contents_id) const {
   return true;
 }
 
-void TabManager::DiscardTab() {
+bool TabManager::DiscardTab() {
 #if defined(OS_CHROMEOS)
   // Call Chrome OS specific low memory handling process.
   if (base::FeatureList::IsEnabled(features::kArcMemoryManagement)) {
     delegate_->LowMemoryKill(GetUnsortedTabStats());
-    return;
+    return false;

[haraken, 2017/03/24 11:55:38]

Does this mean that the tab discarding not working on Chrome OS?

[bashi, 2017/03/28 03:15:30]

Sorry I didn't check the implementation of LowMemoryKill(). It seems that it may
synchronously/asynchronously discard a tab or kill a process. At this point we
can't check if it does something (tab discarding / killing process).

Probably we should take another approach and I'll try to figure it out.

   }
 #endif
-  DiscardTabImpl();
+  return DiscardTabImpl() != nullptr;
 }
 
 WebContents* TabManager::DiscardTabById(int64_t target_web_contents_id) {