Skip to content
Snippets Groups Projects
  1. Dec 29, 2010
  2. Dec 28, 2010
  3. Dec 23, 2010
  4. Dec 22, 2010
  5. Dec 21, 2010
  6. Dec 18, 2010
    • thakis@chromium.org's avatar
      Remove CrApplication dependency from base · a366880f
      thakis@chromium.org authored
      Add a @protocol CrAppProtocol that clients of base must implement in their NSApplication subclass, and let base depend only on this protocol.
      
      Let MessagePumpNSApplication::DoRun() no longer initialize NSApplication (fixes a TODO).
      
      Add a MockCrApplication that the simple unittests in base and app can use, move chrome_application to chrome/common.
      
      Test shell might run nested run loops, so I gave it a real but simplified CrAppProtocol implementation.
      
      BUG=62968,46929
      TEST=Everything still works. The PDF plugin prints one fewer warning when loaded.
      
      Review URL: http://codereview.chromium.org/5950003
      
      git-svn-id: svn://svn.chromium.org/chrome/trunk/src@69615 0039d316-1c4b-4281-b951-d872f2087c98
      a366880f
  7. Dec 17, 2010
  8. Dec 15, 2010
  9. Dec 14, 2010
  10. Dec 13, 2010
  11. Dec 10, 2010
  12. Dec 09, 2010
  13. Dec 08, 2010
  14. Dec 07, 2010
  15. Dec 06, 2010
  16. Dec 04, 2010
  17. Dec 01, 2010
  18. Nov 30, 2010
  19. Nov 26, 2010
    • kbr@google.com's avatar
      Add flow control between renderer and GPU processes, and, on Mac OS X, · 33da8041
      kbr@google.com authored
      between GPU process and browser process. Thanks to Al Patrick for the
      renderer<->GPU flow control mechanism.
      
      This CL prevents the renderer from issuing more OpenGL work than the
      GPU process can execute, and, on the Mac, prevents the combination of
      the renderer and GPU processes from transmitting more frames via
      IOSurfaces from the GPU to the browser process than can be handled by
      the GPU.
      
      This fix causes the renderer to block inside ggl::SwapBuffers() when
      it gets too far ahead. Different strategies can be considered going
      forward, including measuring frame rates in the GPU and renderer
      processes and trying to match them via techniques such as delaying the
      execution of some timers. However, despite the general undesirability
      of blocking the render thread, this fix results in a significant
      performance improvement.
      
      With this fix integrated, a fill-limited test case from Chris Rogers
      displays at 60 FPS instead of 15 FPS on a Mac Pro. Gregg Tavares'
      aquarium from webglsamples.googlecode.com displays at 30 FPS instead
      of 4 or 5 FPS on a MacBook Pro. The frame rates measured at the
      JavaScript level now match the actual frame rate of the browser, where
      previously they were much higher since they were issuing more work
      than the browser could render.
      
      A few other minor OpenGL bugs potentially impacting the correctness of
      the Mac compositor are being fixed as well in this CL.
      
      Verified that WebGL, CSS 3D and YouTube (Core Animation plugin)
      content all work.
      
      BUG=63539
      TEST=none
      
      Review URL: http://codereview.chromium.org/5317007
      
      git-svn-id: svn://svn.chromium.org/chrome/trunk/src@67470 0039d316-1c4b-4281-b951-d872f2087c98
      33da8041
  20. Nov 25, 2010
  21. Nov 24, 2010
  22. Nov 22, 2010
  23. Nov 21, 2010
  24. Nov 20, 2010
  25. Nov 19, 2010
Loading