Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
  • This project
    • Loading...
  • Sign in / Register
A
angle
  • Project
    • Overview
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 0
    • Issues 0
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Chen Yisong
  • angle
  • Repository

Switch branch/tag
  • angle
  • src
  • tests
  • gl_tests
  • StateChangeTest.cpp
Find file
BlameHistoryPermalink
  • Jamie Madill's avatar
    D3D11: Re-check disabled attribs on VAO switch. · 842c43ae
    Jamie Madill authored Oct 31, 2017
    When switching VAOs, if we switch to a VAO which has disabled
    attributes, we could occasionally in some edge cases not have a buffer
    initialized to render with. Fix this by re-checking the current
    value (disabled) attributes every VAO switch.
    
    Probably a regression caused by d28758de:
    "D3D11: Re-enable updateVertexBuffer dirty bits."
    
    BUG=chromium:778689
    
    Change-Id: I01814bafa1d6e3a7d6a5c03bc5d058f39346f087
    Reviewed-on: https://chromium-review.googlesource.com/748426Reviewed-by: 's avatarJamie Madill <jmadill@chromium.org>
    842c43ae
StateChangeTest.cpp 29 KB
EditWeb IDE
×

Replace StateChangeTest.cpp

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.