Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
  • This project
    • Loading...
  • Sign in / Register
S
swiftshader
  • 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
  • swiftshader
  • Repository

Switch branch/tag
  • swiftshader
  • src
  • Radiance
  • libRAD
  • Texture.h
Find file
BlameHistoryPermalink
  • Nicolas Capens's avatar
    Fix an image destruction deadlock. · fa0cc04a
    Nicolas Capens authored Dec 10, 2014
    The EGL image extension allows a texture image to be shared with another
    texture. We previously prevented destroying them as long as they are shared
    but the parent texture (which owns the resource lock for all its images)
    could be destroyed before the EGL image is destroyed, causing a deadlock
    when trying to acquire the resource lock. The situation was aggravated by
    increasing the parent texture's reference count with the image reference
    count (i.e. not the 'owning' texture's reference count). This fix ensures
    that the parent texture can only destroy the images it owns.
    
    Bug 18680652
    
    Change-Id: I7fa09d181e695cbc287e77874bdb88f24c22cbd8
    Reviewed-on: https://swiftshader-review.googlesource.com/1601Tested-by: 's avatarNicolas Capens <nicolascapens@google.com>
    Reviewed-by: 's avatarNicolas Capens <nicolascapens@google.com>
    fa0cc04a
Texture.h 7.11 KB
EditWeb IDE
×

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