Bug 1132953 - Zero AsmJSModule::CodeRange and AsmJSModule::ExportedFunction::pod on construction, to avoid Valgrind warnings. r=luke.

NO BUG - Fix reStructuredText warnings Sphinx has been complaining about a number of reStructuredText warnings for a while. Fix all the ones in .rst files. Not asking for review because this is docs only and changing .rst files can't break anything important. DONTBUILD (NPOTB)

Bug 1132771 - Fix grammar nits in moz.build documentation These were left over from a Ms2ger review and weren't seen before landing. DONTBUILD (NPOTB)

Bug 1135558 - Disable WebM support for MSE; r=rillian

Bug 1135544 - Create an abstract base class for a track demuxer; r=kinetik

Bug 1135785 - Hoist some work onto the state machine thread and tighten down our assertions. r=cpearce

Bug 1135785 - Stop manually resetting mCurrentSeekTarget in MDSM::SeekCompleted and rely on the AutoSetOnScopeExit instead. r=cpearce For some reason the current code is resetting it twice - once explicitly and once with the AutoSetOnScopeExit. To make matters worse, we have a monitor drop between the two. So when DecodeSeek runs on the decode task queue but SeekCompleted runs on the state machine thread, we can start another DecodeSeek during the monitor drop, and then clobber it with the AutoSeetOnScopeExit, causing us to hang. This is a non-issue with the patches in bug 1135170, but necessary to make the patches in this bug independently green.

Bug 1135785 - Stop invoking StopPlayback in SetDormant. r=cpearce This already gets incoded in the DECODER_STATE_DORMANT case of RunStateMachine, which will run momentarily on the state machine thread. Doing this allows us to avoid calling StopPlayback on the main thread.

Bug 1135785 - Return samples on state machine thread. r=cpearce This is necessary because we're going to want to start disconnecting sample and seek requests directly from the state machine thread, and the machinery asserts that disconnection happens on the same thread as resolution. More generally, this is the right thing to do architecturally, and will help wean us off the monitor.

Bug 1135785 - Make DecodeError safe to run on any thread. r=cpearce This is necessary so that we can make On{Audio,Video}{,Not}Decoded run on the state machine thread in the next patch.

Bug 1135785 - Make MediaTaskQueue::IsCurrentThreadIn actually do the right thing on release builds. r=cpearce The current situation is really dangerous because it compiles on release builds, but just lies. This bit me when I tried to use it for non-assertion purposes. My reading of the reasoning for the current setup in bug 968016 is that we didn't trust nsIEventTarget::IsCurrentThreadOn or thought it might be slow. But the implementation of MediaTaskQueue::IsCurrentThreadIn doesn't actually use that, and indeed currently does all of the work for this feature in release builds anyway.

Bug 1135785 - Introduce a 1-argument overload of ProxyMediaCall. r=cpearce

Bug 1138072 - Don't defer reading to a closed stream. r=roc Other streams in the list bail out of the servicing loop if they're closed, so we can wait indefinitely.

Bug 1132771 - Implement file-info mach command; r=glandium Now that we have a mechanism for defining file-based metadata, let's add a mach command to interface with it. Currently, we limit ourselves to simple Bugzilla data dumping. Features will be added over time.

Bug 1132771 - Define some bug components; r=glandium This patch defines bug components for code that I have historically touched.

Bug 1132771 - Add Files to moz.build with ability to define Bugzilla component; r=glandium The Files sub-context allows us to attach metadata to files based on pattern matching rules. Patterns are matched against files in a last-write-wins fashion. The sub-context defines the BUG_COMPONENT variable, which is a 2-tuple (actually a named tuple) defining the Bugzilla product and component for files. There are no consumers yet. But an eventual use case will be to suggest a bug component for a patch/commit. Another will be to automatically suggest a bug component for a failing test.

Bug 1132771 - Support and test for reading without a config object; r=glandium We want the ability to read data from any moz.build file without needing a full build configuration (running configure). This will enable tools to consume metadata by merely having a copy of the source code and nothing more. This commit creates the EmptyConfig object. It is a config object that - as its name implies - is empty. It will be used for reading moz.build files in "no config" mode. Many moz.build files make assumptions that variables in CONFIG are defined and that they are strings. We create the EmptyValue type that behaves like an empty unicode string. Since moz.build files also do some type checking, we carve an exemption for EmptyValue, just like we do for None. We add a test to verify that reading moz.build files in "no config" mode works. This required some minor changes to existing moz.build files to make them work in the new execution mode.

Bug 1132771 - Add a test for reading all moz.build files in filesystem traversal mode; r=glandium moz.build files should execute in filesystem traversal mode. Add a test that verifies this is true. This test performs a brute force filesystem scan to find relevant moz.build files. This can be a little slow. That's unfortunate. But it's a price we need to pay in order to ensure metadata extraction mode continues to work.

Bug 1132771 - Support reading relevant moz.build files; r=glandium Building on top of the API to retrieve relevant moz.build files for a given path, we introduce a moz.build reading API that reads all moz.build files relevant to a given set of paths. We plan to use this new API to read metadata from moz.build files relevant to a set of files. This patch changes the generator behavior of read_mozbuild to emit the main context before any processing occurs. This allows downstream consumers to manipulate state of the context before things like directory processing occurs. We utilize this capability in the new reading API to forcefully declare the directory traversal order for processed moz.build files, overriding DIRS and similar variables. Since variable exporting doesn't work reliably in this new traversal mode, variable exporting no-ops when this mode is activated.

Bug 1132771 - Pass special types down to sandboxes via metadata; r=glandium Currently, MozSandbox assumes that the FUNCTIONS, SPECIAL_VARIABLES, and SUBCONTEXTS data structures are the instances that should be associated with the sandbox. As we introduce new moz.build processing modes that wish to change processing behavior, it is necessary for them to have control over these special symbols. This patch moves the declaration of these types to the special metadata dictionary which is inherited during recursion. The "read_topsrcdir" API now explicitly passes the initial metadata into "read_mozbuild".