CommandExecutor:PutChanged for DisplayCompositor taking 4s |
||
Issue descriptionFiling for gilbertleung@. This is on this desktop linux machine where tasks on the gpu thread are taking 4s. Attached trace and about:gpu This is 53.0.2785.101 afaict this is just drawing the browser chrome, not some complex page causing slow down, since things are already hosed before any renderer produced new frames (I think?) not sure if any other trace category will help here..
,
Sep 12 2016
As I suspected, this happens because the GPU is out of memory:
FB Memory Usage
Total : 1023 MiB
Used : 1007 MiB
Free : 16 MiB
This results in trashing, similar to when out of memory and pages get swapped in and out to disk.
Oftentimes, we observed a lot of the GPU memory to be consumed by the desktop compositor (e.g. compiz) - possibly because of leaks there - and there's not a whole lot we can do if that's the case. One way to tell is to open the Chrome task manager, enable the "GPU memory" column (right-click -> check "GPU memory"), and look at the value under "GPU Process". That will be the amount we believe we use.
There are several similar bugs, will duplicate into one of them - feel free to follow the discussion there, and/or post additional information.
,
Sep 12 2016
I'm seeing about 90,000-10,000K under the GPU RAM column. Is that standard?
,
Sep 13 2016
@#4: is that for the GPU process, or for individual tabs? The data is slightly confusing: only the GPU process allocates GPU memory, and the amount reported for "GPU process" is the actual amount of GPU memory that is allocated (it has a "*" next to it). We further break it down by associating that GPU memory to the clients that caused that allocation, and that's what is reported on the other lines (if you do the math, you'll see that the amount for the GPU process is equal to the sum of amounts for all other processes). We try to release memory for offscreen tabs, but keep up to 5 in LRU fashion for fast tab switching. The allocation for those is about the tab's dimensions worth of pixels. For a 30" screen at 2560x1600, a fullscreen tab is about 16MB of memory. We also have memory for the visible tabs (1 per browser window), and this can be more than the screen worth because we pre-render for smooth scrolling. So for long pages, it's common to see those use more than a screen worth. There's also some GPU-intensive pages (e.g. Google Maps) as well as pathological cases that need more memory. 90K is fairly high but not unheard of. |
||
►
Sign in to add a comment |
||
Comment 1 by piman@chromium.org
, Sep 12 2016