GVD: DestroyTextures() when destroying.

GVD: DestroyTextures() when destroying.

GVD should release its references to textures when it Destroy()s VDA or
when it is deleted. It's safe to do so, as the VDAs should keep their own
references to those textures if they are still using them (normally
achieved via binding them to XPixmaps or EGLImages).

BUG=156251
TEST=manual playbacks, refreshes, tab closes, etc.


Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=162400

[Ami GONE FROM CHROMIUM, 2012-10-17 00:48:09]

LGTM % nit

https://codereview.chromium.org/11189027/diff/1/media/filters/gpu_video_decod...
File media/filters/gpu_video_decoder.cc (right):

https://codereview.chromium.org/11189027/diff/1/media/filters/gpu_video_decod...
media/filters/gpu_video_decoder.cc:198: // It's safe to delete textures here, as
the VDA should be keeping its own
The explanation you give here, in the CL description, and in the linked bug is
all from too low-level a perspective :)

It is safe to DeleteTextures() here because GVD owns the textures, and because
it has already posted the Destroy() to the VDA loop and thus the GPU process. 
Nothing we do here can get to the GPU process before that Destroy message, and
once that Destroy message gets there the VDA must not touch the textures
anymore.

I'd just drop this comment.

[commit-bot: I haz the power, 2012-10-17 00:53:38]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/posciak@chromium.org/11189027/5001

[commit-bot: I haz the power, 2012-10-17 01:39:56]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/posciak@chromium.org/11189027/5001

[commit-bot: I haz the power, 2012-10-17 11:20:51]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/posciak@chromium.org/11189027/5001

[commit-bot: I haz the power, 2012-10-17 14:21:30]

Change committed as 162400