Consider a GL texture used by CC - this texture is shared between a renderer and the GPU process. Many of the objects listed above are shared between multiple processes. GPUMemoryBuffer Category: All GPUMemoryBuffers.GPU Category: All GPU allocations, many shared with other processes.GPUMemoryBuffer Category: All GPUMemoryBuffers in use in the current process.Skia/gpu_resources Category: All GPU resources used by Skia.When GPU rasterization is enabled, these resource allocations will be GPU allocations as well. CC Category: The CC category contains all resource allocations used in the Chrome Compositor.GPU Memory can be found across a number of different processes, in a few different categories. The primary difference is that GLImages are designed to be bound to an OpenGL texture using the image extension. In many cases, GLImages are created from GPUMemoryBuffers. GLImages: GLImages are a platform-independent abstraction around GPU memory, similar to GPU Memory Buffers.Because of their cross process use case, these objects will almost always be shared between a renderer or browser process and the GPU process. While GPUMemoryBuffers represent a platform-independent way to access this memory, they have a number of possible platform-specific implementations (EGL surfaces on Linux, IOSurfaces on Mac, or CPU side shared memory). GPU Memory Buffers: These objects provide a chunk of writable memory which can be handed off cross-process.Because most OpenGL operations occur over IPC, communicating with Chrome's GPU process, these allocations are almost always shared between a renderer or browser process and the GPU process. Chrome itself has handles to these objects, but the actual backing memory may live in a variety of places (CPU side in the GPU process, CPU side in the kernel, GPU side).

Raw OpenGL Objects: These objects are allocated by Chrome using the OpenGL API.GPU Memory in Chrome involves several different types of allocations. If you want an overview of total GPU memory usage, select the GPU process' GPU category and look at the size column.

What is the gpu process in chrome