1. 08 Jun, 2020 1 commit
  2. 29 May, 2020 4 commits
  3. 23 May, 2020 1 commit
  4. 13 May, 2020 1 commit
    • Jeremy White's avatar
      Fix a bug introduced by the full-screen scan. · 28b08ae6
      Jeremy White authored
      You will get occasional screen glitches; you could observe
      this doing an 'ls; clear' pattern again and again.
      This was caused by the full screen optimization made in 97517317
      which can cause some scan reports to be incorrectly discarded.
      Full disclosure:  I modified Brendan's original patch to introduce
      this bug, so the blame is mine alone.
      Acked-by: Frediano Ziglio's avatarFrediano Ziglio <fziglio@redhat.com>
  5. 06 May, 2020 9 commits
  6. 28 Apr, 2020 6 commits
  7. 21 Apr, 2020 4 commits
  8. 20 Apr, 2020 7 commits
  9. 17 Mar, 2020 1 commit
  10. 15 Mar, 2020 3 commits
  11. 11 Mar, 2020 1 commit
    • Jeremy White's avatar
      Fix compliation on gcc 4.X. · ae644b34
      Jeremy White authored
      gcc 4.x warns if you use a { 0 } initialization construct
      for a structure with an initial member that is also a struct.
      The { } construct is simpler and appears to work on a wider
      range of gcc versions.
      This is a correction to fdfdf110
  12. 20 Feb, 2020 1 commit
  13. 20 Aug, 2019 1 commit
    • Brendan Shanks's avatar
      Add cache for SHM segments · 51d2a8ba
      Brendan Shanks authored
      Add a cache to allow the reuse of SHM segments.
      Shared memory segments are added to the cache instead of being
      deallocated, and the cache is searched instead of/before allocating a
      new segment.
      Both the SHM segments and their attachment with the X server are cached.
      The cache currently has a fixed number of 10 entries, this provided a
      good cache hit rate while keeping memory usage under control.
      Building with DEBUG_SHM_CACHE defined and running with
      G_MESSAGES_DEBUG=all will periodically print out the SHM cache hit
      On my Ubuntu 18.04 system running XFCE4 with a 2560x1440 screen, the
      cache hit rate starts around 72%. On-screen windows that update often
      and have consistently-sized damage rectangles are the best case. With
      several of those (scrolling terminal windows, web browser showing a
      WebGL demo), the hit rate slowly rises to around 92%.
      Operations that generate rapid damage reports (like resizing or moving
      windows) will lower the hit rate.
      Signed-off-by: Brendan Shanks's avatarBrendan Shanks <bshanks@codeweavers.com>
      Acked-by: Jeremy White's avatarJeremy White <jwhite@codeweavers.com>