8b00dd26d6b586ac52cec8d7e636c049afaaae28: Bug 1421134. P2 - run MediaCacheStream::SetReadMode() off the main thread. r=bechen,gerald
JW Wang <jwwang@mozilla.com> - Tue, 28 Nov 2017 10:51:47 +0800 - rev 438661
Push 120 by fmarier@mozilla.com at Wed, 29 Nov 2017 22:27:43 +0000
Bug 1421134. P2 - run MediaCacheStream::SetReadMode() off the main thread. r=bechen,gerald MozReview-Commit-ID: A6ui5dtWhNt
b89049710a24aff55abe75f6d89dc59f8b353a9d: Bug 1421134. P1 - default MediaCacheStream::mCurrentMode to MODE_METADATA. r=bechen,gerald
JW Wang <jwwang@mozilla.com> - Tue, 28 Nov 2017 10:43:50 +0800 - rev 438660
Push 120 by fmarier@mozilla.com at Wed, 29 Nov 2017 22:27:43 +0000
Bug 1421134. P1 - default MediaCacheStream::mCurrentMode to MODE_METADATA. r=bechen,gerald We always read metadata when decoding starts. This allows us to remove the call to mResource->SetReadMode(MediaCacheStream::MODE_METADATA) in ChannelMediaDecoder::Load(). MozReview-Commit-ID: AQMq4HxDZdT
8316864557a24cb7c50ff18a6cd7d0939e87bf31: Bug 1420819 - run MediaCache::Flush() off the main thread. r=bechen,gerald
JW Wang <jwwang@mozilla.com> - Mon, 27 Nov 2017 15:04:21 +0800 - rev 438659
Push 120 by fmarier@mozilla.com at Wed, 29 Nov 2017 22:27:43 +0000
Bug 1420819 - run MediaCache::Flush() off the main thread. r=bechen,gerald MozReview-Commit-ID: 4QR1TvORZlz
eff8b66ce5c777b9084b74f416c6e7400a0ed430: Bug 1420355 - Statically link DMD. r=njn
Mike Hommey <mh+mozilla@glandium.org> - Tue, 28 Nov 2017 08:10:48 +0900 - rev 438658
Push 120 by fmarier@mozilla.com at Wed, 29 Nov 2017 22:27:43 +0000
Bug 1420355 - Statically link DMD. r=njn
076e21f3b25ec4598f64208d02cbbc9104d99949: Bug 1420355 - Allow to statically link replace-malloc libraries. r=njn
Mike Hommey <mh+mozilla@glandium.org> - Thu, 23 Nov 2017 17:24:19 +0900 - rev 438657
Push 120 by fmarier@mozilla.com at Wed, 29 Nov 2017 22:27:43 +0000
Bug 1420355 - Allow to statically link replace-malloc libraries. r=njn And statically link logalloc. Statically linking is the default, except when building with --enable-project=memory, allowing to use the generated libraries from such builds with Firefox.
f1d96b6ee076dbb45a1d82a572f2ad1cd6d20ab2: Bug 1420355 - Don't initialize DMD if the DMD environment variable is not given. r=njn
Mike Hommey <mh+mozilla@glandium.org> - Tue, 28 Nov 2017 08:10:07 +0900 - rev 438656
Push 120 by fmarier@mozilla.com at Wed, 29 Nov 2017 22:27:43 +0000
Bug 1420355 - Don't initialize DMD if the DMD environment variable is not given. r=njn This makes things slightly more inconvenient (having to set two environment variables instead of one for the simplest case) until a few patches down the line, when DMD is statically linked, at which point it will get down to one environment variable every time.
b19b3307075a21525643e6db6487929c01b87b45: Bug 1420355 - Don't initialize logalloc if MALLOC_LOG is not given. r=njn
Mike Hommey <mh+mozilla@glandium.org> - Thu, 23 Nov 2017 13:54:16 +0900 - rev 438655
Push 120 by fmarier@mozilla.com at Wed, 29 Nov 2017 22:27:43 +0000
Bug 1420355 - Don't initialize logalloc if MALLOC_LOG is not given. r=njn Now that replace_init can opt-out of registering the replace-malloc functions, don't do so when MALLOC_LOG was not set in the environment. While one would normally set MALLOC_LOG alongside one of the environment variable necessary to load the replace-malloc library, we're also going, in a subsequent change, to allow statically linking replace-malloc libraries, taking full advantage of this change.
a19bce0cd06cf37d1732717ebfc0b9a5fae7fe84: Bug 1420355 - Remove fallbacks when DMD is initializing. r=njn
Mike Hommey <mh+mozilla@glandium.org> - Tue, 28 Nov 2017 08:05:58 +0900 - rev 438654
Push 120 by fmarier@mozilla.com at Wed, 29 Nov 2017 22:27:43 +0000
Bug 1420355 - Remove fallbacks when DMD is initializing. r=njn As of bug 1420353, DMD's replace_* functions can't be called before replace_init places them in the malloc function table, which only happens after DMD::Init has run, meaning DMD is always initialized by the time any of its replace_* function can be called.
921a1441fd228863441faa39e83a50499d7343d1: Bug 1420355 - Don't declare replace_* functions in replace_malloc.h. r=njn
Mike Hommey <mh+mozilla@glandium.org> - Tue, 28 Nov 2017 07:18:15 +0900 - rev 438653
Push 120 by fmarier@mozilla.com at Wed, 29 Nov 2017 22:27:43 +0000
Bug 1420355 - Don't declare replace_* functions in replace_malloc.h. r=njn The original purpose of those declarations was to avoid the function definitions being wrong, as well as forcing them being exported properly (as extern "C", as weak symbols when necessary, etc.), but: - The implementations being C++, function overloads simply allowed functions with the same name to have a different signature. - As of bug 1420353, the functions don't need to be exported anymore, nor do we care whether their symbols are mangled. Furthermore, they're now being assigned to function table fields, meaning there is type checking in place, now. So all in all, these declarations can be removed. Also, as further down the line we're going to statically link the replace-malloc libraries, avoid symbol conflicts by making those functions static.
30920e0f5df4592f2edcb996fbc3bc66290a8138: Bug 1420355 - Don't link logalloc against the static runtime on Windows. r=njn
Mike Hommey <mh+mozilla@glandium.org> - Tue, 28 Nov 2017 17:11:40 +0900 - rev 438652
Push 120 by fmarier@mozilla.com at Wed, 29 Nov 2017 22:27:43 +0000
Bug 1420355 - Don't link logalloc against the static runtime on Windows. r=njn This was never strictly required (for instance, DMD doesn't do that), and would make things harder with the subsequent changes.
a77d1ee6227a31c27e82f49eb7bf8b4e907496e0: Bug 1421478: Clarify comment in handlerDataCleanup.h. r=aklotz
James Teh <jteh@mozilla.com> - Wed, 29 Nov 2017 10:18:01 +1000 - rev 438651
Push 120 by fmarier@mozilla.com at Wed, 29 Nov 2017 22:27:43 +0000
Bug 1421478: Clarify comment in handlerDataCleanup.h. r=aklotz MozReview-Commit-ID: EVzuqVMl7Ck
660d64624ea968587b752e8669e7b3b895b22a00: Bug 1421197 - use 64-bit for restyle generation counters to avoid overflow issues. r=heycam
Jeremy Chen <jeremychen@mozilla.com> - Tue, 28 Nov 2017 17:42:22 +0800 - rev 438650
Push 120 by fmarier@mozilla.com at Wed, 29 Nov 2017 22:27:43 +0000
Bug 1421197 - use 64-bit for restyle generation counters to avoid overflow issues. r=heycam It is expected to use 64-bit for all the restyle generation counters, since the getter methods all return uint64_t type at present. However, we're using uint32_t for the actual counter variables, which means the potential overflow issue is not avoided. In this patch, we use 64-bit for the restyle generation counters, so the overflow issue can be avoided as expected. MozReview-Commit-ID: 2y2afIcuwvc
3c8385b19b24b182ddfdc35ffc746168a4cb9e83: Bug 1420810 - record why we are syncing for most syncs initiated by the scheduler. r=eoger
Mark Hammond <mhammond@skippinet.com.au> - Mon, 27 Nov 2017 17:32:05 +1100 - rev 438649
Push 120 by fmarier@mozilla.com at Wed, 29 Nov 2017 22:27:43 +0000
Bug 1420810 - record why we are syncing for most syncs initiated by the scheduler. r=eoger MozReview-Commit-ID: 1ntqG5yQi7q
8cbc145b9f915eb5911141be9266c909f8ac26af: Backed out 7 changesets (bug 1420355) for mass failures on OS X and Android. r=backout on a CLOSED TREE
Csoregi Natalia <ncsoregi@mozilla.com> - Wed, 29 Nov 2017 03:08:46 +0200 - rev 438648
Push 120 by fmarier@mozilla.com at Wed, 29 Nov 2017 22:27:43 +0000
Backed out 7 changesets (bug 1420355) for mass failures on OS X and Android. r=backout on a CLOSED TREE Backed out changeset a7ed89e13a4c (bug 1420355) Backed out changeset fd6702e6e0a0 (bug 1420355) Backed out changeset 0479dda078a2 (bug 1420355) Backed out changeset e69357ccca9e (bug 1420355) Backed out changeset 3742a4b69ba2 (bug 1420355) Backed out changeset 451cd087922f (bug 1420355) Backed out changeset d80b5c4e1dd0 (bug 1420355)
a7ed89e13a4cc4ce7b8ebe4dd99bce5160852003: Bug 1420355 - Statically link DMD. r=njn
Mike Hommey <mh+mozilla@glandium.org> - Tue, 28 Nov 2017 08:10:48 +0900 - rev 438647
Push 120 by fmarier@mozilla.com at Wed, 29 Nov 2017 22:27:43 +0000
Bug 1420355 - Statically link DMD. r=njn
fd6702e6e0a0a24e2d5d6c98b5467768cff9dbc2: Bug 1420355 - Allow to statically link replace-malloc libraries. r=njn
Mike Hommey <mh+mozilla@glandium.org> - Thu, 23 Nov 2017 17:24:19 +0900 - rev 438646
Push 120 by fmarier@mozilla.com at Wed, 29 Nov 2017 22:27:43 +0000
Bug 1420355 - Allow to statically link replace-malloc libraries. r=njn And statically link logalloc. Statically linking is the default, except when building with --enable-project=memory, allowing to use the generated libraries from such builds with Firefox.
0479dda078a2ab5a9be9ebf5b82705a332ba75bd: Bug 1420355 - Don't initialize DMD if the DMD environment variable is not given. r=njn
Mike Hommey <mh+mozilla@glandium.org> - Tue, 28 Nov 2017 08:10:07 +0900 - rev 438645
Push 120 by fmarier@mozilla.com at Wed, 29 Nov 2017 22:27:43 +0000
Bug 1420355 - Don't initialize DMD if the DMD environment variable is not given. r=njn This makes things slightly more inconvenient (having to set two environment variables instead of one for the simplest case) until a few patches down the line, when DMD is statically linked, at which point it will get down to one environment variable every time.
e69357ccca9e26deb32ef6c5a4e445673fe4ada9: Bug 1420355 - Don't initialize logalloc if MALLOC_LOG is not given. r=njn
Mike Hommey <mh+mozilla@glandium.org> - Thu, 23 Nov 2017 13:54:16 +0900 - rev 438644
Push 120 by fmarier@mozilla.com at Wed, 29 Nov 2017 22:27:43 +0000
Bug 1420355 - Don't initialize logalloc if MALLOC_LOG is not given. r=njn Now that replace_init can opt-out of registering the replace-malloc functions, don't do so when MALLOC_LOG was not set in the environment. While one would normally set MALLOC_LOG alongside one of the environment variable necessary to load the replace-malloc library, we're also going, in a subsequent change, to allow statically linking replace-malloc libraries, taking full advantage of this change.
3742a4b69ba20bdcc47ee8bfa7d56268be944ae1: Bug 1420355 - Remove fallbacks when DMD is initializing. r=njn
Mike Hommey <mh+mozilla@glandium.org> - Tue, 28 Nov 2017 08:05:58 +0900 - rev 438643
Push 120 by fmarier@mozilla.com at Wed, 29 Nov 2017 22:27:43 +0000
Bug 1420355 - Remove fallbacks when DMD is initializing. r=njn As of bug 1420353, DMD's replace_* functions can't be called before replace_init places them in the malloc function table, which only happens after DMD::Init has run, meaning DMD is always initialized by the time any of its replace_* function can be called.
451cd087922f1f1f0e66de9196b7b99e36c8072e: Bug 1420355 - Don't declare replace_* functions in replace_malloc.h. r=njn
Mike Hommey <mh+mozilla@glandium.org> - Tue, 28 Nov 2017 07:18:15 +0900 - rev 438642
Push 120 by fmarier@mozilla.com at Wed, 29 Nov 2017 22:27:43 +0000
Bug 1420355 - Don't declare replace_* functions in replace_malloc.h. r=njn The original purpose of those declarations was to avoid the function definitions being wrong, as well as forcing them being exported properly (as extern "C", as weak symbols when necessary, etc.), but: - The implementations being C++, function overloads simply allowed functions with the same name to have a different signature. - As of bug 1420353, the functions don't need to be exported anymore, nor do we care whether their symbols are mangled. Furthermore, they're now being assigned to function table fields, meaning there is type checking in place, now. So all in all, these declarations can be removed. Also, as further down the line we're going to statically link the replace-malloc libraries, avoid symbol conflicts by making those functions static.
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip