a61f5223b86db8f376af923f15e3a143d2239cca: Bug 1647342 - Part 2: Rely on onResumeFrame to handle marking all frames as on-stack. r=arai! draft
Logan Smyth <loganfsmyth@gmail.com> - Tue, 23 Jun 2020 23:56:22 +0000 - rev 2999990
Push 558599 by reviewbot at Tue, 23 Jun 2020 23:56:49 +0000
Bug 1647342 - Part 2: Rely on onResumeFrame to handle marking all frames as on-stack. r=arai! Summary: It is guaranteed that this will already be populated because in 1539654 we started properly preserving the debuggee-ness of frames across suspend and resume. With slowPathOnResumeFrame guaranteed to run, we no longer need to try to hande handle the case where the generator has been resumed, but the Debugger.Frame's inner data was not populated. Differential Revision: https://phabricator.services.mozilla.com/D80735 Depends on D80734 Test Plan: Reviewers: Subscribers: Bug #: 1647342 Differential Diff: PHID-DIFF-ppztbt6hxxpwtvc3wsnw
f980d1520f92c474ebd9579830d9d41b7362ce78: Bug 1647342 - Part 1: Remove FrameIter::Data from DebuggerFrame public API. r=arai! draft
Logan Smyth <loganfsmyth@gmail.com> - Tue, 23 Jun 2020 23:56:18 +0000 - rev 2999989
Push 558599 by reviewbot at Tue, 23 Jun 2020 23:56:49 +0000
Bug 1647342 - Part 1: Remove FrameIter::Data from DebuggerFrame public API. r=arai! Summary: Exposing frameIterData() and setFrameIterData() isn't great since it makes it harder to follow what state transitions for frame data we expect the frame to have. By hiding this, it helps clarify that frame data can be cleared or replaced, but public usage of the FrameIter::Data object itself isn't expected outside of the class itself. Differential Revision: https://phabricator.services.mozilla.com/D80734 Depends on D80762 Test Plan: Reviewers: Subscribers: Bug #: 1647342 Differential Diff: PHID-DIFF-yyvo3sxpaodbm57o36o2
49a5dc8bb0fd6e7177c45f3926f2f2edbcc429fb: Bug 1577639 - Do not attempt to clean up frames for non-OOM conditions. r=arai! draft
Logan Smyth <loganfsmyth@gmail.com> - Tue, 23 Jun 2020 23:56:14 +0000 - rev 2999988
Push 558599 by reviewbot at Tue, 23 Jun 2020 23:56:49 +0000
Bug 1577639 - Do not attempt to clean up frames for non-OOM conditions. r=arai! Summary: The core issue is that we run removeFromFrameMapsAndClearBreakpointsIn(cx, from) even for non-OOM paths in this function, which is undesirable because that will remove the breakpoints for evaled scripts. In the non-OOM case there are no Debugger.Frame objects left in the frames map for the "frame" list, so there is no reason to actually call it in that case. This patch merges the two OOM handlers together for simplicity, though it is not technically necessary, it seems like the very minor increase in code run if there is an OOM is worth it to keep things centralized. Differential Revision: https://phabricator.services.mozilla.com/D80762 Test Plan: Reviewers: Subscribers: Bug #: 1577639 Differential Diff: PHID-DIFF-bpfhtg7cbdeoujgbzi7c
f961c3a4040efd10733f1e692e86b1bf8d9b8db2: try_task_config for https://phabricator.services.mozilla.com/D80735 draft
libmozevent <release-mgmt-analysis@mozilla.com> - Tue, 23 Jun 2020 23:56:00 +0000 - rev 2999987
Push 558598 by reviewbot at Tue, 23 Jun 2020 23:56:15 +0000
try_task_config for https://phabricator.services.mozilla.com/D80735 Differential Diff: PHID-DIFF-ppztbt6hxxpwtvc3wsnw
f25018e15508ba5c324b7c92c6dd061724b91c5a: Bug 1647342 - Part 2: Rely on onResumeFrame to handle marking all frames as on-stack. r=arai! draft
Logan Smyth <loganfsmyth@gmail.com> - Tue, 23 Jun 2020 23:55:56 +0000 - rev 2999986
Push 558598 by reviewbot at Tue, 23 Jun 2020 23:56:15 +0000
Bug 1647342 - Part 2: Rely on onResumeFrame to handle marking all frames as on-stack. r=arai! Summary: It is guaranteed that this will already be populated because in 1539654 we started properly preserving the debuggee-ness of frames across suspend and resume. With slowPathOnResumeFrame guaranteed to run, we no longer need to try to hande handle the case where the generator has been resumed, but the Debugger.Frame's inner data was not populated. Differential Revision: https://phabricator.services.mozilla.com/D80735 Depends on D80734 Test Plan: Reviewers: Subscribers: Bug #: 1647342 Differential Diff: PHID-DIFF-ppztbt6hxxpwtvc3wsnw
489dd46f42f9e37751ee84120ba854247ee3bbf4: Bug 1647342 - Part 1: Remove FrameIter::Data from DebuggerFrame public API. r=arai! draft
Logan Smyth <loganfsmyth@gmail.com> - Tue, 23 Jun 2020 23:55:53 +0000 - rev 2999985
Push 558598 by reviewbot at Tue, 23 Jun 2020 23:56:15 +0000
Bug 1647342 - Part 1: Remove FrameIter::Data from DebuggerFrame public API. r=arai! Summary: Exposing frameIterData() and setFrameIterData() isn't great since it makes it harder to follow what state transitions for frame data we expect the frame to have. By hiding this, it helps clarify that frame data can be cleared or replaced, but public usage of the FrameIter::Data object itself isn't expected outside of the class itself. Differential Revision: https://phabricator.services.mozilla.com/D80734 Depends on D80762 Test Plan: Reviewers: Subscribers: Bug #: 1647342 Differential Diff: PHID-DIFF-yyvo3sxpaodbm57o36o2
6c26df452d4038f1d08b5924455b91860efe330d: Bug 1577639 - Do not attempt to clean up frames for non-OOM conditions. r=arai! draft
Logan Smyth <loganfsmyth@gmail.com> - Tue, 23 Jun 2020 23:55:50 +0000 - rev 2999984
Push 558598 by reviewbot at Tue, 23 Jun 2020 23:56:15 +0000
Bug 1577639 - Do not attempt to clean up frames for non-OOM conditions. r=arai! Summary: The core issue is that we run removeFromFrameMapsAndClearBreakpointsIn(cx, from) even for non-OOM paths in this function, which is undesirable because that will remove the breakpoints for evaled scripts. In the non-OOM case there are no Debugger.Frame objects left in the frames map for the "frame" list, so there is no reason to actually call it in that case. This patch merges the two OOM handlers together for simplicity, though it is not technically necessary, it seems like the very minor increase in code run if there is an OOM is worth it to keep things centralized. Differential Revision: https://phabricator.services.mozilla.com/D80762 Test Plan: Reviewers: Subscribers: Bug #: 1577639 Differential Diff: PHID-DIFF-bpfhtg7cbdeoujgbzi7c
74ded802b485e9932033108134a490705a89cb5f: try_task_config for https://phabricator.services.mozilla.com/D80762 draft
libmozevent <release-mgmt-analysis@mozilla.com> - Tue, 23 Jun 2020 23:54:40 +0000 - rev 2999983
Push 558597 by reviewbot at Tue, 23 Jun 2020 23:55:06 +0000
try_task_config for https://phabricator.services.mozilla.com/D80762 Differential Diff: PHID-DIFF-bpfhtg7cbdeoujgbzi7c
f0246a6a8b34f82bed70d9115df0966d83f75300: Bug 1577639 - Do not attempt to clean up frames for non-OOM conditions. r=arai! draft
Logan Smyth <loganfsmyth@gmail.com> - Tue, 23 Jun 2020 23:54:33 +0000 - rev 2999982
Push 558597 by reviewbot at Tue, 23 Jun 2020 23:55:06 +0000
Bug 1577639 - Do not attempt to clean up frames for non-OOM conditions. r=arai! Summary: The core issue is that we run removeFromFrameMapsAndClearBreakpointsIn(cx, from) even for non-OOM paths in this function, which is undesirable because that will remove the breakpoints for evaled scripts. In the non-OOM case there are no Debugger.Frame objects left in the frames map for the "frame" list, so there is no reason to actually call it in that case. This patch merges the two OOM handlers together for simplicity, though it is not technically necessary, it seems like the very minor increase in code run if there is an OOM is worth it to keep things centralized. Differential Revision: https://phabricator.services.mozilla.com/D80762 Test Plan: Reviewers: Subscribers: Bug #: 1577639 Differential Diff: PHID-DIFF-bpfhtg7cbdeoujgbzi7c
0b8b698fc00001ff9ce003718917037c7fddb05f: try_task_config for https://phabricator.services.mozilla.com/D80734 draft
libmozevent <release-mgmt-analysis@mozilla.com> - Tue, 23 Jun 2020 23:54:37 +0000 - rev 2999981
Push 558596 by reviewbot at Tue, 23 Jun 2020 23:54:54 +0000
try_task_config for https://phabricator.services.mozilla.com/D80734 Differential Diff: PHID-DIFF-yyvo3sxpaodbm57o36o2
d9edb90a38f6c0ed36de523762ed94a762b77ac5: Bug 1647342 - Part 1: Remove FrameIter::Data from DebuggerFrame public API. r=arai! draft
Logan Smyth <loganfsmyth@gmail.com> - Tue, 23 Jun 2020 23:54:33 +0000 - rev 2999980
Push 558596 by reviewbot at Tue, 23 Jun 2020 23:54:54 +0000
Bug 1647342 - Part 1: Remove FrameIter::Data from DebuggerFrame public API. r=arai! Summary: Exposing frameIterData() and setFrameIterData() isn't great since it makes it harder to follow what state transitions for frame data we expect the frame to have. By hiding this, it helps clarify that frame data can be cleared or replaced, but public usage of the FrameIter::Data object itself isn't expected outside of the class itself. Differential Revision: https://phabricator.services.mozilla.com/D80734 Depends on D80762 Test Plan: Reviewers: Subscribers: Bug #: 1647342 Differential Diff: PHID-DIFF-yyvo3sxpaodbm57o36o2
fbd4816af35b9e62fbdb0278d5a61f2f8596eea8: Bug 1577639 - Do not attempt to clean up frames for non-OOM conditions. r=arai! draft
Logan Smyth <loganfsmyth@gmail.com> - Tue, 23 Jun 2020 23:54:30 +0000 - rev 2999979
Push 558596 by reviewbot at Tue, 23 Jun 2020 23:54:54 +0000
Bug 1577639 - Do not attempt to clean up frames for non-OOM conditions. r=arai! Summary: The core issue is that we run removeFromFrameMapsAndClearBreakpointsIn(cx, from) even for non-OOM paths in this function, which is undesirable because that will remove the breakpoints for evaled scripts. In the non-OOM case there are no Debugger.Frame objects left in the frames map for the "frame" list, so there is no reason to actually call it in that case. This patch merges the two OOM handlers together for simplicity, though it is not technically necessary, it seems like the very minor increase in code run if there is an OOM is worth it to keep things centralized. Differential Revision: https://phabricator.services.mozilla.com/D80762 Test Plan: Reviewers: Subscribers: Bug #: 1577639 Differential Diff: PHID-DIFF-bpfhtg7cbdeoujgbzi7c
544f90db2a82bfab09ed992657226603ec2d5ec2: try_task_config for https://phabricator.services.mozilla.com/D80771 draft
libmozevent <release-mgmt-analysis@mozilla.com> - Tue, 23 Jun 2020 23:48:57 +0000 - rev 2999978
Push 558595 by reviewbot at Tue, 23 Jun 2020 23:49:22 +0000
try_task_config for https://phabricator.services.mozilla.com/D80771 Differential Diff: PHID-DIFF-7fpykvdvkkhfdjicf6qi
11195b8c7e64435e8ddd114ac873fe97f01c3093: Bug 1600178 - multiGPU improvements draft
Bert Peers <bpeers@mozilla.com> - Tue, 23 Jun 2020 23:48:53 +0000 - rev 2999977
Push 558595 by reviewbot at Tue, 23 Jun 2020 23:49:22 +0000
Bug 1600178 - multiGPU improvements Summary: Push the GL context, surface pool, and other gpu-specific data to the compositors. Previously they would ask for a SharedGL. This should make it easier to pass different GL contexts to different windows. There is room for multiple contexts keyed by a "Gpu key" but this is not used yet. Two exceptions to this one-way flow: 1/ device reset on Angle: remembers the Gpu Key it was created with and uses it to lazy-recreate the PerGpuData for it after a device reset. 2/ when there is no valid GL created for the GPU (Wayland), RenderCompositorOGL will lazy-create one using CreateForCompositorWidget. This breaks the notion that the RenderThread owns and is aware of all contexts so it can respond when a GPU goes away. If null-GL doesn't happen on multi-GPU platforms this doesn't have to be a showstopper (yet). Test Plan: Reviewers: Subscribers: Bug #: 1600178 Differential Diff: PHID-DIFF-7fpykvdvkkhfdjicf6qi
ec14d1be11a2112db49053173cd9b7effe2ce09e: Fuzzy query=source-test-python-mozbuild draft
Geoff Brown <gbrown@mozilla.com> - Tue, 23 Jun 2020 17:46:33 -0600 - rev 2999976
Push 558594 by gbrown@mozilla.com at Tue, 23 Jun 2020 23:47:06 +0000
Fuzzy query=source-test-python-mozbuild Pushed via `mach try fuzzy`
216369bc9d3eccc541c8e59c87a54bc715a7199e: [mq]: debug draft
Geoff Brown <gbrown@mozilla.com> - Tue, 23 Jun 2020 17:44:59 -0600 - rev 2999975
Push 558594 by gbrown@mozilla.com at Tue, 23 Jun 2020 23:47:06 +0000
[mq]: debug
7a5a85259a00fb79ad235151b43de752221c4ab9: try_task_config for https://phabricator.services.mozilla.com/D80770 draft
libmozevent <release-mgmt-analysis@mozilla.com> - Tue, 23 Jun 2020 23:41:44 +0000 - rev 2999974
Push 558593 by reviewbot at Tue, 23 Jun 2020 23:42:04 +0000
try_task_config for https://phabricator.services.mozilla.com/D80770 Differential Diff: PHID-DIFF-riiul4ffw2ep6rymqxx2
eb112ea4bd6f0095e79d83d8c6fe94a42d6512bd: Bug 1647603: Update MDN compat data. draft
Daisuke Akatsuka <daisuke@birchill.co.jp> - Tue, 23 Jun 2020 23:41:39 +0000 - rev 2999973
Push 558593 by reviewbot at Tue, 23 Jun 2020 23:42:04 +0000
Bug 1647603: Update MDN compat data. Summary: Test Plan: Reviewers: Subscribers: Bug #: 1647603 Differential Diff: PHID-DIFF-riiul4ffw2ep6rymqxx2
6a1d797be38ec3dd82342455c2d81d6eef32898c: try_task_config for https://phabricator.services.mozilla.com/D80769 draft
libmozevent <release-mgmt-analysis@mozilla.com> - Tue, 23 Jun 2020 23:41:34 +0000 - rev 2999972
Push 558592 by reviewbot at Tue, 23 Jun 2020 23:41:52 +0000
try_task_config for https://phabricator.services.mozilla.com/D80769 Differential Diff: PHID-DIFF-pbkacmrsdqcyav3ukksm
47e906a2403e8c3abccb46c353fe1ed1269b6cae: Bug 1579261 - Remove getUserMedia, getDisplayMedia & mozGetUserMedia cross-origin probes. draft
Jan-Ivar Bruaroey <jib@mozilla.com> - Tue, 23 Jun 2020 23:41:29 +0000 - rev 2999971
Push 558592 by reviewbot at Tue, 23 Jun 2020 23:41:52 +0000
Bug 1579261 - Remove getUserMedia, getDisplayMedia & mozGetUserMedia cross-origin probes. Summary: Test Plan: Reviewers: Subscribers: Bug #: 1579261 Differential Diff: PHID-DIFF-pbkacmrsdqcyav3ukksm
(0) -1000000 -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 +300000 +1000000 tip