summaryrefslogtreecommitdiffstats
path: root/content/browser/gpu
Commit message (Collapse)AuthorAgeFilesLines
* fix-gl-logginggman@chromium.org2012-04-221-0/+1
| | | | | | | | | | TEST=none BUG=none Review URL: http://codereview.chromium.org/10155002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133364 0039d316-1c4b-4281-b951-d872f2087c98
* Add a message to about:gpu when the gpu process crashes.nduca@chromium.org2012-04-191-0/+6
| | | | | | | | | | R=apatrick@chromium.org CC=davemoore@chromium.org Review URL: http://codereview.chromium.org/10116036 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133035 0039d316-1c4b-4281-b951-d872f2087c98
* TabContents -> WebContentsImpl, part 19.avi@chromium.org2012-04-171-1/+1
| | | | | | | | | | BUG=105875 TEST=no change Review URL: http://codereview.chromium.org/10106022 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132599 0039d316-1c4b-4281-b951-d872f2087c98
* Apply an initial seccomp filter policy for Pepper Flash.cevans@chromium.org2012-04-171-0/+1
| | | | | | | | I'll send out a separate mail about the shmat() situation -- for now, a shipping seccomp filter sandbox is better than no filtering. Review URL: https://chromiumcodereview.appspot.com/10105009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132501 0039d316-1c4b-4281-b951-d872f2087c98
* Convert plugin and GPU process to brokered handle duplication.jschuh@chromium.org2012-04-144-58/+5
| | | | | | | BUG=119250 Review URL: https://chromiumcodereview.appspot.com/9958034 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132303 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 132218 - Convert plugin and GPU process to brokered handle duplication.eroman@chromium.org2012-04-134-3/+53
| | | | | | | | | | | | (Seems to be responsible for VMTest failure on ChromiumOS). BUG=119250 Review URL: https://chromiumcodereview.appspot.com/9958034 TBR=jschuh@chromium.org Review URL: https://chromiumcodereview.appspot.com/10081018 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132254 0039d316-1c4b-4281-b951-d872f2087c98
* Convert plugin and GPU process to brokered handle duplication.jschuh@chromium.org2012-04-134-53/+3
| | | | | | | BUG=119250 Review URL: https://chromiumcodereview.appspot.com/9958034 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132218 0039d316-1c4b-4281-b951-d872f2087c98
* Make it so you can add GPU switches by editing 2 files instead of 3.gman@chromium.org2012-04-131-5/+2
| | | | | | | | | | | TEST=none BUG=none R=apatrick@chromium.org Review URL: http://codereview.chromium.org/10065025 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132147 0039d316-1c4b-4281-b951-d872f2087c98
* Index GpuProcessHost by kind rather than ID.apatrick@chromium.org2012-04-122-30/+24
| | | | | | | There should never be more than one GpuProcessHost of each kind (sandboxed vs. unsandboxed). The original motivation for having a map by ID was to allow one GPU process per renderer process. This is no longer the case and it is making the code awkward. Review URL: https://chromiumcodereview.appspot.com/10050004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132084 0039d316-1c4b-4281-b951-d872f2087c98
* Log GPU process launch time to UMA.fischman@chromium.org2012-04-112-0/+9
| | | | | | | | | | BUG=106509 TEST=manually checked chrome://histograms/GPU.GPUPro Review URL: http://codereview.chromium.org/10037025 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@131691 0039d316-1c4b-4281-b951-d872f2087c98
* Cache shared texture in browserjbauman@chromium.org2012-04-072-0/+23
| | | | | | | | | | | | Doing CreateTexture every frame seems to cause a leak in the NVIDIA driver on some optimus systems, so instead cache the texture while it exists. BUG=115422 TEST= Review URL: http://codereview.chromium.org/10007024 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@131245 0039d316-1c4b-4281-b951-d872f2087c98
* Disable image transport surface on AMD's dynamic switchable graphics.jbauman@chromium.org2012-04-071-0/+7
| | | | | | | | | | | It was only displaying black if set to use the AMD chip. BUG=117371 TEST= Review URL: https://chromiumcodereview.appspot.com/9968074 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@131225 0039d316-1c4b-4281-b951-d872f2087c98
* Pass kV and kVModule flags to GPU process.posciak@chromium.org2012-04-061-0/+2
| | | | | | | | | | | | This allows the GPU process to use (D)VLOG(). BUG=117829 TEST=Manual run to check DVLOG messages are outputted from the GPU process. Review URL: http://codereview.chromium.org/9816023 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@131109 0039d316-1c4b-4281-b951-d872f2087c98
* Unobfuscate RWHVMac accelerated compositing code path by separating it from ↵jbates@chromium.org2012-04-051-31/+2
| | | | | | | | | | | | | | | | | | plugin code. This simplification (and multi-race-condition-bug-fix) unfortunately comes with one subtle regression which is that as soon as a OSX chrome window renders accelerated content, it becomes permanently non-opaque. This causes the square gray lines to show up in the upper window corners that currently only show up if a tab has accelerated content. When I tried to support dynamically changing setOpaque, there were rare occurrences of black/transparent flashing when rapidly switching tabs between GPU and non-GPU content. Since we know that we have to fix the window border issue for real (crbug.com/56154) a little more of it is an acceptable trade-off for a reduction in flashing. This cleanup also seems to fix: - all black/transparent flashing (I can't repro it anymore) - window immobilization (104996) - slider widget jumps around during window resize (104996) BUG=121129,56154,104996,119640,81733 TEST=Open lots of webgl and software tabs and rapidly switch between them, make sure things update properly, resize window, etc. Review URL: http://codereview.chromium.org/9958100 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@130989 0039d316-1c4b-4281-b951-d872f2087c98
* Remove TOOLKIT_USES_GTK and consolidate it into TOOLKIT_GTKoshima@chromium.org2012-04-054-15/+15
| | | | | | | | | | | Add gtk dependency to base.gyp for android host_os="linux" case BUG=none TEST=none Review URL: https://chromiumcodereview.appspot.com/9969080 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@130784 0039d316-1c4b-4281-b951-d872f2087c98
* Adding command line switch --gpu-swap-delay to artificially slow down thejunov@google.com2012-03-291-1/+18
| | | | | | | | | | GPU process to simulate slow GPUs. BUG=120469 TEST=None Review URL: https://chromiumcodereview.appspot.com/9866053 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@129673 0039d316-1c4b-4281-b951-d872f2087c98
* Remove display switch callback stuff on Mac.zmo@google.com2012-03-281-44/+0
| | | | | | | | | | | It is not used, so no reason for them to stay there, especially after someone complained :) BUG=120738 TEST=nothing changes R=kbr Review URL: https://chromiumcodereview.appspot.com/9883001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@129500 0039d316-1c4b-4281-b951-d872f2087c98
* Disable GPU features if /dev/nvidiactl is inaccessiblezmo@chromium.org2012-03-281-0/+4
| | | | | | | | | BUG=98819 TEST=chmod a-rw /dev/nvidiactl, and then open about:gpu R=apatrick Review URL: https://chromiumcodereview.appspot.com/9844005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@129314 0039d316-1c4b-4281-b951-d872f2087c98
* make disable-glsl-translator work againgman@chromium.org2012-03-261-0/+5
| | | | | | | | | | TEST=none BUG=none Review URL: http://codereview.chromium.org/9812021 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128849 0039d316-1c4b-4281-b951-d872f2087c98
* Bug: wrong host ID was used to route SwapBuffers ack back to GPU process.apatrick@chromium.org2012-03-221-1/+1
| | | | | | Review URL: http://codereview.chromium.org/9831002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128134 0039d316-1c4b-4281-b951-d872f2087c98
* Removing --in-process-gpu from the set of flags that prevents creation of a ↵robertshield@chromium.org2012-03-211-2/+1
| | | | | | | | | | | | | | GpuChildThread. The Android build uses this flag, which assumes that the GPU process host creates the ChildProcess instance. This regressed in r126140. BUG=NONE TEST=NONE Review URL: http://codereview.chromium.org/9815011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128079 0039d316-1c4b-4281-b951-d872f2087c98
* Fix mac_clang build.apatrick@chromium.org2012-03-201-1/+1
| | | | | | Review URL: https://chromiumcodereview.appspot.com/9768005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@127831 0039d316-1c4b-4281-b951-d872f2087c98
* Windows: Added AcceleratedPresenterMap.apatrick@chromium.org2012-03-203-53/+42
| | | | | | | | | | | | | | | This is a thread safe mapping from window handle to the associated AcceleratorPresenter that maintains the window's swap chain. The mapping was previously maintained by the GpuSurfaceTracker (via the surface ID). I changed it because I think is is possible the GpuSurfaceTracker's AcceleratedSurface pointer was going dangling. I made PresentThread reference counted and made each AcceleratedPresenter ref count it's PresentThread so the PresentThread's message loop are always a valid place to post tasks. Since other threads can post tasks to the AcceleratedPresenter at any time, I changed the shutdown of AcceleratedSurface to simply invalidate the presenter rather than waiting for its pending tasks to complete, which probably wasn't sufficient. I renamed surface_id to surface_handle for consistency with the rest of the code. BUG=117453 Review URL: https://chromiumcodereview.appspot.com/9704075 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@127821 0039d316-1c4b-4281-b951-d872f2087c98
* Pass swiftshader-path flag down to GPU processjbauman@chromium.org2012-03-171-2/+9
| | | | | | | | | | | | Makes it easier to test swiftshader. BUG= TEST= Review URL: http://codereview.chromium.org/9605040 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@127326 0039d316-1c4b-4281-b951-d872f2087c98
* RenderProcessHost should return the list of registered RWHs, not ipc listeners.pfeldman@chromium.org2012-03-161-2/+2
| | | | | | | | BUG=118404 Review URL: https://chromiumcodereview.appspot.com/9701071 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@127130 0039d316-1c4b-4281-b951-d872f2087c98
* Refactor GpuProcessHost::GetForClient to GpuProcessHost::Get, which takes a ↵apatrick@chromium.org2012-03-154-31/+39
| | | | | | | | | | | GPU process kind rather than a client ID. There is no longer a plan to have a GPU process for each client to identify the GPU process by its kind (sandboxed or unsandboxed) rather than client ID. I checked about:gpu still works and that the limit on the number of times the sandboxed GPU is relaunched is still limitted. Review URL: https://chromiumcodereview.appspot.com/9559013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@126960 0039d316-1c4b-4281-b951-d872f2087c98
* Implement WebKitPlatformSupport::canAccelerate2dCanvasjamesr@chromium.org2012-03-141-0/+1
| | | | | | | | | | | | | | | | | | | | | | | We do not want to use the accelerated 2d canvas path if we can lose a context "too easily" - for example due to the screensaver turning on - or if we're using a software rendering backend for GL contexts (swiftshader). The way these conditions are currently checked for are awkard and racy. This adds an explicit check that WebKit calls prior to instantiating an accelerated context for canvas. This does two things: 1.) Attempt to spin up the GpuChannelHost. If we can't do this, then we definitely don't need to bother. Note that if the GPU process crashes this will establish a connection to the new GPU process. 2.) Query the can_lose_context and software_rendering bits from the new channel. These are both properties of the GPU process, not of individual contexts, so we don't need to have a particular context ready in order to do this. BUG=none Review URL: https://chromiumcodereview.appspot.com/9655017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@126558 0039d316-1c4b-4281-b951-d872f2087c98
* Chrome OS: Don't blacklist GPU process after 3 deathspiman@chromium.org2012-03-131-0/+2
| | | | | | | | | | BUG=chromium-os:27603 TEST=run chrome --ui-use-gpu-process, kill gpu process at least 4 times from task manager, check browser doesn't crash. Review URL: http://codereview.chromium.org/9696027 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@126469 0039d316-1c4b-4281-b951-d872f2087c98
* Fix --single-process mode issues with GpuChannelHostFactorypiman@chromium.org2012-03-122-11/+8
| | | | | | | | | | | | | | | GpuChannelHostFactory itself is no longer a singleton, we pass it explicitly to WebGraphicsContext3DCommandBufferImpl. That prevents RenderThreadImpl and BrowserGpuChannelHostFactory from stomping on each other in --single-process mode BUG=117594 TEST=see bug Review URL: http://codereview.chromium.org/9667012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@126194 0039d316-1c4b-4281-b951-d872f2087c98
* Add an explicit single-process check to the GPU process initialization. robertshield@chromium.org2012-03-121-4/+2
| | | | | | | | | | | | This avoids a race between the GPU process and the renderer process that can cause the GPU code to create the first ChildProcess instance, causing the renderer to dcheck. BUG=NONE TEST=NONE Review URL: http://codereview.chromium.org/9647001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@126140 0039d316-1c4b-4281-b951-d872f2087c98
* Shutdown GPU process if Direct 3D cannot be initialized in the browser process.apatrick@chromium.org2012-03-093-10/+32
| | | | | | | | | | | | | The GPU process cannot usefully do anything in this case since its output cannot be presented. This uses the existing machinery to recover from the GPU process crashing. It will reattempt 3 times as before. Direct3D is initialized asynchronously off the main thread so the browser process does not learn of the failure until the GPU process attempts to present a surface. I also discovered a bug where a SwapBuffers acknowledgement could be sent to the wrong instance of a GPU process because of a mismatch between client_id and host_id. BUG=117468 Review URL: https://chromiumcodereview.appspot.com/9651012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@125886 0039d316-1c4b-4281-b951-d872f2087c98
* Aura: recover from lost context / GPU process dyingpiman@chromium.org2012-03-081-1/+1
| | | | | | | | | | | | | | For recovery from lost contexts, we need to: - on the UI thread, recreate the compositing surfaces (since they are textures in the UI compositor context that we lost). - on the IO thread, delay the requests from the renderer process to create view contexts, until the above has happened. BUG=116394,116839 TEST=chrome --ui-use-gpu-process --force-compositing-mode, kill GPU process, check everything still works Review URL: http://codereview.chromium.org/9632005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@125727 0039d316-1c4b-4281-b951-d872f2087c98
* Fix context sharing between channels to be order-independent.piman@chromium.org2012-03-083-4/+4
| | | | | | | | | | | | | | Ensuring order of channel recreation after a GPU process death is very hard. With this there's not need. A channel is either shared or not, all the "shared" channels share their context together, every other one doesn't share with anything. More restrictive but it's enough for our needs. BUG=116913 TEST=chrome --ui-use-gpu-process, kill GPU process, observe GpuChannelManager::OnEstablishChannel crash doesn't happen. Review URL: https://chromiumcodereview.appspot.com/9619017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@125521 0039d316-1c4b-4281-b951-d872f2087c98
* Windows: Limit D3D devices to one per Present Thread (4 max).apatrick@chromium.org2012-03-074-1/+22
| | | | | | | | | | | | | Instead of one D3D device per unsuspended tab, there is one D3D device per Present Thread plus one additional swap chain per unsuspended tab. Also, the swap chains are completely destroyed when a tab is suspended, rather than resizing the device swap chain to 1 x 1. Specified flag on D3D device creation to tell it not to create worker threads to evaluate vertex shaders because we aren't using vertex shaders here but the devices appeared to create some (actually lots) anyway. Sent Suspend notification directly from browser IO thread to present thread rather than via UI thread so tehy don't get unnecessarily held up if the UI thread is busy. BUG=116175,115707 Review URL: https://chromiumcodereview.appspot.com/9565043 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@125439 0039d316-1c4b-4281-b951-d872f2087c98
* Move Render(View|Widget)Host and associated classes to content namespace.joi@chromium.org2012-03-071-0/+1
| | | | | | | | | TBR=jam@chromium.org BUG=98716 Review URL: https://chromiumcodereview.appspot.com/9600036 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@125388 0039d316-1c4b-4281-b951-d872f2087c98
* Move Render(Widget|View)HostImpl to files with _impl in filename.joi@chromium.org2012-03-062-2/+2
| | | | | | | | | TBR=jam@chromium.org BUG=98716 Review URL: https://chromiumcodereview.appspot.com/9600021 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@125167 0039d316-1c4b-4281-b951-d872f2087c98
* Extract minimal RenderViewHost interface for embedders, leavingjoi@chromium.org2012-03-051-1/+1
| | | | | | | | | | | | RenderViewHostImpl for content. TBR=darin@chromium.org BUG=98716 Review URL: http://codereview.chromium.org/9473001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@124941 0039d316-1c4b-4281-b951-d872f2087c98
* Coverity: Fix a few pass-by-values.jhawkins@chromium.org2012-03-042-4/+4
| | | | | | | | | | | | CID_COUNT=2 CID=103366,103367 TEST=none BUG=none R=groby Review URL: https://chromiumcodereview.appspot.com/9429066 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@124883 0039d316-1c4b-4281-b951-d872f2087c98
* Land 9348117: (Aura) use GPU process for UIbacker@chromium.org2012-02-246-11/+21
| | | | | | | | | | | | | This is behind a flag (--ui-use-gpu-process). Currently problems occur when the GPU process crash, this will be handled in a follow-up CL. BUG=99516 TEST=chrome --ui-use-gpu-process (with an aura build) TBR=sky,jam,apatrick Review URL: https://chromiumcodereview.appspot.com/9442017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@123473 0039d316-1c4b-4281-b951-d872f2087c98
* Cleanup: Remove base::environment_vector and ↵thestig@chromium.org2012-02-242-4/+6
| | | | | | | | | | | base::file_handle_mapping_vector to StudlyCaps. BUG=none TEST=none Review URL: http://codereview.chromium.org/9429039 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@123438 0039d316-1c4b-4281-b951-d872f2087c98
* Extract first version of a RenderWidgetHost interface.joi@chromium.org2012-02-231-1/+1
| | | | | | | | | | | | | | | | | | | | | This begins the process of extracting RWH and RVH interfaces and leaving RenderWidgetHostImpl and RenderViewImpl classes in content. There will be parallel inheritance hierarchies, i.e. RWHImpl inherits from RWH, RVH inherits from RWH, RVHImpl inherits from RVH and RWHImpl. Thus, chrome will only see the interfaces. I fully expect that some of the things chrome needs from the RVH interface, once I introduce that, will more properly belong on the RWH interface, in which case I expect to move them there. But first to define the base interfaces. BUG=98716 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=123227 Review URL: https://chromiumcodereview.appspot.com/9432027 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@123239 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 123227 - Extract first version of a RenderWidgetHost interface.joi@chromium.org2012-02-231-1/+1
| | | | | | | | | | | | | | | | | | | | | | This begins the process of extracting RWH and RVH interfaces and leaving RenderWidgetHostImpl and RenderViewImpl classes in content. There will be parallel inheritance hierarchies, i.e. RWHImpl inherits from RWH, RVH inherits from RWH, RVHImpl inherits from RVH and RWHImpl. Thus, chrome will only see the interfaces. I fully expect that some of the things chrome needs from the RVH interface, once I introduce that, will more properly belong on the RWH interface, in which case I expect to move them there. But first to define the base interfaces. BUG=98716 Review URL: https://chromiumcodereview.appspot.com/9432027 TBR=joi@chromium.org Review URL: https://chromiumcodereview.appspot.com/9453010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@123234 0039d316-1c4b-4281-b951-d872f2087c98
* Extract first version of a RenderWidgetHost interface.joi@chromium.org2012-02-231-1/+1
| | | | | | | | | | | | | | | | | | | This begins the process of extracting RWH and RVH interfaces and leaving RenderWidgetHostImpl and RenderViewImpl classes in content. There will be parallel inheritance hierarchies, i.e. RWHImpl inherits from RWH, RVH inherits from RWH, RVHImpl inherits from RVH and RWHImpl. Thus, chrome will only see the interfaces. I fully expect that some of the things chrome needs from the RVH interface, once I introduce that, will more properly belong on the RWH interface, in which case I expect to move them there. But first to define the base interfaces. BUG=98716 Review URL: https://chromiumcodereview.appspot.com/9432027 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@123227 0039d316-1c4b-4281-b951-d872f2087c98
* Allow GPU process to present to the compositing surface without the ↵apatrick@chromium.org2012-02-214-0/+86
| | | | | | | | | | | | | involvement of the UI thread. This is to prevent a potential deadlock and so I can revert this: https://chromiumcodereview.appspot.com/9295021 BUG=111514 Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=122205 Review URL: https://chromiumcodereview.appspot.com/9380019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@122915 0039d316-1c4b-4281-b951-d872f2087c98
* Coverity: Fix pass-by-values.jhawkins@chromium.org2012-02-214-12/+12
| | | | | | | | | | | | CID_COUNT=7 CID=103317,103318,103319,103320,103321,103322,103323 BUG=none TEST=none R=groby Review URL: https://chromiumcodereview.appspot.com/9414033 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@122853 0039d316-1c4b-4281-b951-d872f2087c98
* Move RenderWidgetHostView into content namespace. Fix include paths.joi@chromium.org2012-02-201-2/+2
| | | | | | | | | | | | TBR=pkasting@chromium.org BUG=98716 Initial commit: 122753 Reverted (linux_chromeos_gtk build problem): r122755 Review URL: https://chromiumcodereview.appspot.com/9420007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@122758 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 122753 - Move RenderWidgetHostView into content namespace. Fix ↵joi@chromium.org2012-02-201-2/+2
| | | | | | | | | | | | | | | include paths. TBR=pkasting@chromium.org BUG=98716 Review URL: http://codereview.chromium.org/9420007 TBR=joi@chromium.org Review URL: https://chromiumcodereview.appspot.com/9355042 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@122755 0039d316-1c4b-4281-b951-d872f2087c98
* Move RenderWidgetHostView into content namespace. Fix include paths.joi@chromium.org2012-02-201-2/+2
| | | | | | | | | | TBR=pkasting@chromium.org BUG=98716 Review URL: http://codereview.chromium.org/9420007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@122753 0039d316-1c4b-4281-b951-d872f2087c98
* Introduce content::RenderWidgetHostViewPort (in content/port/browser).joi@chromium.org2012-02-161-9/+10
| | | | | | | | | | | | | | | Move RenderWidgetHostViewBase and TestRenderWidgetHostView to content namespace. Follow-up changes will move RenderWidgetHostView to content namespace, and get rid of content/browser/renderer_host/render_widget_host_view.h which is now just a redirect header. BUG=98716 Review URL: https://chromiumcodereview.appspot.com/9347042 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@122288 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 122213 - aura: Use GPU process for UIdpapad@chromium.org2012-02-166-21/+11
| | | | | | | | | | | | | | | | This is behind a flag (--ui-use-gpu-process). Currently problems occur when the GPU process crash, this will be handled in a follow-up CL. BUG=99516 TEST=chrome --ui-use-gpu-process (with an aura build) Review URL: http://codereview.chromium.org/9348117 TBR=piman@chromium.org Review URL: https://chromiumcodereview.appspot.com/9347063 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@122219 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-03-28 03:03:31 +0000