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
  • libANGLE
  • Framebuffer.h
Find file
BlameHistoryPermalink
  • Jamie Madill's avatar
    Track rendering feedback loops by-context. · c9c4e4ed
    Jamie Madill authored Apr 02, 2020
    This fixes an issue where feedback loops detection would trigger false
    positives based on texture use in multiple contexts.
    
    1) there are two contexts, C1 and C2, sharing resources
    2) in C1, there is a texture T bound to GL_TEXTURE_2D, and a program in
       use that will sample C1
    3) in C2, a framebuffer is created and T is bound to it
    
    This fix indexes each set of active bindings in an object by ContextID.
    We can potentially redo this solution in the future if this proves to
    have too much tracking overhead.
    
    Includes a test writen by Ken Russell.
    
    Bug: angleproject:4517
    Change-Id: I67012e68947c42d863dca193972576c82d5f3712
    Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2134406
    Commit-Queue: Jamie Madill <jmadill@chromium.org>
    Reviewed-by: 's avatarKenneth Russell <kbr@chromium.org>
    c9c4e4ed
Framebuffer.h 19.9 KB
EditWeb IDE
×

Replace Framebuffer.h

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.