ade013fb7d6976b03f3fe990d2b5008d02970869: Bug 1455040 - Enable tab hiding API by default r?mixedpuppy draft
Mark Striemer <mstriemer@mozilla.com> - Mon, 07 May 2018 12:27:41 -0500 - rev 792127
Push 109002 by bmo:mstriemer@mozilla.com at Mon, 07 May 2018 18:12:08 +0000
Bug 1455040 - Enable tab hiding API by default r?mixedpuppy MozReview-Commit-ID: HtzpV7bySeY
8495f7960c639daa86ae0d818073e9a6c5f660cc: Bug 1352015 - Part 2: Build with Android O SDK. r?nalexander draft
Jan Henning <jh+bugzilla@buttercookie.de> - Sun, 06 May 2018 17:38:22 +0200 - rev 792126
Push 109001 by mozilla@buttercookie.de at Mon, 07 May 2018 18:08:46 +0000
Bug 1352015 - Part 2: Build with Android O SDK. r?nalexander MozReview-Commit-ID: BhqwL4nyj6J
9d4e58dd2bbf81baf9e16f3dd3f25bba9ec9cf7c: Bug 1176019 - Cache layers of background tabs r?mconley draft
Doug Thayer <dothayer@mozilla.com> - Mon, 16 Apr 2018 15:35:41 -0700 - rev 792125
Push 109000 by bmo:dothayer@mozilla.com at Mon, 07 May 2018 17:56:30 +0000
Bug 1176019 - Cache layers of background tabs r?mconley We maintain a simple LRU cache of tab layers by setting their docShellIsActive = false with preserveLayers(true). Once they are pushed out of the cache by more recently used tabs, their layers are discarded. Luckily most of the complexity of this could be contained in the AsyncTabSwitcher - the one change that had to sit outside of that was moving the aTab.closing = true earlier in the removeTab call, so that we could use that information to eagerly evict tabs from the cache. This was to address a leak in a few tests on try. MozReview-Commit-ID: 2E3uU8LEYkD
ef0b520af35dfb8873730da914368455826e838c: Bug 1455040 - Enable tab hiding API by default r?mixedpuppy draft
Mark Striemer <mstriemer@mozilla.com> - Mon, 07 May 2018 12:27:41 -0500 - rev 792124
Push 108999 by bmo:mstriemer@mozilla.com at Mon, 07 May 2018 17:43:17 +0000
Bug 1455040 - Enable tab hiding API by default r?mixedpuppy MozReview-Commit-ID: HtzpV7bySeY
5ca16f23556d5d49ff93bdaf46ee237ad8c1677f: Bug 1444546 - Post: Remove add_java_jar and support. r=froydnj draft
Nick Alexander <nalexander@mozilla.com> - Tue, 06 Mar 2018 14:48:20 -0800 - rev 792123
Push 108998 by nalexander@mozilla.com at Mon, 07 May 2018 17:26:10 +0000
Bug 1444546 - Post: Remove add_java_jar and support. r=froydnj MozReview-Commit-ID: J6E2ZOs9r3P
b2e4aad7024123b42988b5ceb471d5be8a307839: Bug 1444546 - Part 4b: Make AnnotationProcessor avoid writing, like Python's FileAvoidWrite. r=jchen draft
Nick Alexander <nalexander@mozilla.com> - Mon, 26 Mar 2018 09:36:19 -0700 - rev 792122
Push 108998 by nalexander@mozilla.com at Mon, 07 May 2018 17:26:10 +0000
Bug 1444546 - Part 4b: Make AnnotationProcessor avoid writing, like Python's FileAvoidWrite. r=jchen This allows us to invoke AnnotationProcessor more than is strictly necessary and not trigger expensive native code compilations unless the native code has actually evolved. MozReview-Commit-ID: H1BIzJsdyIh
201247e7df2534686759007284bb9244b4b9abb1: Bug 1444546 - Part 4: Use GENERATED_FILES for Android JNI wrapper generation. r=jchen,froydnj draft
Nick Alexander <nalexander@mozilla.com> - Tue, 06 Mar 2018 20:09:37 -0800 - rev 792121
Push 108998 by nalexander@mozilla.com at Mon, 07 May 2018 17:26:10 +0000
Bug 1444546 - Part 4: Use GENERATED_FILES for Android JNI wrapper generation. r=jchen,froydnj MozReview-Commit-ID: 1IjoQdEMqr8
d977b46daedf2270003604629a3935e8133e8f52: Bug 1444546 - Part 3: Use GENERATED_FILES for Android SDK bindings generation. r=jchen,froydnj draft
Nick Alexander <nalexander@mozilla.com> - Tue, 06 Mar 2018 19:19:48 -0800 - rev 792120
Push 108998 by nalexander@mozilla.com at Mon, 07 May 2018 17:26:10 +0000
Bug 1444546 - Part 3: Use GENERATED_FILES for Android SDK bindings generation. r=jchen,froydnj MozReview-Commit-ID: 2blmzKTvpj3
38536d12c658fd71dd13e9d123f558a606cd1312: Bug 1445392: Remove pending slots from the docgroup on unlink. r?smaug draft
Emilio Cobos Álvarez <emilio@crisal.io> - Mon, 07 May 2018 19:12:29 +0200 - rev 792119
Push 108997 by bmo:emilio@crisal.io at Mon, 07 May 2018 17:25:13 +0000
Bug 1445392: Remove pending slots from the docgroup on unlink. r?smaug This fixes the leak. However, I suspect it's not the right thing to do, given the same test-case asserts later with: mPendingMicroTaskRunnables.empty() In CycleCollectedJSContext.cpp. That microtask is posted from DocGroup::SignalSlotChange, from the UnbindFromTree that happens on the <div> during unlink, and I suspect we should prevent it, somehow. If this is a good excuse to pass down a "are we unlinking" bit to UnbindFromTree, I can do that. MozReview-Commit-ID: 6sJgMqZa80U
8e6f0c39cea0b829f67ed9ee0cac34d2002ddc52: Bug 1445392: Traverse ShadowRoot's mStyleSheets for consistency with nsDocument. r?smaug draft
Emilio Cobos Álvarez <emilio@crisal.io> - Mon, 07 May 2018 19:11:13 +0200 - rev 792118
Push 108997 by bmo:emilio@crisal.io at Mon, 07 May 2018 17:25:13 +0000
Bug 1445392: Traverse ShadowRoot's mStyleSheets for consistency with nsDocument. r?smaug Ended up not being the cause of the leak, but worth doing as well IMO, or worth removing nsDocument's traversal otherwise. MozReview-Commit-ID: FlkA0Mq9M3J
8a3a026f4b7e5a2d3803605c82ae61507526c567: Bug 1445392: Make HTMLSlotElement slot change event stuff not linear. r?smaug draft
Emilio Cobos Álvarez <emilio@crisal.io> - Mon, 07 May 2018 19:09:19 +0200 - rev 792117
Push 108997 by bmo:emilio@crisal.io at Mon, 07 May 2018 17:25:13 +0000
Bug 1445392: Make HTMLSlotElement slot change event stuff not linear. r?smaug Also fix refcount churn in nsDOMMutationObserver and such. This is a preliminar patch which I think is worth landing regardless of whether the next is the right thing to do. MozReview-Commit-ID: GwEB0LZY7Ss
516c782518b691eb51c9103306de542e43449150: Bug 1444546 - Post: Remove add_java_jar and support. r=Build draft
Nick Alexander <nalexander@mozilla.com> - Tue, 06 Mar 2018 14:48:20 -0800 - rev 792116
Push 108996 by nalexander@mozilla.com at Mon, 07 May 2018 17:23:26 +0000
Bug 1444546 - Post: Remove add_java_jar and support. r=Build MozReview-Commit-ID: J6E2ZOs9r3P
c1db839a167687d5066837a63101fb485f439780: Bug 1444546 - Part 4b: Make AnnotationProcessor avoid writing, like Python's FileAvoidWrite. r=jchen draft
Nick Alexander <nalexander@mozilla.com> - Mon, 26 Mar 2018 09:36:19 -0700 - rev 792115
Push 108996 by nalexander@mozilla.com at Mon, 07 May 2018 17:23:26 +0000
Bug 1444546 - Part 4b: Make AnnotationProcessor avoid writing, like Python's FileAvoidWrite. r=jchen This allows us to invoke AnnotationProcessor more than is strictly necessary and not trigger expensive native code compilations unless the native code has actually evolved. MozReview-Commit-ID: H1BIzJsdyIh
a56a65d8e48275ca01d861ee864f54934eda3175: Bug 1444546 - Part 4: Use GENERATED_FILES for Android JNI wrapper generation. r=jchen,Build draft
Nick Alexander <nalexander@mozilla.com> - Tue, 06 Mar 2018 20:09:37 -0800 - rev 792114
Push 108996 by nalexander@mozilla.com at Mon, 07 May 2018 17:23:26 +0000
Bug 1444546 - Part 4: Use GENERATED_FILES for Android JNI wrapper generation. r=jchen,Build MozReview-Commit-ID: 1IjoQdEMqr8
3bb0dfa4b20de712607e2f858031a5060eaf606e: Bug 1444546 - Part 3: Use GENERATED_FILES for Android SDK bindings generation. r=jchen,Build draft
Nick Alexander <nalexander@mozilla.com> - Tue, 06 Mar 2018 19:19:48 -0800 - rev 792113
Push 108996 by nalexander@mozilla.com at Mon, 07 May 2018 17:23:26 +0000
Bug 1444546 - Part 3: Use GENERATED_FILES for Android SDK bindings generation. r=jchen,Build MozReview-Commit-ID: 2blmzKTvpj3
d99b74a0a1e0bb3e8f4d4540978328388e5c2e42: Bug 1444546 - Part 2: Build annotationProcessors with Gradle. r=jchen draft
Nick Alexander <nalexander@mozilla.com> - Thu, 22 Feb 2018 16:11:14 -0800 - rev 792112
Push 108996 by nalexander@mozilla.com at Mon, 07 May 2018 17:23:26 +0000
Bug 1444546 - Part 2: Build annotationProcessors with Gradle. r=jchen We want annotationProcessors to be compiled and archived into a JAR at build time, ready to generate JNI wrappers. (That is, until we turn the whole thing into a real annotation processor.) But even if we do use a real annotation processor, we still need to generate SDK bindings, which is less clearly expressed as an annotation processor. (It's more of a build step.) Gradle provides a huge number of ways to organize build logic to achieve this: see https://docs.gradle.org/current/userguide/organizing_build_logic.html. Unfortunately, the best such way -- putting the code into $topsrcdir/buildSrc -- has key disadvantages: 1) it pollutes the top-level $topsrcdir, and there's no way to change the location of buildSrc (https://github.com/gradle/gradle/issues/2472); 2) it's complicated to have a dependent project (mobile/android/annotations) expose its code via a buildSrc project; 3) using buildSrc at all appears to conflict with the Android-Gradle plugin version that we are using. Therefore, this commit does something much simpler: it adds a Java-only project and uses the resulting Gradle "Jar" task and archive output as input to the existing Gradle "generate JNI wrappers" task. MozReview-Commit-ID: 2OyYLPneE1M
65b85ec338cc5a7cb12afc2ad7678271339a6e89: Bug 1444546 - Part 1: hg mv build/annotationProcessors mobile/android/annotations. r=jchen draft
Nick Alexander <nalexander@mozilla.com> - Thu, 22 Feb 2018 13:51:15 -0800 - rev 792111
Push 108996 by nalexander@mozilla.com at Mon, 07 May 2018 17:23:26 +0000
Bug 1444546 - Part 1: hg mv build/annotationProcessors mobile/android/annotations. r=jchen MozReview-Commit-ID: J3Wz83vWAVX
44a77d9abac8f346a3d317a68682002c15d0925d: Bug 1445392: Remove pending slots from the docgroup on unlink. r?smaug draft
Emilio Cobos Álvarez <emilio@crisal.io> - Mon, 07 May 2018 19:12:29 +0200 - rev 792110
Push 108995 by bmo:emilio@crisal.io at Mon, 07 May 2018 17:19:57 +0000
Bug 1445392: Remove pending slots from the docgroup on unlink. r?smaug This fixes the leak. However, I suspect it's not the right thing to do, given the same test-case asserts later with: mPendingMicroTaskRunnables.empty() In CycleCollectedJSContext.cpp. That microtask is posted from DocGroup::SignalSlotChange, from the UnbindFromTree that happens on the <div> during unlink, and I suspect we should prevent it, somehow. If this is a good excuse to pass down a "are we unlinking" bit to UnbindFromTree, I can do that. MozReview-Commit-ID: 6sJgMqZa80U
06c138bfbf263a699baa677191224423e0e5b469: Bug 1445392: Traverse ShadowRoot's mStyleSheets for consistency with nsDocument. r?smaug draft
Emilio Cobos Álvarez <emilio@crisal.io> - Mon, 07 May 2018 19:11:13 +0200 - rev 792109
Push 108995 by bmo:emilio@crisal.io at Mon, 07 May 2018 17:19:57 +0000
Bug 1445392: Traverse ShadowRoot's mStyleSheets for consistency with nsDocument. r?smaug Ended up not being the cause of the leak, but worth doing as well IMO, or worth removing nsDocument's traversal otherwise. MozReview-Commit-ID: FlkA0Mq9M3J
93f72a04ca55ea767fff4fd727acdaacb0d34695: Bug 1445392: Make HTMLSlotElement slot change event stuff not linear. r?smaug draft
Emilio Cobos Álvarez <emilio@crisal.io> - Mon, 07 May 2018 19:09:19 +0200 - rev 792108
Push 108995 by bmo:emilio@crisal.io at Mon, 07 May 2018 17:19:57 +0000
Bug 1445392: Make HTMLSlotElement slot change event stuff not linear. r?smaug Also fix refcount churn in nsDOMMutationObserver and such. This is a preliminar patch which I think is worth landing regardless of whether the next is the right thing to do. MozReview-Commit-ID: GwEB0LZY7Ss
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip