Commit 2f61858f authored by Matthew Cary's avatar Matthew Cary Committed by Commit Bot

media/base: Fix incorrect comment in WritableUnalignedMapping.

When WritableUnalignedMapping takes a handle, it *does* own it (the temporary
shared memory region created in the constructor consumes the handle).

Bug: 849207
Change-Id: Icabca455727ad275d9c5a55065c5baf18f44e08c
Reviewed-on: https://chromium-review.googlesource.com/1152913Reviewed-by: default avatarDan Sanders <sandersd@chromium.org>
Reviewed-by: default avatarAlexandr Ilin <alexilin@chromium.org>
Commit-Queue: Matthew Cary <mattcary@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579755}
parent 58faa748
......@@ -50,7 +50,7 @@ class MEDIA_EXPORT UnalignedSharedMemory {
// offsets.
class MEDIA_EXPORT WritableUnalignedMapping {
public:
// Creates an |UnalignedSharedMemory| instance from a
// Creates an |WritableUnalignedMapping| instance from a
// |UnsafeSharedMemoryRegion|. |size| sets the maximum size that may be mapped
// within |region| and |offset| is the offset that will be mapped. |region| is
// not retained and is used only in the constructor.
......@@ -58,7 +58,7 @@ class MEDIA_EXPORT WritableUnalignedMapping {
size_t size,
off_t offset);
// As above, but creates from a handle. This region will not own the handle.
// As above, but creates from a handle. This region will own the handle.
// DEPRECATED: this should be used only for the legacy shared memory
// conversion project, see https://crbug.com/795291.
WritableUnalignedMapping(const base::SharedMemoryHandle& handle,
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment