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
  • FrameCapture.cpp
Find file
BlameHistoryPermalink
  • Jamie Madill's avatar
    Capture/Replay: Don't capture deleted shaders. · 385fb40f
    Jamie Madill authored Oct 04, 2020
    ANGLE can sometimes hold on to deleted shaders while they're still in
    use. This would happen when re-capturing captured application. A bunch
    of shaders would be still around after used in the program linking
    step because they are still attached to the program. Fix this by not
    skipping the capture for shader that have been deleted but are still
    in the resource map. Noticed while capturing the T-Rex replay.
    
    Bug: angleproject:5134
    Change-Id: I04e3e96b43e445d7b467e6db0325ecd0d821549d
    Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2449162
    Commit-Queue: Jamie Madill <jmadill@chromium.org>
    Reviewed-by: 's avatarCody Northrop <cnorthrop@google.com>
    Reviewed-by: 's avatarCourtney Goeltzenleuchter <courtneygo@google.com>
    385fb40f
FrameCapture.cpp 182 KB
EditWeb IDE
×

Replace FrameCapture.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.