1. 11 Sep, 2018 8 commits
  2. 07 Sep, 2018 2 commits
  3. 06 Sep, 2018 3 commits
  4. 05 Sep, 2018 5 commits
  5. 31 Aug, 2018 2 commits
  6. 30 Aug, 2018 3 commits
  7. 29 Aug, 2018 3 commits
  8. 18 Aug, 2018 1 commit
  9. 14 Aug, 2018 1 commit
  10. 13 Aug, 2018 1 commit
  11. 10 Aug, 2018 2 commits
  12. 07 Aug, 2018 2 commits
  13. 06 Aug, 2018 1 commit
  14. 02 Aug, 2018 1 commit
  15. 01 Aug, 2018 1 commit
  16. 31 Jul, 2018 1 commit
  17. 20 Jul, 2018 2 commits
  18. 13 Jul, 2018 1 commit
    • Remove X11 window validation. · 8fb6f6a1
      Nicolas Capens authored
      Despite being a 'client resource', the window can become invalid due to
      events outside of the client code's control, which causes
      XGetWindowAttributes to fail because it retrieves servers-side data
      that is no longer available. Hence it is something we should expect to
      see happen, and not (always) an indication of a bug that needs fixing.
      Also, we should be able to safely continue with an invalid window.
      
      At this point it's up to the client code to catch the X error and
      handle it appropriately. The EGL spec does not indicate that it should
      catch it instead and generate an error (eglSwapBuffers can generate
      EGL_CONTEXT_LOST but that's reserved for power management events).
      
      Bug chromium:861882
      Bug chromium:824522
      
      Change-Id: I78a364516b9466f652c94de68553369935590bde
      Reviewed-on: https://swiftshader-review.googlesource.com/19868Reviewed-by: 's avatarAntoine Labour <piman@chromium.org>
      Reviewed-by: 's avatarNicolas Capens <nicolascapens@google.com>
      Tested-by: 's avatarNicolas Capens <nicolascapens@google.com>