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
  • test_utils
  • ANGLETest.h
Find file
BlameHistoryPermalink
  • Yuly Novikov's avatar
    Restrict OpenGL/Vulkan test window re-creation workaround to NVIDIA · aaa17b85
    Yuly Novikov authored Feb 26, 2019
    The workaround in https://chromium-review.googlesource.com/430887
    was intended only for NVIDIA.
    
    Re-creating the test window causes new native display to be created every time.
    Normally, re-using the same native display with different implementation
    would release the old implementation.
    When new display is created instead of re-using the old one,
    old implementation is never released, leaking memory.
    
    Use SystemInfo to check if any of GPUs is NVIDIA
    and apply the workaround only then,
    reducing the leak on other platforms.
    
    Bug: angleproject:1810, angleproject:3153
    Change-Id: I6198c01c82a01e2adc0bcd1fad303c47cd7328d8
    Reviewed-on: https://chromium-review.googlesource.com/c/1490379
    Commit-Queue: Yuly Novikov <ynovikov@chromium.org>
    Reviewed-by: 's avatarJamie Madill <jmadill@google.com>
    aaa17b85
ANGLETest.h 19 KB
EditWeb IDE
×

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