searching for reviewer(jya)
c20861a8b748c86797abc9a9518a759d5ab9f3fa: Bug 1657788 - Refactor SendShare() to use promise instead of callback r=jya
Marcos Cáceres <mcaceres@mozilla.com> - Fri, 07 Aug 2020 02:38:41 +0000 - rev 543727
Push 123638 by mcaceres@mozilla.com at Fri, 07 Aug 2020 05:11:30 +0000
Bug 1657788 - Refactor SendShare() to use promise instead of callback r=jya Differential Revision: https://phabricator.services.mozilla.com/D85986
df7c9cae79bee9a78c5ef532d9d3986e5abf473e: Bug 1657311 - Hard-code MIME-extension mappings for FLAC and AAC. r=jya,Gijs
Tom Schuster <evilpies@gmail.com> - Thu, 06 Aug 2020 11:41:18 +0000 - rev 543579
Push 123548 by evilpies@gmail.com at Thu, 06 Aug 2020 11:53:35 +0000
Bug 1657311 - Hard-code MIME-extension mappings for FLAC and AAC. r=jya,Gijs Drive-by: Remove the obviously unused macro MAC_TYPE. Differential Revision: https://phabricator.services.mozilla.com/D85989
1ff4754fc8749a8fbbcc6fd87c959e20259bb65f: Bug 1656436 [Linux/VAAPI] Release VAAPI surface data before we re-use them, r=jya
Martin Stransky <stransky@redhat.com> - Thu, 06 Aug 2020 11:12:45 +0000 - rev 543578
Push 123547 by csabou@mozilla.com at Thu, 06 Aug 2020 11:52:14 +0000
Bug 1656436 [Linux/VAAPI] Release VAAPI surface data before we re-use them, r=jya VAAPI HW surfaces are released at ReleaseUnusedVAAPIFrames() and we use DMABufSurface::IsUsed() flag to detect unused surfaces. Then we call GetUnusedDMABufSurfaceWrapper() to get unused surfaces to re-use them for decoding. Because DMABufSurface::IsUsed() flag is updated asynchronously it may change between ReleaseUnusedVAAPIFrames() and GetUnusedDMABufSurfaceWrapper() calls. In that case GetUnusedDMABufSurfaceWrapper() may return unused but also unreleased surface as it was marked as used in time of ReleaseUnusedVAAPIFrames() call. In this patch explicitly release VAAPI data of any surface before we re-use it. Also fail when we try to upload data to already used DMABufSurfaceYUV surface. Differential Revision: https://phabricator.services.mozilla.com/D85842
bacacb384008a44fb04c63c456311c7530dfa67e: Bug 1645671 [Linux/VA-API] Create DMABufSurfaceWrapper directly at nsTAttay and disable DMABufSurfaceWrapper class copy and assignment constructors, r=jya
Martin Stransky <stransky@redhat.com> - Mon, 03 Aug 2020 09:08:26 +0000 - rev 543088
Push 123214 by abutkovits@mozilla.com at Mon, 03 Aug 2020 09:45:11 +0000
Bug 1645671 [Linux/VA-API] Create DMABufSurfaceWrapper directly at nsTAttay and disable DMABufSurfaceWrapper class copy and assignment constructors, r=jya When DMABufSurfaceWrapper is added to nsTArray, a temporary local DMABufSurfaceWrapper object is created. When the temporary object is deleted after the adding, associated dmabuf data is released which leads to rendering artifact during VA-API video playback. As a fix in this patch we create DMABufSurfaceWrapper 'in-place' at nsTAttay. We also disable DMABufSurfaceWrapper class copy and assignment constructors to avoid similar potential issues. Differential Revision: https://phabricator.services.mozilla.com/D85152
0bed87941dc5ad1e12884f0c51d6be82a557afa0: Bug 1550248 - Sniff .m3u8 files as application/vnd.apple.mpegurl. r=jya
Paul Adenot <paul@paul.cx> - Fri, 31 Jul 2020 01:04:08 +0000 - rev 542872
Push 123086 by padenot@mozilla.com at Fri, 31 Jul 2020 13:57:45 +0000
Bug 1550248 - Sniff .m3u8 files as application/vnd.apple.mpegurl. r=jya Depends on D85144 Differential Revision: https://phabricator.services.mozilla.com/D85286
164f54ec7aff3f2d74e468f83d9738529702e48f: Bug 1656137 - Spin-wait on completion event rather than blocking main thread. r=jya
Matthew Gregan <kinetik@flim.org> - Fri, 31 Jul 2020 01:45:44 +0000 - rev 542726
Push 123057 by mgregan@mozilla.com at Fri, 31 Jul 2020 01:48:56 +0000
Bug 1656137 - Spin-wait on completion event rather than blocking main thread. r=jya Differential Revision: https://phabricator.services.mozilla.com/D85357
e66ce7967edc2c22588ef0ae9d4b71214af3ea16: Bug 1463915 - Update libvorbis to 1.3.7. r=jya
Thomas Daede <tdaede@mozilla.com> - Fri, 24 Jul 2020 00:25:08 +0000 - rev 542122
Push 122650 by tdaede@mozilla.com at Fri, 24 Jul 2020 21:02:42 +0000
Bug 1463915 - Update libvorbis to 1.3.7. r=jya Differential Revision: https://phabricator.services.mozilla.com/D84565
41de9ac734d69d754ea3f13db6933343b62ea1b8: Bug 1646899 - P4: Handle object & embed via DocumentChannel. r=mattwoodrow,jya
Dan Glastonbury <dan.glastonbury@gmail.com> - Tue, 21 Jul 2020 01:01:05 +0000 - rev 541394
Push 122215 by dglastonbury@mozilla.com at Tue, 21 Jul 2020 04:28:37 +0000
Bug 1646899 - P4: Handle object & embed via DocumentChannel. r=mattwoodrow,jya Pass internal content policy type to DLL and switch behavior depending on type being loaded. This implementation immediately redirects channel back to the content process for further handling. Depends on D80406 Differential Revision: https://phabricator.services.mozilla.com/D80407
d06b2e855360b986b907c285c2559525ac123d31: Bug 1578042 - Ignore skipped frames when the video was offscreen. r=jya,nical
Markus Stange <mstange.moz@gmail.com> - Mon, 20 Jul 2020 21:47:07 +0000 - rev 541361
Push 122193 by mstange@themasta.com at Mon, 20 Jul 2020 21:58:30 +0000
Bug 1578042 - Ignore skipped frames when the video was offscreen. r=jya,nical This patch makes it work for WebRender. The next patch in the series makes it work for non-WebRender, too. Differential Revision: https://phabricator.services.mozilla.com/D83463
8ab99078da80166e569a158be9394a7c85125d07: Bug 1578042 - Improve dropped frames reporting for videos, by counting all frames in mImages that were never composited. r=jya,nical
Markus Stange <mstange.moz@gmail.com> - Mon, 20 Jul 2020 21:56:21 +0000 - rev 541360
Push 122193 by mstange@themasta.com at Mon, 20 Jul 2020 21:58:30 +0000
Bug 1578042 - Improve dropped frames reporting for videos, by counting all frames in mImages that were never composited. r=jya,nical In the current state this also counts frame drops while the video is offscreen, but this will be fixed in a later patch in the series. This patch also adjusts the time delta check: It now compares floored milliseconds. In 60fps WebM videos, the video frame durations are 16.0, 17.0, 17.0, 16.0, 17.0, 17.0, ... so we need to consider frames with 16.0ms as displayable even when the target frame duration is 16.67ms, otherwise we gloss over one third of the frames when counting potentially dropped frames. Differential Revision: https://phabricator.services.mozilla.com/D82635
3fbf9c0203dd22b404ffbe0e9dfbdb9c772a786c: Bug 1578042 - Ignore skipped frames when the video was offscreen. r=jya,nical
Markus Stange <mstange.moz@gmail.com> - Mon, 20 Jul 2020 16:20:12 +0000 - rev 541296
Push 122157 by mstange@themasta.com at Mon, 20 Jul 2020 17:32:01 +0000
Bug 1578042 - Ignore skipped frames when the video was offscreen. r=jya,nical This patch makes it work for WebRender. The next patch in the series makes it work for non-WebRender, too. Differential Revision: https://phabricator.services.mozilla.com/D83463
57f65280709f122439ded298eeea0b8fb5707a87: Bug 1578042 - Improve dropped frames reporting for videos, by counting all frames in mImages that were never composited. r=jya,nical
Markus Stange <mstange.moz@gmail.com> - Mon, 20 Jul 2020 16:19:51 +0000 - rev 541295
Push 122157 by mstange@themasta.com at Mon, 20 Jul 2020 17:32:01 +0000
Bug 1578042 - Improve dropped frames reporting for videos, by counting all frames in mImages that were never composited. r=jya,nical In the current state this also counts frame drops while the video is offscreen, but this will be fixed in a later patch in the series. This patch also adjusts the time delta check: It now compares floored milliseconds. In 60fps WebM videos, the video frame durations are 16.0, 17.0, 17.0, 16.0, 17.0, 17.0, ... so we need to consider frames with 16.0ms as displayable even when the target frame duration is 16.67ms, otherwise we gloss over one third of the frames when counting potentially dropped frames. Differential Revision: https://phabricator.services.mozilla.com/D82635
5d7977a864c4f0f89444fb34a0c5dfc1d313aa04: Bug 1653679 - Propagate CompositionOpportunityId to ImageComposite. r=jya,nical
Markus Stange <mstange.moz@gmail.com> - Sat, 18 Jul 2020 05:15:47 +0000 - rev 541128
Push 122058 by mstange@themasta.com at Sat, 18 Jul 2020 06:40:27 +0000
Bug 1653679 - Propagate CompositionOpportunityId to ImageComposite. r=jya,nical Differential Revision: https://phabricator.services.mozilla.com/D83462
05227bc2bb3d88be45b76033af6f73754560dd4a: Bug 1653679 - Don't call UpdateCompositedFrame outside of a composition. r=jya,nical
Markus Stange <mstange.moz@gmail.com> - Sat, 18 Jul 2020 05:13:16 +0000 - rev 541126
Push 122058 by mstange@themasta.com at Sat, 18 Jul 2020 06:40:27 +0000
Bug 1653679 - Don't call UpdateCompositedFrame outside of a composition. r=jya,nical Correctly indicate that we're not in a composition during SetDisplayList or during empty transactions, by making sure the composition timestamp is null outside of a composition. We also now return 0 rather than -1 from the first call to ChooseImageIndex outside of a composition, so that static images (like canvases) default to the correct initial frame. We don't call ChooseImageIndex for them again once we composite them. This is different from non-WebRender, which would call ChooseImageIndex on canvas layers during every composition. This introduces a behavior difference for static images when WebRender is enabled: Those images will no longer update mLastFrameID, because UpdateCompositedFrame will not be called during a composition for them. I'm also removing a comment that seems like it's unnecessarily duplicating information from another comment a few lines further up. That other comment is also easier to understand. Differential Revision: https://phabricator.services.mozilla.com/D83460
d9989b0e83cbda3f9e0e4e0a822af0d9efb9b116: Bug 1653679 - Move more logic into UpdateCompositedFrame. r=jya,nical
Markus Stange <mstange.moz@gmail.com> - Sat, 18 Jul 2020 05:05:27 +0000 - rev 541125
Push 122058 by mstange@themasta.com at Sat, 18 Jul 2020 06:40:27 +0000
Bug 1653679 - Move more logic into UpdateCompositedFrame. r=jya,nical This also makes it so that UpdateBias for non-WebRender is only called when the video frame changes. This mirrors the recent change that we made for WebRender in bug 1652181. Non-WebRender only calls UpdateCompositedFrame when it actually draws the video onto the screen, so when the video is the only thing that was updating, the new behavior is equivalent. But the new behavior makes more sense if you have a 30fps video and a 60fps animation running on a 60fps screen at the same time - now the bias won't be accidentally reset every other frame. Differential Revision: https://phabricator.services.mozilla.com/D83459
bec480097ff6e6b1e3f7be9d0517741166bed931: Bug 1653679 - Update mLastFrameID in a new method UpdateCompositedFrame. r=jya,nical
Markus Stange <mstange.moz@gmail.com> - Sat, 18 Jul 2020 05:28:56 +0000 - rev 541124
Push 122058 by mstange@themasta.com at Sat, 18 Jul 2020 06:40:27 +0000
Bug 1653679 - Update mLastFrameID in a new method UpdateCompositedFrame. r=jya,nical Differential Revision: https://phabricator.services.mozilla.com/D82634
ff727e9821be10f720eb989344fc474108ae03f4: Bug 1578042 - Ignore skipped frames when the video was offscreen. r=jya,nical
Markus Stange <mstange.moz@gmail.com> - Thu, 16 Jul 2020 03:37:03 +0000 - rev 540807
Push 121925 by mstange@themasta.com at Thu, 16 Jul 2020 20:01:20 +0000
Bug 1578042 - Ignore skipped frames when the video was offscreen. r=jya,nical This currently only works for WebRender. In non-WR, no frame drops are reported. There are two reasons why it doesn't work for non-WR: - Non-WR currently does not increment the composition opportunity ID. - In non-WR, UpdateCompositedFrame is only called for videos when they are drawn. But this detection relies on it being called on every composite, if the video is part of the on-screen scene. (WR does that.) To make this detection work for non-WR as well, we would need to address both of those points. The latter point is somewhat tricky because non-WR calls ChooseImageIndex many times throughout a composite, and we would need to choose a point in the composite at which to "lock in" the image for that composite and cache the image index on the ImageHost somewhere, and then also find a way to reset that locked-in index in the next composite. I haven't come up with a way to do that and I do not know if it is worth the effort. Differential Revision: https://phabricator.services.mozilla.com/D83463
94159598ab2a3af0d514bf7a0339aac8f2a507b7: Bug 1578042 - Propagate CompositionOpportunityId to ImageComposite. r=jya,nical
Markus Stange <mstange.moz@gmail.com> - Thu, 16 Jul 2020 08:47:49 +0000 - rev 540806
Push 121925 by mstange@themasta.com at Thu, 16 Jul 2020 20:01:20 +0000
Bug 1578042 - Propagate CompositionOpportunityId to ImageComposite. r=jya,nical Differential Revision: https://phabricator.services.mozilla.com/D83462
0e658297a2bae55a714bde1bdb26928eafa190a7: Bug 1578042 - Improve dropped frames reporting for videos, by counting all frames in mImages that were never composited. r=jya,nical
Markus Stange <mstange.moz@gmail.com> - Thu, 16 Jul 2020 03:37:02 +0000 - rev 540804
Push 121925 by mstange@themasta.com at Thu, 16 Jul 2020 20:01:20 +0000
Bug 1578042 - Improve dropped frames reporting for videos, by counting all frames in mImages that were never composited. r=jya,nical In the current state this also counts frame drops while the video is offscreen, but this will be fixed in a later patch in the series. This patch also adjusts the time delta check: It now compares floored milliseconds. In 60fps WebM videos, the video frame durations are 16.0, 17.0, 17.0, 16.0, 17.0, 17.0, ... so we need to consider frames with 16.0ms as displayable even when the target frame duration is 16.67ms, otherwise we gloss over one third of the frames when counting potentially dropped frames. Differential Revision: https://phabricator.services.mozilla.com/D82635
035199ba3d5a6d14170d195634fd2208ad3cbbb3: Bug 1578042 - Don't call UpdateCompositedFrame outside of a composition. r=jya,nical
Markus Stange <mstange.moz@gmail.com> - Thu, 16 Jul 2020 08:47:21 +0000 - rev 540803
Push 121925 by mstange@themasta.com at Thu, 16 Jul 2020 20:01:20 +0000
Bug 1578042 - Don't call UpdateCompositedFrame outside of a composition. r=jya,nical Correctly indicate that we're not in a composition during SetDisplayList or during empty transactions, by making sure the composition timestamp is null outside of a composition. We also now return 0 rather than -1 from the first call to ChooseImageIndex outside of a composition, so that static images (like canvases) default to the correct initial frame. We don't call ChooseImageIndex for them again once we composite them. This is different from non-WebRender, which would call ChooseImageIndex on canvas layers during every composition. This introduces a behavior difference for static images when WebRender is enabled: Those images will no longer update mLastFrameID, because UpdateCompositedFrame will not be called during a composition for them. I'm also removing a comment that seems like it's unnecessarily duplicating information from another comment a few lines further up. That other comment is also easier to understand. Differential Revision: https://phabricator.services.mozilla.com/D83460
0306fe17b5aa1b210e1454f1e84fbc3d243135f1: Bug 1578042 - Move more logic into UpdateCompositedFrame. r=jya,nical
Markus Stange <mstange.moz@gmail.com> - Thu, 16 Jul 2020 03:37:02 +0000 - rev 540802
Push 121925 by mstange@themasta.com at Thu, 16 Jul 2020 20:01:20 +0000
Bug 1578042 - Move more logic into UpdateCompositedFrame. r=jya,nical This also makes it so that UpdateBias for non-WebRender is only called when the video frame changes. This mirrors the recent change that we made for WebRender in bug 1652181. Non-WebRender only calls UpdateCompositedFrame when it actually draws the video onto the screen, so when the video is the only thing that was updating, the new behavior is equivalent. But the new behavior makes more sense if you have a 30fps video and a 60fps animation running on a 60fps screen at the same time - now the bias won't be accidentally reset every other frame. Differential Revision: https://phabricator.services.mozilla.com/D83459
b0d63daa5d600b107ee99738fce6f67a14028946: Bug 1578042 - Update mLastFrameID in a new method UpdateCompositedFrame. r=jya,nical
Markus Stange <mstange.moz@gmail.com> - Thu, 16 Jul 2020 03:37:01 +0000 - rev 540801
Push 121925 by mstange@themasta.com at Thu, 16 Jul 2020 20:01:20 +0000
Bug 1578042 - Update mLastFrameID in a new method UpdateCompositedFrame. r=jya,nical Differential Revision: https://phabricator.services.mozilla.com/D82634
86a5e0827050e262bb713d6910a8c1d6e6ec3738: Bug 1646899 - P4: Handle object & embed via DocumentChannel. r=mattwoodrow,jya
Dan Glastonbury <dan.glastonbury@gmail.com> - Mon, 13 Jul 2020 00:48:57 +0000 - rev 540150
Push 121497 by dglastonbury@mozilla.com at Mon, 13 Jul 2020 00:50:31 +0000
Bug 1646899 - P4: Handle object & embed via DocumentChannel. r=mattwoodrow,jya Pass internal content policy type to DLL and switch behavior depending on type being loaded. This implementation immediately redirects channel back to the content process for further handling. Differential Revision: https://phabricator.services.mozilla.com/D80407
9f7c95cb5aacee7841bdca487a789ccf675a0994: Bug 1649349 - Don't delay rejecting DocumentLoadListener's Open promise when we switch process. r=jya
Matt Woodrow <mwoodrow@mozilla.com> - Sun, 12 Jul 2020 22:50:34 +0000 - rev 540127
Push 121490 by mwoodrow@mozilla.com at Sun, 12 Jul 2020 23:03:58 +0000
Bug 1649349 - Don't delay rejecting DocumentLoadListener's Open promise when we switch process. r=jya Differential Revision: https://phabricator.services.mozilla.com/D81648
2d709e60c76ec75960054105fae65a758d7a5e78: Bug 1649058 - Replace MozPromise with SyncRunnable and assert not main thread. r=jya
Alex Chronopoulos <achronop@gmail.com> - Thu, 02 Jul 2020 12:20:24 +0000 - rev 538427
Push 120570 by achronopoulos@mozilla.com at Thu, 02 Jul 2020 12:26:24 +0000
Bug 1649058 - Replace MozPromise with SyncRunnable and assert not main thread. r=jya Differential Revision: https://phabricator.services.mozilla.com/D81998
55f11d5e3341201488d1f461ef2f761f86e91df4: Bug 1649675 [Linux] Use DRM or Wayland VA-API display according to pref, r=jya
Martin Stransky <stransky@redhat.com> - Thu, 02 Jul 2020 10:31:45 +0000 - rev 538424
Push 120567 by ncsoregi@mozilla.com at Thu, 02 Jul 2020 11:50:26 +0000
Bug 1649675 [Linux] Use DRM or Wayland VA-API display according to pref, r=jya Depends on D81967 Differential Revision: https://phabricator.services.mozilla.com/D81968
d75dddfb97a95762ebd87f2129f40e1aa8470bf2: Bug 1649675 [Linux] Load vaGetDisplayDRM() from libva-drm.so.2 for VA-API DRM display, r=jya
Martin Stransky <stransky@redhat.com> - Thu, 02 Jul 2020 10:31:37 +0000 - rev 538423
Push 120567 by ncsoregi@mozilla.com at Thu, 02 Jul 2020 11:50:26 +0000
Bug 1649675 [Linux] Load vaGetDisplayDRM() from libva-drm.so.2 for VA-API DRM display, r=jya In order to implement VA-API playback we need a VADisplay connection. According to preference load libva-wayland.so.2 or libva-drm.so.2 libraries and dlsym vaGetDisplayWl or vaGetDisplayDRM to get VADisplay for VA-API decoding. Differential Revision: https://phabricator.services.mozilla.com/D81967
3e349b00a1e41edf93cd8e64afd1654f79f531c5: Bug 1649349 - Don't delay rejecting DocumentLoadListener's Open promise when we switch process. r=jya
Matt Woodrow <mwoodrow@mozilla.com> - Thu, 02 Jul 2020 07:12:23 +0000 - rev 538387
Push 120545 by mwoodrow@mozilla.com at Thu, 02 Jul 2020 07:17:19 +0000
Bug 1649349 - Don't delay rejecting DocumentLoadListener's Open promise when we switch process. r=jya Differential Revision: https://phabricator.services.mozilla.com/D81648
28298106459de32312347ccadbe138f6e0fde598: Bug 1649349 - Don't delay rejecting DocumentLoadListener's Open promise when we switch process. r=jya
Matt Woodrow <mwoodrow@mozilla.com> - Tue, 30 Jun 2020 19:19:59 +0000 - rev 538354
Push 120529 by mwoodrow@mozilla.com at Thu, 02 Jul 2020 00:39:15 +0000
Bug 1649349 - Don't delay rejecting DocumentLoadListener's Open promise when we switch process. r=jya Differential Revision: https://phabricator.services.mozilla.com/D81648
c1bcf9de8834d60c55e16d3fe90089e42d7b4b4b: Bug 1649120 [Linux] Rename Wayland/DMABuf config functions at ffmpeg, r=jya
Martin Stransky <stransky@redhat.com> - Wed, 01 Jul 2020 11:22:35 +0000 - rev 538198
Push 120465 by dluca@mozilla.com at Wed, 01 Jul 2020 11:27:36 +0000
Bug 1649120 [Linux] Rename Wayland/DMABuf config functions at ffmpeg, r=jya Depends on D81514 Differential Revision: https://phabricator.services.mozilla.com/D81515
31649a85ff043523dfb8c1ddbaa25cee2ff2ca81: Bug 1649120 [Linux] Rename dmabuf/vaapi preferences, r=jya
Martin Stransky <stransky@redhat.com> - Wed, 01 Jul 2020 11:22:07 +0000 - rev 538195
Push 120465 by dluca@mozilla.com at Wed, 01 Jul 2020 11:27:36 +0000
Bug 1649120 [Linux] Rename dmabuf/vaapi preferences, r=jya As DMABuf is going to be used under X11 let's remove Wayland keyword from the preferences and also use media.ffmpeg key. Wayland specific preferences rename: widget.wayland-dmabuf-textures.enabled to widget.dmabuf-textures.enabled widget.wayland-dmabuf-webgl.enabled to widget.dmabuf-webgl.enabled Change dmabuf preferences to media.ffmpeg ones: widget.wayland-dmabuf-vaapi.enabled to media.ffmpeg.vaapi.enabled widget.wayland-dmabuf-video-textures.enabled to media.ffmpeg.dmabuf-textures.enabled Implement media.ffmpeg.vaapi-drm-display.enabled preference to use DRM VA-API display instead of the native one. Differential Revision: https://phabricator.services.mozilla.com/D81512
f53cf203cbf5aec0797b17748ad096e56eb9c6ef: Bug 1649540 - Remove unified files workaround for MSVC in dom/media r=jya
David Major <dmajor@mozilla.com> - Wed, 01 Jul 2020 06:42:46 +0000 - rev 538181
Push 120457 by dmajor@mozilla.com at Wed, 01 Jul 2020 10:33:40 +0000
Bug 1649540 - Remove unified files workaround for MSVC in dom/media r=jya We no longer need to worry about MSVC issues. Differential Revision: https://phabricator.services.mozilla.com/D81730
c49a40eece91a508970479b59e2051ded8a9135f: Bug 1623461 - Clear nsDocShell::mBlankTiming when providing an existing timing object from a process switch. r=jya
Matt Woodrow <mwoodrow@mozilla.com> - Tue, 30 Jun 2020 03:32:43 +0000 - rev 537934
Push 120303 by mwoodrow@mozilla.com at Tue, 30 Jun 2020 07:10:29 +0000
Bug 1623461 - Clear nsDocShell::mBlankTiming when providing an existing timing object from a process switch. r=jya Differential Revision: https://phabricator.services.mozilla.com/D81636
33b415f44869de360738666d1eb4e857dbabef61: Bug 1647557 - Add preffed-off code for controlling document loads directly from CanonicalBrowsingContext. r=nika,jya,necko-reviewers,dragana
Matt Woodrow <mwoodrow@mozilla.com> - Tue, 30 Jun 2020 01:19:15 +0000 - rev 537911
Push 120290 by mwoodrow@mozilla.com at Tue, 30 Jun 2020 02:55:05 +0000
Bug 1647557 - Add preffed-off code for controlling document loads directly from CanonicalBrowsingContext. r=nika,jya,necko-reviewers,dragana Differential Revision: https://phabricator.services.mozilla.com/D70629
9404dd36d892589b8478352b988c5704c7c352e4: Bug 1646892 - Allow DocumentChannel process switches into the parent process. r=jya,nika
Matt Woodrow <mwoodrow@mozilla.com> - Sat, 27 Jun 2020 04:10:23 +0000 - rev 537705
Push 120177 by mwoodrow@mozilla.com at Sat, 27 Jun 2020 06:59:18 +0000
Bug 1646892 - Allow DocumentChannel process switches into the parent process. r=jya,nika Differential Revision: https://phabricator.services.mozilla.com/D80327
c2649a68a3a75f092e133ea5fef66297ea7673f5: Bug 1646892 - Move ParentChannelWrapper into a separate file. r=jya,nika
Matt Woodrow <mwoodrow@mozilla.com> - Sat, 27 Jun 2020 04:09:35 +0000 - rev 537704
Push 120177 by mwoodrow@mozilla.com at Sat, 27 Jun 2020 06:59:18 +0000
Bug 1646892 - Move ParentChannelWrapper into a separate file. r=jya,nika Differential Revision: https://phabricator.services.mozilla.com/D80326
e99d26b81d3a2fe10a651c61de4ec466841218cb: Bug 1648159 - Remove unnecessary redirection of promises when sink changes. r=jya
Alex Chronopoulos <achronop@gmail.com> - Thu, 25 Jun 2020 14:18:59 +0000 - rev 537435
Push 119989 by achronopoulos@mozilla.com at Thu, 25 Jun 2020 14:42:39 +0000
Bug 1648159 - Remove unnecessary redirection of promises when sink changes. r=jya At the end of `HTMLMediaElement::SetSrcMediaStreamSink` a redirection of MozPromises, from `GenericPromise::AllPromiseType` to `GenericPromise` is taking place. However, this is not necessary since this is an internal method and the returned value of the promise is not useful. Thus the `GenericPromise::AllPromiseType` can be returned directly and avoid the extra thread dispatch. Differential Revision: https://phabricator.services.mozilla.com/D80908
2d39c868776994011fb9ac51389ed10e35e1ef55: Bug 1638925 - Ensure that the event gets destroyed within the guards r=jya
Honza Bambas <honzab.moz@firemni.cz> - Wed, 24 Jun 2020 13:51:25 +0000 - rev 537400
Push 119964 by honzab.moz@firemni.cz at Thu, 25 Jun 2020 12:29:14 +0000
Bug 1638925 - Ensure that the event gets destroyed within the guards r=jya Differential Revision: https://phabricator.services.mozilla.com/D80171
331fd3b03fbe7d6dbc0d8ec191b4a260dfacd146: Bug 1638925 - Do not keep a raw pointer to an event in `LogTaskBase::Run` RAII class to avoid possible work with a released pointer, r=jya
Honza Bambas <honzab.moz@firemni.cz> - Wed, 24 Jun 2020 13:51:23 +0000 - rev 537399
Push 119964 by honzab.moz@firemni.cz at Thu, 25 Jun 2020 12:29:14 +0000
Bug 1638925 - Do not keep a raw pointer to an event in `LogTaskBase::Run` RAII class to avoid possible work with a released pointer, r=jya Differential Revision: https://phabricator.services.mozilla.com/D80640
7cb09c402732afc111838970f1807f7c1ce03412: Bug 1645704 [Wayland] Rename WaylandDMABufSurface to DMABufSurface at ffmpeg, r=jya
Martin Stransky <stransky@redhat.com> - Sun, 21 Jun 2020 13:59:09 +0000 - rev 536510
Push 119498 by ccoroiu@mozilla.com at Sun, 21 Jun 2020 16:30:39 +0000
Bug 1645704 [Wayland] Rename WaylandDMABufSurface to DMABufSurface at ffmpeg, r=jya Prepare ffmpeg decoding module to X11 dmabuf implementation. In order to cover both X11 and Wayland backend do: - Use DMABUFSurfaceImage instead of WaylandDMABUFSurfaceImage - Use DMABufSurface instead of WaylandDMABufSurface - Rename former DMABufSurface to DMABufSurfaceWrapper to state it actually wraps the DMABufSurface. - Use DMABufSurfaceYUV instead of WaylandDMABufSurfaceNV12 Differential Revision: https://phabricator.services.mozilla.com/D79638
8a463700d1698fead0b1804d96fcd59309db6f6e: Bug 1629788 [Wayland] Implement SW decoding to WaylandDMABufSurface, r=jya
Martin Stransky <stransky@redhat.com> - Sat, 13 Jun 2020 18:38:38 +0000 - rev 535624
Push 118972 by abutkovits@mozilla.com at Sat, 13 Jun 2020 19:12:28 +0000
Bug 1629788 [Wayland] Implement SW decoding to WaylandDMABufSurface, r=jya - Use WaylandDMABufSurface for SW decoded frames when they can be converted to NV12 format. - Rename VAAPIFrameHolder to DMABufSurface and use it as general placeholder for WaylandDMABufSurface surface. It's used for VA-API/SW video playback and holds decoded video images until thery are used by gecko rendering engine. - Implmenet a linked list of DMABufSurface where recently used frames are stored. The frames are recycled by ffmpeg decoder for VA-API and SW video playback. Differential Revision: https://phabricator.services.mozilla.com/D78292
9d1e4da287a6b2db78e48595f61b45a9e4d95c70: Bug 1629788 [Wayland] Implement SW decoding to WaylandDMABufSurface, r=jya
Martin Stransky <stransky@redhat.com> - Sat, 13 Jun 2020 10:35:40 +0000 - rev 535600
Push 118954 by btara@mozilla.com at Sat, 13 Jun 2020 10:39:46 +0000
Bug 1629788 [Wayland] Implement SW decoding to WaylandDMABufSurface, r=jya - Use WaylandDMABufSurface for SW decoded frames when they can be converted to NV12 format. - Rename VAAPIFrameHolder to DMABufSurface and use it as general placeholder for WaylandDMABufSurface surface. It's used for VA-API/SW video playback and holds decoded video images until thery are used by gecko rendering engine. - Implmenet a linked list of DMABufSurface where recently used frames are stored. The frames are recycled by ffmpeg decoder for VA-API and SW video playback. Differential Revision: https://phabricator.services.mozilla.com/D78292
308399471b6e70a047951712e4cb8e91bfc795a8: Bug 1644945 - Implement a wrapper nsIParentChannel for ParentProcessDocumentChannel so that we can use the same code in DocumentLoadListener. r=jya
Matt Woodrow <mwoodrow@mozilla.com> - Fri, 12 Jun 2020 21:03:06 +0000 - rev 535565
Push 118928 by mwoodrow@mozilla.com at Fri, 12 Jun 2020 21:29:57 +0000
Bug 1644945 - Implement a wrapper nsIParentChannel for ParentProcessDocumentChannel so that we can use the same code in DocumentLoadListener. r=jya Differential Revision: https://phabricator.services.mozilla.com/D79241
7a8c4bb304b870919276746e18296a601779f3fa: Bug 1645020 - Add `rust-analyzer` as a default plugin to `vscode`. r=jya
Andi-Bogdan Postelnicu <bpostelnicu@mozilla.com> - Fri, 12 Jun 2020 10:41:36 +0000 - rev 535452
Push 118859 by bpostelnicu@mozilla.com at Fri, 12 Jun 2020 10:42:30 +0000
Bug 1645020 - Add `rust-analyzer` as a default plugin to `vscode`. r=jya Differential Revision: https://phabricator.services.mozilla.com/D79290
05e436fbc095956356421978a548db389d000ed8: Bug 1644945 - Implement a wrapper nsIParentChannel for ParentProcessDocumentChannel so that we can use the same code in DocumentLoadListener. r=jya
Matt Woodrow <mwoodrow@mozilla.com> - Thu, 11 Jun 2020 16:21:45 +0000 - rev 535448
Push 118855 by mwoodrow@mozilla.com at Fri, 12 Jun 2020 09:29:51 +0000
Bug 1644945 - Implement a wrapper nsIParentChannel for ParentProcessDocumentChannel so that we can use the same code in DocumentLoadListener. r=jya Differential Revision: https://phabricator.services.mozilla.com/D79241
c448f9dcdedc76fdfdbcafebf8acca29c81e80cd: Bug 1638711 - Report correct error code in DocumentLoadListener if AsyncOpen fails. r=jya,necko-reviewers,valentin
Matt Woodrow <mwoodrow@mozilla.com> - Mon, 08 Jun 2020 23:17:52 +0000 - rev 534565
Push 118405 by mwoodrow@mozilla.com at Tue, 09 Jun 2020 02:20:05 +0000
Bug 1638711 - Report correct error code in DocumentLoadListener if AsyncOpen fails. r=jya,necko-reviewers,valentin Differential Revision: https://phabricator.services.mozilla.com/D77954
3529cf4e69b648b691d77fdf7f2e925dcc92cee3: Bug 1638711 - Report correct error code in DocumentLoadListener if AsyncOpen fails. r=jya,necko-reviewers,valentin
Matt Woodrow <mwoodrow@mozilla.com> - Mon, 08 Jun 2020 07:29:58 +0000 - rev 534374
Push 118299 by mwoodrow@mozilla.com at Mon, 08 Jun 2020 08:38:40 +0000
Bug 1638711 - Report correct error code in DocumentLoadListener if AsyncOpen fails. r=jya,necko-reviewers,valentin Depends on D77171 Differential Revision: https://phabricator.services.mozilla.com/D77954
865edc41179afc8f6f8a345d8c17a0a63597d6d8: Bug 1638652 - Only disable content conversion in the parent process if we're going to be delivering data to a content process. r=jya,necko-reviewers
Matt Woodrow <mwoodrow@mozilla.com> - Tue, 02 Jun 2020 23:43:19 +0000 - rev 533656
Push 117877 by mwoodrow@mozilla.com at Wed, 03 Jun 2020 05:58:18 +0000
Bug 1638652 - Only disable content conversion in the parent process if we're going to be delivering data to a content process. r=jya,necko-reviewers Differential Revision: https://phabricator.services.mozilla.com/D77399
7600c1bbd621e9ba857d419706b11e8b8ecbdfa0: Bug 1637235 - Implement a ring buffer for audio data. r=padenot,jya
Alex Chronopoulos <achronop@gmail.com> - Mon, 01 Jun 2020 15:53:18 +0000 - rev 533363
Push 117692 by achronopoulos@mozilla.com at Mon, 01 Jun 2020 18:02:41 +0000
Bug 1637235 - Implement a ring buffer for audio data. r=padenot,jya Implement a ring buffer that is not thread-safe and preallocate its internal buffers. The intention is that the internal data is preallocate to any thread and then read/write operations will take place in a single thread using the memory in a ring manner. Differential Revision: https://phabricator.services.mozilla.com/D74882
81012bc3b3ac59a2ed490dfed1c51b053bed3601: Bug 1637235 - Implement a ring buffer for audio data. r=padenot,jya
Alex Chronopoulos <achronop@gmail.com> - Mon, 01 Jun 2020 12:27:00 +0000 - rev 533224
Push 117659 by achronopoulos@mozilla.com at Mon, 01 Jun 2020 13:39:44 +0000
Bug 1637235 - Implement a ring buffer for audio data. r=padenot,jya Implement a ring buffer that is not thread-safe and preallocate its internal buffers. The intention is that the internal data is preallocate to any thread and then read/write operations will take place in a single thread using the memory in a ring manner. Differential Revision: https://phabricator.services.mozilla.com/D74882