Pass decoded picture size from VDA to client

media/video/picture.cc

Index: media/video/picture.cc
diff --git a/media/video/picture.cc b/media/video/picture.cc
index 7b32563824e3172749871915cad50b13ea632056..917651f9a05a4a8967cd343b0943aa116f50db79 100644
--- a/media/video/picture.cc
+++ b/media/video/picture.cc
@@ -22,9 +22,12 @@ PictureBuffer::PictureBuffer(int32 id,
       texture_mailbox_(texture_mailbox) {
 }
 
-Picture::Picture(int32 picture_buffer_id, int32 bitstream_buffer_id)
+Picture::Picture(int32 picture_buffer_id,
+                 int32 bitstream_buffer_id,
+                 const gfx::Size& size)
     : picture_buffer_id_(picture_buffer_id),
-      bitstream_buffer_id_(bitstream_buffer_id) {
+      bitstream_buffer_id_(bitstream_buffer_id),
+      size_(size) {

[jln (very slow on Chromium), 2014/08/15 18:07:08]

What happens here if an attacker supplies a bogus size via the IPC?

How could we make sure that this size is safe to use? Could we check that it is
within the bounds of the image? (We should do this as close to receiving the IPC
message as possible).

 }
 
 }  // namespace media