Add mailbox-based Mojo VideoFrame variant.

media/base/video_frame.cc

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "media/base/video_frame.h"
 
 #include <algorithm>
 #include <climits>
 
 #include "base/atomic_sequence_num.h"
@@ skipping 750 matching lines @@
   storage_type_ = STORAGE_SHMEM;
   shared_memory_handle_ = handle;
 }
 
 #if defined(OS_MACOSX)
 CVPixelBufferRef VideoFrame::cv_pixel_buffer() const {
   return cv_pixel_buffer_.get();
 }
 #endif
 
+void VideoFrame::SetReleaseMailboxCB(
+    const ReleaseMailboxCB& release_mailbox_cb) {
+  DCHECK(!release_mailbox_cb.is_null());
+  DCHECK(mailbox_holders_release_cb_.is_null());
+  mailbox_holders_release_cb_ = std::move(release_mailbox_cb);

[xhwang, 2017/01/25 18:25:09]

OOC nit, not related to your CL: do we need to worry about the thread safty of
VideoFrame?

[sandersd (OOO until July 31), 2017/01/26 23:49:05]

I suppose we do. I added a warning to the header; for now it just says that you
should only call this method in constructor-like situations.

We can fix it with locking if necessary, but we really don't need that for the
current use case.

+}
+
 void VideoFrame::AddDestructionObserver(const base::Closure& callback) {
   DCHECK(!callback.is_null());
   done_callbacks_.push_back(callback);
 }
 
 void VideoFrame::UpdateReleaseSyncToken(SyncTokenClient* client) {
   DCHECK(HasTextures());
   base::AutoLock locker(release_sync_token_lock_);
   // Must wait on the previous sync point before inserting a new sync point so
   // that |mailbox_holders_release_cb_| guarantees the previous sync point
@@ skipping 371 matching lines @@
   if (zero_initialize_memory)
     memset(data, 0, data_size);
 
   for (size_t plane = 0; plane < NumPlanes(format_); ++plane)
     data_[plane] = data + offset[plane];
 
   AddDestructionObserver(base::Bind(&base::AlignedFree, data));
 }
 
 }  // namespace media