2 Commits

Author	SHA1	Message	Date
Ehsan Akhgari	b6e35bb4b4	Bug 1118486 - Part 1: Use = delete instead of MOZ_DELETE directly; r=Waldo ... Most of this patch (with the exception of dom/bindings/Codegen.py) was generated by the following bash script: #!/bin/bash function convert() { echo "Converting $1 to $2..." find . ! -wholename "*nsprpub*" \ ! -wholename "*security/nss*" \ ! -wholename "*/.hg*" \ ! -wholename "*/.git*" \ ! -wholename "obj-*" \ -type f \ \( -iname "*.cpp" \ -o -iname "*.h" \ -o -iname "*.cc" \ -o -iname "*.idl" \ -o -iname "*.ipdl" \ -o -iname "*.ipdlh" \ -o -iname "*.mm" \) | \ xargs -n 1 sed -i -e "s/\b$1\b/$2/g" } convert MOZ_DELETE '= delete'	2015-01-08 23:19:05 -05:00
Paul Adenot	f5c2676219	Bug 1085356 - Better handling of OSX audio output devices switching when SourceMediaStream are present in the MSG. r=jesup ... On OSX, when the audio output device changes, the OS will call the audio callbacks in weird patterns, if at all, during a period of ~1s. If real-time SourceMediaStreams are present in the MediaStreamGraph, this means buffering will occur, and the overall latency between the MediaStreamGraph insertion time, and the actual output time will grow. To fix this, we detect when the output device changes, and we switch temporarily to a SystemClockDriver, that will pull from the SourceMediaStream, and simply discard all input data. Then, when we get audio callbacks called reliably (basically, when OSX is done switching to the other output), we switch back to the previous AudioCallbackDriver. We keep the previous AudioCallbackDriver alive using a self-reference. If an AudioCallbackDriver has a self-reference, that means it's in a state when a device is switching, so it's not linked to an MSG per se.	2014-10-22 16:12:29 +02:00