The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/2ad785825859b6be6964d484a1d6a5f3f2c2ded5

commit 2ad785825859b6be6964d484a1d6a5f3f2c2ded5
Author: Matt Wolenetz <wolenetz@chromium.org>
Date: Wed Sep 06 01:45:17 2017

MSE: Expand pipeline integration fuzzer mimetype/codec coverage

Adds the following mediasource_*_pipeline_integration_fuzzer targets:
  ADTS
  MP2T_AACLC
  MP2T_AACSBR
  MP2T_AVC
  MP2T_MP3
  MP4_AACLC
  MP4_AACSBR
  WEBM_OPUS
  WEBM_VORBIS
  WEBM_VP8
And a subset of muxed A/V:
  MP2T_AACLC_AVC
  MP4_AACLC_AVC
  WEBM_OPUS_VP9

Note: No MSE pipeline-integration fuzzing of HEVC, DV, AC3/EAC3, or MP2T
HLS with SAMPLE-AES encryption is included; those are only in Chromecast
builds and use hardware-specific decode/rendering.

BUG= 759752 
TEST=All the mediasource_*_pipeline_integration_fuzzers appear to make
at least minimal progress locally (getting far enough to emit coded
frames from the parser) on a narrow manually selected subset of the
seed_corpus.

Change-Id: Id48e709a78fb9ffe48323d03dd89f91ed4fe0b88
Reviewed-on: https://chromium-review.googlesource.com/651070
Commit-Queue: Matthew Wolenetz <wolenetz@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#499841}
[modify] https://crrev.com/2ad785825859b6be6964d484a1d6a5f3f2c2ded5/media/test/BUILD.gn
[modify] https://crrev.com/2ad785825859b6be6964d484a1d6a5f3f2c2ded5/media/test/pipeline_integration_fuzzertest.cc

The majority of the basic MSE parser fuzzer coverage is landed as of #1 (excluding some Chromecast-specific pieces that it mentions in the CL description.)

Beyond #1, I'm keeping this bug open to track additional MSE API behavior fuzzing (e.g. do some seeking, append mode changing, append window modifications, attempt to decode stuff in buffered ranges, etc.) as well as perhaps add more mimetype/codec combos. 

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot