Index: content/browser/renderer_host/render_widget_host_view_aura_unittest.cc |
diff --git a/content/browser/renderer_host/render_widget_host_view_aura_unittest.cc b/content/browser/renderer_host/render_widget_host_view_aura_unittest.cc |
index de4cf01d2961e04ce9830090176ce7443475beee..3a419f28c1563a30606d416cb88ae7022862c8e7 100644 |
--- a/content/browser/renderer_host/render_widget_host_view_aura_unittest.cc |
+++ b/content/browser/renderer_host/render_widget_host_view_aura_unittest.cc |
@@ -444,10 +444,11 @@ class RenderWidgetHostViewAuraTest : public testing::Test { |
base::MemoryPressureListener::MemoryPressureLevel level) { |
// Here should be base::MemoryPressureListener::NotifyMemoryPressure, but |
// since the RendererFrameManager is installing a MemoryPressureListener |
- // which uses ObserverListThreadSafe, which furthermore remembers the |
+ // which uses base::ObserverListThreadSafe, which furthermore remembers the |
// message loop for the thread it was created in. Between tests, the |
// RendererFrameManager singleton survives and and the MessageLoop gets |
- // destroyed. The correct fix would be to have ObserverListThreadSafe look |
+ // destroyed. The correct fix would be to have base::ObserverListThreadSafe |
+ // look |
// up the proper message loop every time (see crbug.com/443824.) |
RendererFrameManager::GetInstance()->OnMemoryPressure(level); |
} |