Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(5472)

Unified Diff: chrome/browser/sessions/tab_loader_unittest.cc

Issue 2565323002: Stop using callbacks in MemoryCoordinatorProxy (Closed)
Patch Set: fix Created 4 years ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: chrome/browser/sessions/tab_loader_unittest.cc
diff --git a/chrome/browser/sessions/tab_loader_unittest.cc b/chrome/browser/sessions/tab_loader_unittest.cc
index 3f7aae7be0eabfa0b9cd975a80e40604e5265506..79058dbadcbf04d31fc722850ad8d7b5c68bba49 100644
--- a/chrome/browser/sessions/tab_loader_unittest.cc
+++ b/chrome/browser/sessions/tab_loader_unittest.cc
@@ -62,7 +62,7 @@ class TabLoaderTest : public testing::Test {
TEST_F(TabLoaderTest, MAYBE_OnMemoryStateChange) {
TabLoader::RestoreTabs(restored_tabs_, base::TimeTicks());
EXPECT_TRUE(TabLoader::shared_tab_loader_->loading_enabled_);
- base::MemoryCoordinatorProxy::GetInstance()->SetCurrentMemoryStateForTesting(
+ base::MemoryCoordinatorProxy::GetInstance()->SetMemoryStateForTesting(
base::MemoryState::THROTTLED);
// ObserverListThreadsafe is used to notify the state to clients, so running
// the loop is necessary here.

Powered by Google App Engine
This is Rietveld 408576698