From bf3e486a5c09dc66c3528f1666d6740929d26384 Mon Sep 17 00:00:00 2001 From: Brian Salomon Date: Wed, 19 Dec 2018 14:54:12 -0500 Subject: [PATCH] Don't use client side buffers with WebGL Change-Id: I00575f7ebbac89646d65cd6cefbf4715c9bd3914 Reviewed-on: https://skia-review.googlesource.com/c/179249 Reviewed-by: Greg Daniel Commit-Queue: Brian Salomon --- src/gpu/gl/GrGLCaps.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/gpu/gl/GrGLCaps.cpp b/src/gpu/gl/GrGLCaps.cpp index 7c83e18b47..3d29ab6751 100644 --- a/src/gpu/gl/GrGLCaps.cpp +++ b/src/gpu/gl/GrGLCaps.cpp @@ -386,7 +386,7 @@ void GrGLCaps::init(const GrContextOptions& contextOptions, // families rather than basing it on the vendor alone. // The Chrome command buffer blocks the use of client side buffers (but may emulate VBOs with // them). Client side buffers are not allowed in core profiles. - if (ctxInfo.driver() != kChromium_GrGLDriver && !fIsCoreProfile && + if (ctxInfo.driver() != kChromium_GrGLDriver && !fIsCoreProfile && !kIsWebGL && (ctxInfo.vendor() == kARM_GrGLVendor || ctxInfo.vendor() == kImagination_GrGLVendor || ctxInfo.vendor() == kQualcomm_GrGLVendor)) { fPreferClientSideDynamicBuffers = true;