diff options
| author | fischman@chromium.org <fischman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-01-31 03:16:00 +0000 |
|---|---|---|
| committer | fischman@chromium.org <fischman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-01-31 03:16:00 +0000 |
| commit | 70cbe3b33543648d8667a39d8e008bdcdd467c03 (patch) | |
| tree | 24fd8be6f27eb6351868286bb80e8050ded5bedb /build | |
| parent | 866e832f381cdb49d5ddcf561a03313fbbe75348 (diff) | |
| download | chromium_src-70cbe3b33543648d8667a39d8e008bdcdd467c03.zip chromium_src-70cbe3b33543648d8667a39d8e008bdcdd467c03.tar.gz chromium_src-70cbe3b33543648d8667a39d8e008bdcdd467c03.tar.bz2 | |
WebMediaPlayer{Android,Impl}: use RenderFrameObserver instead of ML::DestructionObserver/RenderViewObserver.
RenderThreadImpl is torn down before the main thread's MessageLoop is, and some
of WebMediaPlayerAndroid's dependencies require the render thread to still be
alive, so move its tear-down to earlier in the process.
This is the Android version of r240125 which fixed the same bug in
WebMediaPlayerImpl, but forgot that WebMediaPlayerAndroid is a fork.
Since RenderViewObserver is apparently out of favor nowadays, use RenderFrameObserver.
BUG=338393,304967,338481
Review URL: https://codereview.chromium.org/137243005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@248115 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'build')
0 files changed, 0 insertions, 0 deletions