diff options
| author | dcastagna <dcastagna@chromium.org> | 2016-02-01 13:54:28 -0800 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2016-02-01 21:56:49 +0000 |
| commit | 09bd6b32984a6bc6687378118db9e624ffe5ba20 (patch) | |
| tree | 365f6be1f131bf31982aa06fa8ed4c00a212cd69 /components/translate/core/browser/translate_manager.cc | |
| parent | 4ef49b388232ca3681e36d4d05cc26de3d35458a (diff) | |
| download | chromium_src-09bd6b32984a6bc6687378118db9e624ffe5ba20.zip chromium_src-09bd6b32984a6bc6687378118db9e624ffe5ba20.tar.gz chromium_src-09bd6b32984a6bc6687378118db9e624ffe5ba20.tar.bz2 | |
Allocate new gpu_factories when the cache has an invalid context.
gpu_factories_ provides a GL context to media.
In crrev.com/1369843002 we started caching gpu_factories_ per renderer,
prior to that a new one would be created each time one was requested.
This might have exacerbated the media context loss issue (crbug.com/580386).
This patch adds a workaround where a new one is instantiated every time
the last cached one has an invalid GL context.
We want to merge this back to m48 and m49 since after 48 started rolling out
we have had many reports about green videos that might be caused by this
new behavior.
Once crbug.com/580386 is addressed, this workaround can be removed.
The plan to properly fix crbug.com/580386 is to use media suspend/resume
functionality that is untested in m49 and unavailable in m48.
BUG=582824
Review URL: https://codereview.chromium.org/1649203002
Cr-Commit-Position: refs/heads/master@{#372776}
Diffstat (limited to 'components/translate/core/browser/translate_manager.cc')
0 files changed, 0 insertions, 0 deletions