- 08 Dec, 2020 40 commits
-
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/e59d8716b300..a13f6847238e 2020-12-08 angle-autoroll@skia-public.iam.gserviceaccount.com Roll Chromium from bbe26af2 to a3984b7e (468 revisions) 2020-12-08 syoussefi@chromium.org Suppress flaky multithreading swiftshader test If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/angle-chromium-autoroll Please CC syoussefi@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win-asan;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86 Bug: None Tbr: syoussefi@google.com Change-Id: I12ee3f84b478a59d567fdceb8d157892f08ed5f0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2578780Reviewed-by:
chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#834661}
-
arthursonzogni authored
With real users, we are seeing unexpected difference in between the sandbox flags computed from the renderer and the browser process. This is implemented by those two functions: - content::NavigationRequest::ComputeSandboxFlagsToCommit() - blink::FrameLoader::CalculateSandboxFlags After a navigation, the new document gets sandbox_flags from: - FramePolicy.sandbox, which contains everything except CSP. - The response's CSP sandbox. That's basically it. Both function does the same and are fed from the same data. The only difference is blink, which used "forced_sandbox_flags". This looked a bit mysterious at first. It turns out to be needed only for setting the sandbox flags for the initial empty document and the second 'initial empty document'. (e.g. not via navigation). Removing forced_sandbox_flags from CalculateSandboxFlags helps guaranteeing both browser side and renderer side computation always match. This make it explicit in the code from where the inheritance happens. This patch aligns inheriting sandbox from the opener with "OpenerFeatureState" (1), by moving it toward Frame, instead of the FrameLoader. (1) Turns out this will be removed: https://chromium-review.googlesource.com/c/chromium/src/+/2564396 Change-Id: I7098b459e485485630ab9edc99d392fcdbfdef4e Bug: 1153708 Fixed: 1153708 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2573362 Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by:
Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#834660}
-
Internal Frameworks Autoroller authored
TBR=bling-team@google.com Change-Id: I15d8d049626c71d53e06afe21437ac0b64aed21b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2578479Reviewed-by:
Internal Frameworks Autoroller <bling-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: Internal Frameworks Autoroller <bling-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#834659}
-
chromium-autoroll authored
Roll Chrome Win32 PGO profile from chrome-win32-master-1607374595-14878fd6c473cc4aebbe55be6f54c0ff79c3ed8e.profdata to chrome-win32-master-1607396289-70fddd0960b2020da66aa7308994f58594fe5850.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-win32-chromium Please CC pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:win-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I1a8e7dae44013f1b9dd93d079a22a6d8c58f383a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2578399Reviewed-by:
-
chromium-autoroll authored
Roll Chrome Win64 PGO profile from chrome-win64-master-1607374595-d12d27ca344e18f0b40a9dc8f54420fe6b49bde9.profdata to chrome-win64-master-1607396289-b814d12d89d9aa0b6942a46cc974733f2726887a.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-win64-chromium Please CC pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:win64-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I628099855f27bcc8065e6183d1aac2d67a30089b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2578108Reviewed-by:
-
Ramin Halavati authored
Updates ProfilePickerHandler to record ephemeral Guest profiles launch similar to off the record Guest profiles. Please see go/ephemeral-guest-profiles for more context. Bug: 1125474 Change-Id: I12625f7db4addfe6f8dcd7bc05584dbf45d404c8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2574755Reviewed-by:
David Roger <droger@chromium.org> Commit-Queue: Ramin Halavati <rhalavati@chromium.org> Cr-Commit-Position: refs/heads/master@{#834656}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/7843c257dbae..53fee9259fa3 2020-12-08 sigurds@chromium.org Improve types in front_end/sdk/SDKModel.js If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: chromium:1011811 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: Ibf01fc2779e7e81a88f9c21af5b49cecb5e8fd90 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2578663Reviewed-by:
-
chromium-autoroll authored
If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll Please CC chrome-fuchsia-gardener@grotations.appspotmail.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-deterministic-dbg;luci.chromium.try:fuchsia-x64-cast Tbr: chrome-fuchsia-gardener@grotations.appspotmail.com Change-Id: Ib0da17331a3638a708a8b43a79a74bf0f7702017 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2578658Reviewed-by:
-
Jiawei Shao authored
BUG=dawn:529 Change-Id: I9cae2840f7e653372d9434a2d8a9ea386ede988b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2574062 Commit-Queue: Jiawei Shao <jiawei.shao@intel.com> Reviewed-by:
Corentin Wallez <cwallez@chromium.org> Cr-Commit-Position: refs/heads/master@{#834653}
-
Alice Gong authored
BUG=1154032 Change-Id: Idb1cfb620b41e6dfe7bed4ed316de76679e6e250 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2578056Reviewed-by:
Roger Tawa <rogerta@chromium.org> Reviewed-by:
Alex Ilin <alexilin@chromium.org> Commit-Queue: Alex Ilin <alexilin@chromium.org> Auto-Submit: Alice Gong <alicego@google.com> Cr-Commit-Position: refs/heads/master@{#834652}
-
Alex Ilin authored
This refactor will enable ProfilePicker to use UserManagerProfileDialogDelegate for displaying force signin dialogs. Bug: 1156096 Change-Id: I2ae84c3bc882b45aa0a016d28e182d11cc87a0de Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2577220 Commit-Queue: Alex Ilin <alexilin@chromium.org> Reviewed-by:
-
Rainhard Findling authored
* Update the PW check UI to show compromised and weak password counts the same way as safety check does with crrev.com/c/2547582. * Also moves the corresponding strings from the SC to the PW check. Translation screenshots: IDS_SETTINGS_COMPROMISED_PASSWORDS_COUNT_SHORT https://storage.cloud.google.com/chromium-translation-screenshots/57beb450355e12e0a3ca2c8c9a4ce2b41a892535 IDS_SETTINGS_WEAK_PASSWORDS_COUNT_SHORT https://storage.cloud.google.com/chromium-translation-screenshots/3530dd0582d65de57d6d71d472576ce8c41fd292 Bug: 1128904 Change-Id: Ic98ed21c020132e3e36221b441eec138b2e85d63 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567779 Commit-Queue: Rainhard Findling <rainhard@chromium.org> Reviewed-by:
Jan Wilken Dörrie <jdoerrie@chromium.org> Reviewed-by:
Esmael Elmoslimany <aee@chromium.org> Cr-Commit-Position: refs/heads/master@{#834650}
-
Wojciech Dzierżanowski authored
Ignore invalid display work area that is reported as a transient value in some cases, e.g. when reconnecting via Remote Desktop. Bug: 1154202 Change-Id: I4915fbdd5dd23248692ab6a66b382349e262dc89 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2571302 Commit-Queue: Wojciech Dzierżanowski <wdzierzanowski@opera.com> Reviewed-by:
François Beaufort <beaufort.francois@gmail.com> Cr-Commit-Position: refs/heads/master@{#834649}
-
Alice Wang authored
This CL cleans up redundant GoogleActivityController. Bug: 1153038 Change-Id: I7a81ce074648c2830cb539d029784068eeb73ffa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2577197 Commit-Queue: Alice Wang <aliceywang@chromium.org> Reviewed-by:
Tanmoy Mollik <triploblastic@chromium.org> Cr-Commit-Position: refs/heads/master@{#834648}
-
sauski authored
Replace the stub functions for conversion measurement on the PrivacySettingsSandbox class with implementations that respect both the privacy sandbox preferences and cookie content settings. Bug: 1152336 Change-Id: I1d7baed13f9830f95f389d26d80629cec17e2988 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2569653Reviewed-by:
Christian Dullweber <dullweber@chromium.org> Reviewed-by:
Martin Šrámek <msramek@chromium.org> Commit-Queue: Theodore Olsauskas-Warren <sauski@google.com> Cr-Commit-Position: refs/heads/master@{#834647}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/03c2a0ffe52f..e94373d60dc3 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll Please CC engedy@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: None Tbr: engedy@google.com Change-Id: I8b3596d44255fa22405935cb772e72581023f185 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2578779Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Reviewed-by:
Balazs Engedy <engedy@chromium.org> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#834646}
-
Hitoshi Yoshida authored
The test failure happens only on BF cache bot. Dropped the flakiness expectation from general TestExpectations to catch actual failures. Bug: 1155125 Change-Id: I0966a5b76962b60e24870640249c65faeec4bdb4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2576224 Commit-Queue: Rakina Zata Amni <rakina@chromium.org> Auto-Submit: Hitoshi Yoshida <peria@chromium.org> Reviewed-by:
Rakina Zata Amni <rakina@chromium.org> Cr-Commit-Position: refs/heads/master@{#834645}
-
Richard Knoll authored
This flag will be enabled on M88 Beta to launch the Mute Notifications feature on Desktop platforms. This will prevent potentially sensitive notification content from showing up on full-screen-share recordings. Approved launch bug for Beta: crbug.com/1133886 Bug: 1133886 Change-Id: I4a549738a02d73883c87731e4cef1ce846a30de8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2577224Reviewed-by:
Peter Beverloo <peter@chromium.org> Commit-Queue: Richard Knoll <knollr@chromium.org> Cr-Commit-Position: refs/heads/master@{#834644}
-
sandromaggi authored
This changes the |SelfDeleteFullCardRequester| to respond with adding details to the failure status according to the the result it got from the |FullCardRequest|. The |UseCreditCardAction| does not treat a failed status, but passes it on as the response to the action. Bug: b/174304769 Change-Id: Idcad69cf74eab14a9a59d5b6dc1ea166b230db67 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2577218 Commit-Queue: Sandro Maggi <sandromaggi@google.com> Reviewed-by:
Clemens Arbesser <arbesser@google.com> Cr-Commit-Position: refs/heads/master@{#834643}
-
Minggang Wang authored
URLLoaderClientImpl is an implementation of network::mojom::URLLoaderClient and used by ResourceDispatcher only to receives messages from a single URLLoader, it couples with the ResourceDispatcher tightly. As part of the OnionSoup project, this patch implements: 1. Moves URLLoaderClientImpl to third_party/blink/public/platform/ and decouples it from the ResourceDispatcher by adding an interface of WebURLLoaderClientObserver. 2. Moves url_loader_client_impl_unittest.cc into blink and decouples it from the dependency of TestRequestPeer by implementing a MockWebURLLoaderClientObserver that mostly inherits the functionality of TestRequestPeer. So, after this patch, the TestRequestPeer will be only used by the unit test of ResourceDispatcher and could be removed with the ResourceDispatcher together eventually. Change-Id: I08793d58623713ee1fc40f9e2395e19ea141f952 Bug: 1110032 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2560678Reviewed-by:
Makoto Shimazu <shimazu@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Hiroki Nakagawa <nhiroki@chromium.org> Commit-Queue: Minggang Wang <minggang.wang@intel.com> Cr-Commit-Position: refs/heads/master@{#834642}
-
Keishi Hattori authored
When BackupRefPtr is used for LocalStorageImpl::StorageAreaHolder::area_ptr_, the destruction order of the fields causes a null dereference. ~StorageAreaHolder() ends up calling StorageAreaHolder::PrepareToCommit() which tries to use area_ptr_ without a null check Bug: 1080832 Change-Id: Iff06bbf440eb5a3d26226c85b13b36ac037f1fca Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2564932Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Bartek Nowierski <bartekn@chromium.org> Reviewed-by:
Marijn Kruisselbrink <mek@chromium.org> Commit-Queue: Keishi Hattori <keishi@chromium.org> Cr-Commit-Position: refs/heads/master@{#834641}
-
Luciano Pacheco authored
Generate the JS modules for the following elements: * <xf-button> * <xf-circular-progress> * <xf-display-panel> * <xf-panel-item> And their test: files_xf_elements.unittest.m.js. Bug: 1133186 Change-Id: I22c71f6a6e648c4a1b027ef1766eb4df060f9f93 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2576299 Auto-Submit: Luciano Pacheco <lucmult@chromium.org> Reviewed-by:
Jeremie Boulic <jboulic@chromium.org> Commit-Queue: Jeremie Boulic <jboulic@chromium.org> Cr-Commit-Position: refs/heads/master@{#834640}
-
Victor Hugo Vianna Silva authored
The feature has been launched to 100% Stable for over a month [1], so this CL removes the feature toggle. Besides this, some instances of base::RepeatingClosure() in profile_sync_service_unittest.cc are replaced with base::DoNothing(). [1]https://groups.google.com/a/google.com/g/cr-rel-notify/c/_DOaHr_-x10/m/CA_P823xAQAJ https://groups.google.com/a/google.com/g/cr-rel-notify/c/mOOb_eXMgy4/m/aRpz0POPAAAJ https://groups.google.com/a/google.com/g/cr-rel-notify/c/bJ323M0Nrr4/m/jVRaVJWIBAAJ https://groups.google.com/a/google.com/g/cr-rel-notify/c/ad3g3moxG4k/m/n-KJcTuTAAAJ Bug: 1140447 Change-Id: Ifc72d6a35402d72bb5935a3dbc2d838fb5855bcb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2489894Reviewed-by:
Marc Treib <treib@chromium.org> Commit-Queue: Victor Vianna <victorvianna@google.com> Cr-Commit-Position: refs/heads/master@{#834639}
-
Heng-Ruey Hsu authored
Simply rename *_halv3 to *_delegate to keep git history. Add an intermediate layer to prepare further refactor to support multiple streams. Bug: b:151047537 Test: Manually Change-Id: Ic2db36b003206972aabd70a5ceafd00e9f8f1c3e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2351931 Commit-Queue: Heng-ruey Hsu <henryhsu@chromium.org> Reviewed-by:
Miguel Casas <mcasas@chromium.org> Reviewed-by:
Wei Lee <wtlee@chromium.org> Auto-Submit: Heng-ruey Hsu <henryhsu@chromium.org> Cr-Commit-Position: refs/heads/master@{#834638}
-
sauski authored
Fixes an issue where the mouse interactions with the toggle buttons under a settings-collapse-radio-button which has been disabled by poliy do not work. Bug: 1156264 Change-Id: Ifac3bd2767378b9f05ad95586ec4a46ea262a561 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2577225Reviewed-by:
Rainhard Findling <rainhard@chromium.org> Commit-Queue: Theodore Olsauskas-Warren <sauski@google.com> Cr-Commit-Position: refs/heads/master@{#834637}
-
Daniel Vogelheim authored
Fix-it week: Fix failing WPT test. Change-Id: I3bf43d39f19bc9b690bb943185e7ddb8961699da Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2574951Reviewed-by:
Yifan Luo <lyf@chromium.org> Commit-Queue: Daniel Vogelheim <vogelheim@chromium.org> Cr-Commit-Position: refs/heads/master@{#834636}
-
Daniel Vogelheim authored
Fix-It week: The test passes, but will then report an error in the test harness, because the string chosen for the example test is not actually a valid script. If we simply return "0" - which is valid JS - the bug disappears. (The test doesn't care about the script anyhow, only about whether it's accepted as input ot not.) Change-Id: Ie36c27965494f71b796176d3818aefd41b3067ab Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2574953Reviewed-by:
-
Side Yilmaz authored
This CL passes the correct profile in LayerTitleCache by accessing profile with tab#isIncognito boolean. Bug: 1048632 Change-Id: I9555f637a890ea5052ac044667d953d221d0f84a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567226Reviewed-by:
David Trainor <dtrainor@chromium.org> Commit-Queue: Side YILMAZ <sideyilmaz@chromium.org> Cr-Commit-Position: refs/heads/master@{#834634}
-
Balazs Engedy authored
This reverts commit 09825450. Reason for revert: `generate_build_files` failure on `Cast Audio Linux` builder: ERROR at //ui/gfx/linux/BUILD.gn:8:1: Assertion failed. assert(use_x11 || ozone_platform_drm || ozone_platform_wayland || ^----- See //media/gpu/chromeos/BUILD.gn:92:5: which caused the file to be included. "//ui/gfx/linux:drm", ^------------------- Original change's description: > media/platform_vf_utils: Handle null GMB factory. > > This CL handles a null GpuMemoryBufferFactory in > AllocateGpuMemoryBufferHandle() so that the caller is not obligated to > pass a valid factory. This is in preparation for follow-ups CLs to > remove the need for video encode accelerators to have access to a > GpuMemoryBufferFactory. > > When the GpuMemoryBufferFactory is null, we just use the render node > directly to allocate a native buffer object and then we wrap it into a > GpuMemoryBufferHandle. > > So, why do we still keep the option to have a non-null > GpuMemoryBufferFactory? This is because that path is still useful in the > decoding case: when a buffer is created with the GpuMemoryBufferFactory, > the corresponding NativePixmap is cached [1]; eventually, a SharedImage > needs to be created and to do so we pass the GpuMemoryBufferHandle > obtained from the factory [2]; when the SharedImage system needs to > create the GLImage for the buffer, it passes the handle to the > factory [3] which in turn uses it to look up the cached > NativePixmap [4]. This saves us from going through a gbm_bo_import() > (which also implies a thread hop to the DRM thread). > > So, in conclusion, for buffers that need to be displayed later, it's > still better to use the GMB factory owned by the GpuServiceImpl. For > encoders this is not the case. > > [1] https://source.chromium.org/chromium/chromium/src/+/master:gpu/ipc/service/gpu_memory_buffer_factory_native_pixmap.cc;l=319;drc=d81c5852498699fe3cd812e78d31c77c28e29281 > [2] https://source.chromium.org/chromium/chromium/src/+/master:media/gpu/chromeos/mailbox_video_frame_converter.cc;l=355-359;drc=d81c5852498699fe3cd812e78d31c77c28e29281 > [3] https://source.chromium.org/chromium/chromium/src/+/master:gpu/command_buffer/service/shared_image_backing_gl_texture.cc;l=355-356;drc=d81c5852498699fe3cd812e78d31c77c28e29281 > [4] https://source.chromium.org/chromium/chromium/src/+/master:gpu/ipc/service/gpu_memory_buffer_factory_native_pixmap.cc;l=164-172;drc=d81c5852498699fe3cd812e78d31c77c28e29281 > > Bug: b:173167846 > Test: video.EncodeAccel.h264_720p_nv12_dmabuf on elm > Change-Id: I7b730eb843da7503c61bffe30dce7a5ce51dec60 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568937 > Commit-Queue: Andres Calderon Jaramillo <andrescj@chromium.org> > Reviewed-by: Miguel Casas <mcasas@chromium.org> > Reviewed-by: Hirokazu Honda <hiroh@chromium.org> > Cr-Commit-Position: refs/heads/master@{#834608} TBR=mcasas@chromium.org,hiroh@chromium.org,andrescj@chromium.org,chromium-scoped@luci-project-accounts.iam.gserviceaccount.com Change-Id: Ibaf9e8a6e473a3b566ee9d5dd45b25a5f5283c14 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: b:173167846 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2578836Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/2d4ece529113..7843c257dbae 2020-12-08 tvanderlippe@chromium.org Upgrade third_party/marked to 1.2.5 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: None Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I5d9c8cb370d91797d70b3265a11e784701dc0386 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2578777Reviewed-by:
-
Yu Su authored
Add UKM logging for Lens chip shown and action: - record Lens chip shown event in the context menu metric "ContextMenuAndroid.Shown" - record Lens chip action in the context menu metric "ContextMenuAndroid.Selected" with an action id ShopWithGoogleLensChip Add an UMA histogram for Lens Prime errors: - The histogram is used to record errors occurred in Lens Prime session processing. https://chrome-internal-review.googlesource.com/c/clank/internal/apps/+/3412247 - The error codes are integer constants defined by the Lens SDK. Change-Id: Ibfa4134ee2d29b1d010654c7762bc820eb528ad4 Bug: b/166648354 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2551256 Commit-Queue: Yu Su <yusuyoutube@google.com> Reviewed-by:
Theresa <twellington@chromium.org> Reviewed-by:
Ben Goldberger <benwgold@google.com> Reviewed-by:
Steven Holte <holte@chromium.org> Reviewed-by:
Sinan Sahin <sinansahin@google.com> Cr-Commit-Position: refs/heads/master@{#834631}
-
Nohemi Fernandez authored
Currently the SigninPromoViewMode uses implicit naming scheme cold/warm to represent the sign-in state. With the addition of a sync promo it becomes necessary to be more precise with the state of accounts on the device that will be represented in this enum. Bug: 1151289 Change-Id: I88e7e940ce8248c4b6f3d6e03c916f6ed5866df9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2574737Reviewed-by:
Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
Jérôme Lebel <jlebel@chromium.org> Commit-Queue: Nohemi Fernandez <fernandex@chromium.org> Cr-Commit-Position: refs/heads/master@{#834630}
-
Camillo Bruni authored
Delay calling into V8 for detected the topmost script. Crossing the API and getting a stack trace can be avoided in many case. This has a measurable impact on Speedometer. Bug: 808503 Change-Id: I6ed1b8734056ecb2efd55cf83f1d7a3302690f52 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2571091Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#834629}
-
Morten Stenshorne authored
TBR=ikilpatrick@chromium.org Bug: 1156312 Change-Id: I1885dfb7c9b437bc78f80b0b833388981a4a75e3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2577467Reviewed-by:
Morten Stenshorne <mstensho@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#834628}
-
Jérémie Boulic authored
Update modules generation script: - Fix detection of duplicate dependencies - Update class export condition: export class if the class is used in another JS file - Fix clang-format off/on Bug: 1133186 Change-Id: Icb5b38f8d57ca69912397b489b8e49dd23e1b8b2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2575303Reviewed-by:
Luciano Pacheco <lucmult@chromium.org> Commit-Queue: Jeremie Boulic <jboulic@chromium.org> Cr-Commit-Position: refs/heads/master@{#834627}
-
David Jean authored
TBR=stkhapugin@chromium.org Bug: 1156541 Change-Id: Ic0d27facc25b67778ace7c21d3cd5c4adcaf74da Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2577681Reviewed-by:
David Jean <djean@chromium.org> Commit-Queue: David Jean <djean@chromium.org> Auto-Submit: David Jean <djean@chromium.org> Cr-Commit-Position: refs/heads/master@{#834626}
-
Victor Costan authored
make_heap is linear in the size of the input, not logarithmic. Change-Id: I88a7c78bfdae4c7dfd09efa433febc6ffdd2d9a2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2577034Reviewed-by:
-
Keishi Hattori authored
Bug: 1080832 Change-Id: Ifb7f704416ec9e993f1c180a3a72a76b7ffb2452 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2578417Reviewed-by:
Takashi Sakamoto <tasak@google.com> Commit-Queue: Bartek Nowierski <bartekn@chromium.org> Cr-Commit-Position: refs/heads/master@{#834624}
-
James Vecore authored
This is a mechanical change to move the nearby-progress Polymer component from being chrome://nearby (Poylmer3) only to being shared with chrome://os-settings (Polymer2/3). This necessary for Nearby Share's launch despite Polymer2 being phased out (the conversion won't be complete in time for M-89 launch). Bug: 1156035 Change-Id: Iff63927d43215dbcab4325c5794c792fed1550df Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2575947 Commit-Queue: James Vecore <vecore@google.com> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#834623}
-
Luciano Pacheco authored
Bug: 1133186 Change-Id: Ifc81fa000fa91a69e8eed2450b9d8fbe4c61dd7a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2576859 Commit-Queue: Luciano Pacheco <lucmult@chromium.org> Commit-Queue: Jeremie Boulic <jboulic@chromium.org> Reviewed-by:
-
