Fix memory leak with default Framebuffers.

When the depth-stencil attachment had no depth or stencil bits, we
would like a gl::Renderbuffer object. This was causing unbounded
memory growth in Chrome, and could happen when you watched a lot
of streaming video.

The bug was originally reported and fixed by Austin Kinross in
commit 44f4d74c0f07fa23.

BUG=403471

Change-Id: I022f01a6d3159f766e65f65f023e6ce9baacbc8e
Reviewed-on: https://chromium-review.googlesource.com/231235
Tested-by: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Hendrik Wagenaar <hendrikw@chromium.org>
Tested-by: Hendrik Wagenaar <hendrikw@chromium.org>
Reviewed-by: Geoff Lang <geofflang@chromium.org>
1 file changed
tree: adb42be2e3fe84c24063777f82a4f3accf700771
  1. .gitattributes
  2. .gitignore
  3. AUTHORS
  4. BUILD.gn
  5. CONTRIBUTORS
  6. DEPS
  7. LICENSE
  8. README.chromium
  9. README.md
  10. build/
  11. codereview.settings
  12. enumerate_files.py
  13. extensions/
  14. generate_projects
  15. include/
  16. projects/
  17. samples/
  18. src/
  19. tests/
  20. util/
README.md

#ANGLE The goal of ANGLE is to allow Windows users to seamlessly run WebGL and other OpenGL ES content by translating OpenGL ES API calls to DirectX 9 or DirectX 11 API calls.

ANGLE is a conformant implementation of the OpenGL ES 2.0 specification that is hardware‐accelerated via Direct3D. ANGLE v1.0.772 was certified compliant by passing the ES 2.0.3 conformance tests in October 2011. ANGLE also provides an implementation of the EGL 1.4 specification. Work on ANGLE's OpenGL ES 3.0 implementation is currently in progress, but should not be considered stable.

ANGLE is used as the default WebGL backend for both Google Chrome and Mozilla Firefox on Windows platforms. Chrome uses ANGLE for all graphics rendering on Windows, including the accelerated Canvas2D implementation and the Native Client sandbox environment.

Portions of the ANGLE shader compiler are used as a shader validator and translator by WebGL implementations across multiple platforms. It is used on Mac OS X, Linux, and in mobile variants of the browsers. Having one shader validator helps to ensure that a consistent set of GLSL ES shaders are accepted across browsers and platforms. The shader translator can be used to translate shaders to other shading languages, and to optionally apply shader modifications to work around bugs or quirks in the native graphics drivers. The translator targets Desktop GLSL, Direct3D HLSL, and even ESSL for native GLES2 platforms.

##Building For building instructions, visit the dev setup wiki.

##Contributing