GitLab

This is a speculative fix for https://crbug.com/1022151. Based on the
crash error and stack trace, it seems likely that we are calling
ClearFramebufferResourceManager::Destroy after a context is unavailable
(i.e. released or lost). In this case, we shouldn't be making any more
GL calls. This copies a pattern of GLES2DecoderImpl::Destroy, so that
CFRM::Destroy is only called if we have a current context.

Bug: 1022151
Change-Id: Icc76e505fa32c3b3bc5bea68a973ac4550828bf5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1934519Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org>
Commit-Queue: Jonathan Backer <backer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#718801}