ozone: Introduce ClientPixmap and ClientPixmapFactory for non-GPU processes.

ui/ozone/public/ozone_platform.cc

Index: ui/ozone/public/ozone_platform.cc
diff --git a/ui/ozone/public/ozone_platform.cc b/ui/ozone/public/ozone_platform.cc
index b69bc28927d76d800321b2f58b2c26c66759d21d..76248cbfc721dfb46e201ea102b55a8d4554fec6 100644
--- a/ui/ozone/public/ozone_platform.cc
+++ b/ui/ozone/public/ozone_platform.cc
@@ -8,6 +8,7 @@
 #include "ui/events/devices/device_data_manager.h"
 #include "ui/ozone/platform_object.h"
 #include "ui/ozone/platform_selection.h"
+#include "ui/ozone/public/native_pixmap_client.h"
 #include "ui/ozone/public/ozone_platform.h"
 #include "ui/ozone/public/ozone_switches.h"
 
@@ -42,6 +43,8 @@ void OzonePlatform::InitializeForUI() {
   // This is deliberately created after initializing so that the platform can
   // create its own version of DDM.
   DeviceDataManager::CreateInstance();
+
+  NativePixmapClient::InitializeIfNeeded();

[dshwang, 2015/06/03 14:11:51]

Browser process always initializes it unlike Renderer.

[spang, 2015/06/05 19:21:54]

Why does the browser need it? Is there a case where GPU memory buffers are
mapped in the browser?

[reveman, 2015/06/05 20:26:07]

The UI compositor.

 }
 
 // static