searching for memory leak
c8811545863b: Backed out 3 changesets (bug 1505777) for linux leakcheck failures on a CLOSED TREE
Gurzau Raul <rgurzau@mozilla.com> - Fri, 09 Nov 2018 01:05:49 +0200 - rev 445327
Push 35014 by dvarga@mozilla.com at Fri, 09 Nov 2018 10:01:40 +0000
Backed out 3 changesets (bug 1505777) for linux leakcheck failures on a CLOSED TREE Backed out changeset 027bf8dee1e5 (bug 1505777) Backed out changeset 29649174d3e7 (bug 1505777) Backed out changeset 6fe8e6a201ed (bug 1505777)
cb4df8a62231: Bug 1501225 [wpt PR 13674] - Revert "Reland "bindings: Implement timers with V8Function"", a=testonly
Timothy Gu <timothygu@chromium.org> - Thu, 01 Nov 2018 11:21:44 +0000 - rev 445006
Push 35006 by aiakab@mozilla.com at Wed, 07 Nov 2018 21:51:52 +0000
Bug 1501225 [wpt PR 13674] - Revert "Reland "bindings: Implement timers with V8Function"", a=testonly Automatic update from web-platform-testsRevert "Reland "bindings: Implement timers with V8Function"" This reverts commit 17f4e7d2ec13d6112dfcd8aa253f340bdb00d395. Reason for revert: Still breaks ASAN Original change's description: > Reland "bindings: Implement timers with V8Function" > > This is a reland of 254369a5f6df06c2c6be067d14c2cb2a036ba173. It addresses bug > 888025 by adding ASAN test expectations, as the relevant V8 feature does not > yet support running on ASAN builds. > > Original change's description: > > bindings: Implement timers with V8Function > > > > This fixes bug 866610 by using the IDL infrastructure to properly enter > > the v8::Context before calling the registered callback. > > > > Also ensure eager finalization of ScheduledAction in DOMTimer to > > prevent a memory leak. Added two more effective DCHECKs to confirm. > > > > Bug: 866610 > > Change-Id: I37d7bd05f035fe31856cfe68bae51aa0632cd3b1 > > Reviewed-on: https://chromium-review.googlesource.com/1220486 > > Reviewed-by: Nate Chapin <japhet@chromium.org> > > Reviewed-by: Yuki Shiino <yukishiino@chromium.org> > > Reviewed-by: Hitoshi Yoshida <peria@chromium.org> > > Commit-Queue: Timothy Gu <timothygu@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#593108} > > TBR=japhet@chromium.org > > Bug: 866610, 888025 > Change-Id: Iee5c1d6917ad7770383e06a425f96000835a663a > Reviewed-on: https://chromium-review.googlesource.com/c/1239624 > Reviewed-by: Nate Chapin <japhet@chromium.org> > Reviewed-by: Hitoshi Yoshida <peria@chromium.org> > Reviewed-by: Kentaro Hara <haraken@chromium.org> > Reviewed-by: Yuki Shiino <yukishiino@chromium.org> > Commit-Queue: Timothy Gu <timothygu@chromium.org> > Cr-Commit-Position: refs/heads/master@{#601830} TBR=peria@chromium.org,yukishiino@chromium.org,haraken@chromium.org,japhet@chromium.org,timothygu@chromium.org Change-Id: Ie4f45dfcc1adcc2ac3469eab99dba813723288f4 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 866610, 888025 Reviewed-on: https://chromium-review.googlesource.com/c/1296057 Commit-Queue: Timothy Gu <timothygu@chromium.org> Reviewed-by: Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#601864} -- wpt-commits: 675cff1248d55626a6c3b922ab3d2d98d4a48a39 wpt-pr: 13674
d8f6cb92b3a9: Bug 1493421 [wpt PR 13166] - Reland "bindings: Implement timers with V8Function", a=testonly
Timothy Gu <timothygu@chromium.org> - Thu, 01 Nov 2018 11:21:36 +0000 - rev 445003
Push 35006 by aiakab@mozilla.com at Wed, 07 Nov 2018 21:51:52 +0000
Bug 1493421 [wpt PR 13166] - Reland "bindings: Implement timers with V8Function", a=testonly Automatic update from web-platform-testsReland "bindings: Implement timers with V8Function" This is a reland of 254369a5f6df06c2c6be067d14c2cb2a036ba173. It addresses bug 888025 by adding ASAN test expectations, as the relevant V8 feature does not yet support running on ASAN builds. Original change's description: > bindings: Implement timers with V8Function > > This fixes bug 866610 by using the IDL infrastructure to properly enter > the v8::Context before calling the registered callback. > > Also ensure eager finalization of ScheduledAction in DOMTimer to > prevent a memory leak. Added two more effective DCHECKs to confirm. > > Bug: 866610 > Change-Id: I37d7bd05f035fe31856cfe68bae51aa0632cd3b1 > Reviewed-on: https://chromium-review.googlesource.com/1220486 > Reviewed-by: Nate Chapin <japhet@chromium.org> > Reviewed-by: Yuki Shiino <yukishiino@chromium.org> > Reviewed-by: Hitoshi Yoshida <peria@chromium.org> > Commit-Queue: Timothy Gu <timothygu@chromium.org> > Cr-Commit-Position: refs/heads/master@{#593108} TBR=japhet@chromium.org Bug: 866610, 888025 Change-Id: Iee5c1d6917ad7770383e06a425f96000835a663a Reviewed-on: https://chromium-review.googlesource.com/c/1239624 Reviewed-by: Nate Chapin <japhet@chromium.org> Reviewed-by: Hitoshi Yoshida <peria@chromium.org> Reviewed-by: Kentaro Hara <haraken@chromium.org> Reviewed-by: Yuki Shiino <yukishiino@chromium.org> Commit-Queue: Timothy Gu <timothygu@chromium.org> Cr-Commit-Position: refs/heads/master@{#601830} -- wpt-commits: 60d9a09fcf6ea0244db9433198ef8cbce23a1ef4 wpt-pr: 13166
edc4ae8f78e2: Bug 1486741 - Enable ESLint rule comma-dangle for all of mozilla-central (automatic fixes). r=mossop
Mark Banner <standard8@mozilla.com> - Fri, 19 Oct 2018 12:55:39 +0000 - rev 442146
Push 34890 by dvarga@mozilla.com at Sat, 20 Oct 2018 09:40:11 +0000
Bug 1486741 - Enable ESLint rule comma-dangle for all of mozilla-central (automatic fixes). r=mossop Differential Revision: https://phabricator.services.mozilla.com/D8389
b89a744deccb: Merge autoland to mozilla-central. a=merge
Tiberius Oros <toros@mozilla.com> - Thu, 11 Oct 2018 06:52:43 +0300 - rev 440641
Push 34827 by toros@mozilla.com at Thu, 11 Oct 2018 03:53:09 +0000
Merge autoland to mozilla-central. a=merge
724343258461: bug 1481612 - vendor an unpacked win64 wheel of psutil 5.4.3. r=gps
Ted Mielczarek <ted@mielczarek.org> - Wed, 10 Oct 2018 19:54:25 +0000 - rev 440608
Push 34827 by toros@mozilla.com at Thu, 11 Oct 2018 03:53:09 +0000
bug 1481612 - vendor an unpacked win64 wheel of psutil 5.4.3. r=gps This change uses the previously added `--with-windows-wheel` option to vendor a win64 wheel of psutil. This patch was produced by running: `mach vendor python --with-windows-wheel psutil==5.4.3`. We vendor this wheel unpacked so that we can insert it into sys.path in mach without needing a virtualenv in which to install a wheel with pip, since we have a chicken-and-egg problem there where configure creates the virtualenv but we'd like to be able to use psutil before we run configure. Differential Revision: https://phabricator.services.mozilla.com/D3436
aafdbf2213ec: bug 1481612 - Re-vendor psutil 5.4.3 using `mach vendor python`. r=chmanchester,gps
Ted Mielczarek <ted@mielczarek.org> - Wed, 10 Oct 2018 19:47:58 +0000 - rev 440606
Push 34827 by toros@mozilla.com at Thu, 11 Oct 2018 03:53:09 +0000
bug 1481612 - Re-vendor psutil 5.4.3 using `mach vendor python`. r=chmanchester,gps psutil was previously vendored manually, so re-vendor it using our new tooling to make for smaller diffs in follow-up patches. This mostly just winds up adding some extra files that must have been left out of the manual vendoring, but it also updates the third_party/python/requirements.{in,txt}. Differential Revision: https://phabricator.services.mozilla.com/D3434
3c2fc3b5c03a: Merge m-c to inbound. a=merge
Ryan VanderMeulen <ryanvm@gmail.com> - Wed, 10 Oct 2018 12:31:21 -0400 - rev 440565
Push 34825 by toros@mozilla.com at Wed, 10 Oct 2018 21:58:12 +0000
Merge m-c to inbound. a=merge
641b4a378923: Backed out 5 changesets (bug 1481612, bug 1483651) for merge conflicts with bug 1490253.
Ryan VanderMeulen <ryanvm@gmail.com> - Wed, 10 Oct 2018 12:29:18 -0400 - rev 440516
Push 34821 by ryanvm@gmail.com at Wed, 10 Oct 2018 16:31:04 +0000
Backed out 5 changesets (bug 1481612, bug 1483651) for merge conflicts with bug 1490253. Backed out changeset de7e35a459e3 (bug 1481612) Backed out changeset eb440bc9fed1 (bug 1481612) Backed out changeset 7f8cad00dc2e (bug 1483651) Backed out changeset 1ecd5ddcdd79 (bug 1481612) Backed out changeset c8f12706c421 (bug 1481612)
eb440bc9fed1: bug 1481612 - vendor an unpacked win64 wheel of psutil 5.4.3. r=gps
Ted Mielczarek <ted@mielczarek.org> - Wed, 15 Aug 2018 10:54:26 -0400 - rev 440508
Push 34821 by ryanvm@gmail.com at Wed, 10 Oct 2018 16:31:04 +0000
bug 1481612 - vendor an unpacked win64 wheel of psutil 5.4.3. r=gps This change uses the previously added `--with-windows-wheel` option to vendor a win64 wheel of psutil. This patch was produced by running: `mach vendor python --with-windows-wheel psutil==5.4.3`. We vendor this wheel unpacked so that we can insert it into sys.path in mach without needing a virtualenv in which to install a wheel with pip, since we have a chicken-and-egg problem there where configure creates the virtualenv but we'd like to be able to use psutil before we run configure. Differential Revision: https://phabricator.services.mozilla.com/D3436
c8f12706c421: bug 1481612 - Re-vendor psutil 5.4.3 using `mach vendor python`. r=gps
Ted Mielczarek <ted@mielczarek.org> - Wed, 15 Aug 2018 10:39:35 -0400 - rev 440505
Push 34821 by ryanvm@gmail.com at Wed, 10 Oct 2018 16:31:04 +0000
bug 1481612 - Re-vendor psutil 5.4.3 using `mach vendor python`. r=gps psutil was previously vendored manually, so re-vendor it using our new tooling to make for smaller diffs in follow-up patches. This mostly just winds up adding some extra files that must have been left out of the manual vendoring, but it also updates the root Pipfile + Pipfile.lock. Differential Revision: https://phabricator.services.mozilla.com/D3434
ee1f0957ef4d: Bug 1473513 - resolve memory leak
yulia <ystartsev@mozilla.com> - Wed, 26 Sep 2018 10:08:43 +0200 - rev 438505
Push 34722 by rgurzau@mozilla.com at Thu, 27 Sep 2018 16:43:14 +0000
Bug 1473513 - resolve memory leak Summary: Depends on D6476 Reviewers: ochameau Reviewed By: ochameau Bug #: 1473513 Differential Revision: https://phabricator.services.mozilla.com/D6477
6b19db2da4eb: Bug 1493375 [wpt PR 13156] - Revert "bindings: Implement timers with V8Function", a=testonly
Frank Liberato <liberato@chromium.org> - Wed, 26 Sep 2018 10:46:51 +0000 - rev 438472
Push 34722 by rgurzau@mozilla.com at Thu, 27 Sep 2018 16:43:14 +0000
Bug 1493375 [wpt PR 13156] - Revert "bindings: Implement timers with V8Function", a=testonly Automatic update from web-platform-testsRevert "bindings: Implement timers with V8Function" This reverts commit 254369a5f6df06c2c6be067d14c2cb2a036ba173. Reason for revert: <INSERT REASONING HERE> Original change's description: > bindings: Implement timers with V8Function > > This fixes bug 866610 by using the IDL infrastructure to properly enter > the v8::Context before calling the registered callback. > > Also ensure eager finalization of ScheduledAction in DOMTimer to > prevent a memory leak. Added two more effective DCHECKs to confirm. > > Bug: 866610 > Change-Id: I37d7bd05f035fe31856cfe68bae51aa0632cd3b1 > Reviewed-on: https://chromium-review.googlesource.com/1220486 > Reviewed-by: Nate Chapin <japhet@chromium.org> > Reviewed-by: Yuki Shiino <yukishiino@chromium.org> > Reviewed-by: Hitoshi Yoshida <peria@chromium.org> > Commit-Queue: Timothy Gu <timothygu@chromium.org> > Cr-Commit-Position: refs/heads/master@{#593108} TBR=peria@chromium.org,yukishiino@chromium.org,haraken@chromium.org,japhet@chromium.org,timothygu@chromium.org Change-Id: Ifaccc3374466b851fc28b10c63ed1397bdae635e No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 866610 Reviewed-on: https://chromium-review.googlesource.com/1239216 Reviewed-by: Frank Liberato <liberato@chromium.org> Commit-Queue: Frank Liberato <liberato@chromium.org> Cr-Commit-Position: refs/heads/master@{#593260} -- wpt-commits: 45f38e4c17379c83be5533ff60697ac888d8eea7 wpt-pr: 13156
b9e9fdc21dd7: Bug 1491459 [wpt PR 13012] - bindings: Implement timers with V8Function, a=testonly
Timothy Gu <timothygu@chromium.org> - Wed, 26 Sep 2018 10:46:23 +0000 - rev 438461
Push 34722 by rgurzau@mozilla.com at Thu, 27 Sep 2018 16:43:14 +0000
Bug 1491459 [wpt PR 13012] - bindings: Implement timers with V8Function, a=testonly Automatic update from web-platform-testsbindings: Implement timers with V8Function This fixes bug 866610 by using the IDL infrastructure to properly enter the v8::Context before calling the registered callback. Also ensure eager finalization of ScheduledAction in DOMTimer to prevent a memory leak. Added two more effective DCHECKs to confirm. Bug: 866610 Change-Id: I37d7bd05f035fe31856cfe68bae51aa0632cd3b1 Reviewed-on: https://chromium-review.googlesource.com/1220486 Reviewed-by: Nate Chapin <japhet@chromium.org> Reviewed-by: Yuki Shiino <yukishiino@chromium.org> Reviewed-by: Hitoshi Yoshida <peria@chromium.org> Commit-Queue: Timothy Gu <timothygu@chromium.org> Cr-Commit-Position: refs/heads/master@{#593108} -- wpt-commits: 4eaebdf70cbbbac6b95d757c424a879c1f980dac wpt-pr: 13012
cf6b1314df05: Bug 1479035: Part 1 - Don't create event queues for stub nsThread wrappers. r=froydnj
Kris Maglione <maglione.k@gmail.com> - Fri, 27 Jul 2018 15:13:12 -0700 - rev 438394
Push 34719 by shindli@mozilla.com at Thu, 27 Sep 2018 03:14:06 +0000
Bug 1479035: Part 1 - Don't create event queues for stub nsThread wrappers. r=froydnj Most of the times when we automatically create nsThread wrappers for threads that don't already have them, we don't actually need the event targets, since those threads don't run XPCOM event loops. Aside from wasting memory, actually creating these event loops can lead to leaks if a thread tries to dispatch a runnable to the queue which creates a reference cycle with the thread. Not creating the event queues for threads that don't actually need them helps avoid those foot guns, and also makes it easier to figure out which treads actually run XPCOM event loops. MozReview-Commit-ID: Arck4VQqdne
5152af6ab3e3: Bug 1479035: Part 1 - Don't create event queues for stub nsThread wrappers. r=froydnj
Kris Maglione <maglione.k@gmail.com> - Fri, 27 Jul 2018 15:13:12 -0700 - rev 438381
Push 34719 by shindli@mozilla.com at Thu, 27 Sep 2018 03:14:06 +0000
Bug 1479035: Part 1 - Don't create event queues for stub nsThread wrappers. r=froydnj Most of the times when we automatically create nsThread wrappers for threads that don't already have them, we don't actually need the event targets, since those threads don't run XPCOM event loops. Aside from wasting memory, actually creating these event loops can lead to leaks if a thread tries to dispatch a runnable to the queue which creates a reference cycle with the thread. Not creating the event queues for threads that don't actually need them helps avoid those foot guns, and also makes it easier to figure out which treads actually run XPCOM event loops. MozReview-Commit-ID: Arck4VQqdne
a03a61d6d724: Bug 1479035: Part 1 - Don't create event queues for stub nsThread wrappers. r=froydnj
Kris Maglione <maglione.k@gmail.com> - Fri, 27 Jul 2018 15:13:12 -0700 - rev 438329
Push 34717 by shindli@mozilla.com at Wed, 26 Sep 2018 21:52:33 +0000
Bug 1479035: Part 1 - Don't create event queues for stub nsThread wrappers. r=froydnj Most of the times when we automatically create nsThread wrappers for threads that don't already have them, we don't actually need the event targets, since those threads don't run XPCOM event loops. Aside from wasting memory, actually creating these event loops can lead to leaks if a thread tries to dispatch a runnable to the queue which creates a reference cycle with the thread. Not creating the event queues for threads that don't actually need them helps avoid those foot guns, and also makes it easier to figure out which treads actually run XPCOM event loops. MozReview-Commit-ID: Arck4VQqdne
87d4667da724: Bug 1492930 - Part 4. Add ImageMemoryReporter to support extra shared surfaces reporting. r=tnikkel
Andrew Osmond <aosmond@mozilla.com> - Tue, 25 Sep 2018 09:13:51 -0400 - rev 438170
Push 34711 by aciure@mozilla.com at Tue, 25 Sep 2018 21:49:34 +0000
Bug 1492930 - Part 4. Add ImageMemoryReporter to support extra shared surfaces reporting. r=tnikkel By delegating responsibility for shared surfaces reporting to imagelib, we can cross reference the GPU shared surfaces cache with the local surface cache in a content process (or the main process). This will allow us to identify entries that are in the GPU cache but not in the content/main process cache, and aid in debugging memory leaks. This functionality is pref'd off by default behind image.mem.debug-reporting. Additionally, we want to report every entry that was mapped into the compositor process, in the compositor process memory report. This will give us a sense of how much of our resident memory is consumed by mapped images in absence of the more detailed cross referencing above.
2959314ecf7c: Bug 1492930 - Part 4. Add ImageMemoryReporter to support extra shared surfaces reporting. r=tnikkel
Andrew Osmond <aosmond@mozilla.com> - Tue, 25 Sep 2018 06:18:06 -0400 - rev 438154
Push 34711 by aciure@mozilla.com at Tue, 25 Sep 2018 21:49:34 +0000
Bug 1492930 - Part 4. Add ImageMemoryReporter to support extra shared surfaces reporting. r=tnikkel By delegating responsibility for shared surfaces reporting to imagelib, we can cross reference the GPU shared surfaces cache with the local surface cache in a content process (or the main process). This will allow us to identify entries that are in the GPU cache but not in the content/main process cache, and aid in debugging memory leaks. This functionality is pref'd off by default behind image.mem.debug-reporting. Additionally, we want to report every entry that was mapped into the compositor process, in the compositor process memory report. This will give us a sense of how much of our resident memory is consumed by mapped images in absence of the more detailed cross referencing above.
80c51a6e896e: Bug 1473513 - resolve memory leak r=ochameau
yulia <ystartsev@mozilla.com> - Tue, 25 Sep 2018 08:06:25 +0000 - rev 438090
Push 34710 by aciure@mozilla.com at Tue, 25 Sep 2018 21:48:21 +0000
Bug 1473513 - resolve memory leak r=ochameau Depends on D6476 Differential Revision: https://phabricator.services.mozilla.com/D6477