- 23 Jan, 2020 40 commits
-
-
Eric Seckler authored
Also includes a manual modification to switch to perfetto's EventContext. https://android.googlesource.com/platform/external/perfetto.git/+log/aa94421bfd1f..6ce872b758f4 git log aa94421bfd1f..6ce872b758f4 --date=short --first-parent --format='%2020-01-23 ddrone@google.com Merge "Add clangd working folder to .gitignore" 2020-01-23 eseckler@google.com Merge "client lib: Don't depend on default_deps from include/perfetto/tracing" 2020-01-23 fmayer@google.com Merge "Mark merged callsites as [merged]" 2020-01-23 fmayer@google.com Fix infinity self size. 2020-01-23 fmayer@google.com Merge changes I2c6ef9a4,I196e54e8 2020-01-23 fmayer@google.com Merge "Show heap graphs in UI." 2020-01-23 treehugger-gerrit@google.com Merge "TrackEvent: Add support for legacy events with arguments" 2020-01-23 lalitm@google.com tp: add multiple filter benchmark on table 2020-01-23 eseckler@google.com Revert "build: Remove dep on client lib from Chrome's libperfetto" Created with: gclient setdep -r src/third_party/perfetto@6ce872b758f4 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-chromium-autoroll Please CC perfetto-bugs@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/+/master/autoroll/README.md Bug: None Change-Id: I74f9d9b4c444da09532e4ccf54ec20b9658d3087 Tbr: perfetto-bugs@google.com Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2014931 Commit-Queue: Eric Seckler <eseckler@chromium.org> Reviewed-by:
Sami Kyöstilä <skyostil@chromium.org> Reviewed-by:
Eric Seckler <eseckler@chromium.org> Cr-Commit-Position: refs/heads/master@{#734468}
-
Johannes Kron authored
This is a reland of 0fdf70f4 Reland with some tests disabled for ASAN builds. Original change's description: > Set PROCESSING_TIME and CAPTURE_BEGIN_TIME of WebRTC video frames > > Bug: chromium:1011581 > Change-Id: I12cc31309f896f6a00802adb5cb1991f8db9b342 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007209 > Commit-Queue: Johannes Kron <kron@chromium.org> > Reviewed-by: Guido Urdaneta <guidou@chromium.org> > Cr-Commit-Position: refs/heads/master@{#733959} Bug: chromium:1011581 Change-Id: I911457709f7404d205219b4d56c58565cffc0440 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2014928Reviewed-by:
Guido Urdaneta <guidou@chromium.org> Commit-Queue: Johannes Kron <kron@chromium.org> Cr-Commit-Position: refs/heads/master@{#734467}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/878a52cac350..35101480671e Created with: gclient setdep -r src-internal@35101480671e 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 jbudorick@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/+/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: None Tbr: jbudorick@google.com Change-Id: Icb10cb628e3f4dd2241edc8439d4247c18885488 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016869Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#734466}
-
Stephen Nusko authored
This reverts commit 92ff17fd. Reason for revert: Keep SMB around forever. TBR=avi@chromium.org Change-Id: Ifc811f7aa420dc63a80dc62cb292c16e5fd40bb3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2014930Reviewed-by:
Stephen Nusko <nuskos@chromium.org> Reviewed-by:
-
Anton Bikineev authored
For minor GCs, we clear remembered sets after visiting them to reduce potential cache misses. We also must not forget to clear them after major GCs. Bug: 1029379 Change-Id: Id8fc6ca300f308112513b9146e6ff6ccdd848399 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2013241 Commit-Queue: Anton Bikineev <bikineev@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#734464}
-
Fergal Daly authored
Follow-up to https://crrev.com/c/2011585 Change-Id: I045e22957c5e3b9ad93ae9604164490febe0fccf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015904Reviewed-by:
Bret Sepulveda <bsep@chromium.org> Commit-Queue: Fergal Daly <fergal@chromium.org> Cr-Commit-Position: refs/heads/master@{#734463}
-
Josh Karlin authored
Bug: 1042695 Change-Id: I6e782f866309ae4cf8994c79e92844455aececbc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003554Reviewed-by:
Charlie Harrison <csharrison@chromium.org> Commit-Queue: Josh Karlin <jkarlin@chromium.org> Cr-Commit-Position: refs/heads/master@{#734462}
-
Nicolas Ouellet-Payeur authored
Previously, ExtensionPolicyMigrators only ran on platform policies, and machine-level user cloud policies. This leaves out user cloud policies, and CrOS-specific policy providers. This CL makes the list of ExtensionPolicyMigrators static, instead of each provider keeping a separate list. This ensures no provider is left out of the policy migrator logic. TESTED=checked that the LBS extension picks up `BrowserSwitcherEnabled` when it's set through user cloud policy Bug: 1043775, 1030607 Change-Id: Ib257d2f18e3a106cbcd04d957b84a09b005a4680 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2013485Reviewed-by:Julian Pastarmov <pastarmovj@chromium.org> Commit-Queue: Nicolas Ouellet-Payeur <nicolaso@chromium.org> Cr-Commit-Position: refs/heads/master@{#734461}
-
Maxim Kolosovskiy authored
Autofill Assistant should be able to generate new strong password in some flows. This CL adds password generation functionality to the SetFormFieldValue action. TODO: this CL doesn't implement filling the confirmation field. Bug: 1043132 Change-Id: Id31d98d74a66ec80106284ea49e57b9679651f63 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007408Reviewed-by:
Mathias Carlen <mcarlen@chromium.org> Reviewed-by:
Clemens Arbesser <arbesser@google.com> Commit-Queue: Maxim Kolosovskiy <kolos@chromium.org> Cr-Commit-Position: refs/heads/master@{#734460}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/material-foundation/material-font-disk-loader-ios/+log/93acc021e303..8e30188777b0 git log 93acc021e303..8e30188777b0 --date=short --first-parent --format='%ad %ae %s' 2017-02-17 willlarche@users.noreply.github.com [Docs] Clarity in README (#1) Created with: gclient setdep -r src/ios/third_party/material_font_disk_loader_ios/src@8e30188777b0 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/material-font-disk-loader-ios-chromium Please CC bling-p10-rolls@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/+/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:ios-internal-mdc Bug: None Tbr: bling-p10-rolls@google.com Change-Id: I8bb0b370de889e5014d78532bbd8703c2d9a091c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016865Reviewed-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@{#734459}
-
Yutaka Hirano authored
When CORS is involved there may be multiple network::URLLoader associated with one InProgressRequest, because CorsURLLoader may create a new network::URLLoader for the same request id in redirect handling - see CorsURLLoader::FollowRedirect. In such a case the old network::URLLoader is going to be detached fairly soon, so we don't need to take care of it. Bug: 1043874 Change-Id: Icd91931d817898f59980fbadbb17ad6e63df07cc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2011781Reviewed-by:
Clark DuVall <cduvall@chromium.org> Reviewed-by:
Karan Bhatia <karandeepb@chromium.org> Reviewed-by:
Matt Mueller <mattm@chromium.org> Reviewed-by:
Takashi Toyoshima <toyoshim@chromium.org> Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Commit-Queue: Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#734458}
-
Peter Marshall authored
A frontend CL changes the order of some of these messages: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2016752 Bug: chromium:1010534 Change-Id: I1a4a6e28cad9038fe2ac9f18078fd8b423fa845d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015056 Auto-Submit: Peter Marshall <petermarshall@chromium.org> Reviewed-by:
Mathias Bynens <mathias@chromium.org> Commit-Queue: Peter Marshall <petermarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#734457}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/4b64b3f2634c..ddbec81f2d80 git log 4b64b3f2634c..ddbec81f2d80 --date=short --first-parent --format='%ad %ae %s' 2020-01-23 tvanderlippe@chromium.org Map imports to Protocol to ProtocolModule 2020-01-23 tvanderlippe@chromium.org Migrates protocol/ to ESM internally 2020-01-23 aerotwist@chromium.org [Global] Update refs to Bindings.networkProjectManager 2020-01-23 tvanderlippe@chromium.org Standardize license headers 2020-01-23 mathias@chromium.org Improve npm run debug-test output Created with: gclient setdep -r src/third_party/devtools-frontend/src@ddbec81f2d80 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/+/master/autoroll/README.md Bug: chromium:1006759 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: Ibc484a88d01ba9bebf1c3149b31dc1f11c439f7d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016864Reviewed-by:
-
Sebastien Lalancette authored
LayerTreeHostTestEarlyDamageCheckStops.RunMultiThread_DelegatingRenderer is flaky. TBR=weiliangc@chromium.org Bug: 1043900 Change-Id: I9bf1efd00208f7a068083fe24dfe97e81a9c2309 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015659Reviewed-by:
Sebastien Lalancette <seblalancette@chromium.org> Commit-Queue: Sebastien Lalancette <seblalancette@chromium.org> Cr-Commit-Position: refs/heads/master@{#734455}
-
Kevin Ellis authored
https://drafts.csswg.org/web-animations/#replacing-animations Animations with fill modes are a potential source of memory leaks. To overcome this problem, replaceable animations were introduced to the spec. If a finished animation is active purely by virtue of having a fill mode and if all of the properties have been replaced by an animation higher in the composite ordering, then the animation can be removed (somewhat over simplified). Animations can be forced to remain active via the persist() method. This patch introduces Animation.replaceState and Animation.persist() as well as support for detection and removal of replaced animations. The logic for handling CSS transitions and CSS animations has been oversimplified in this patch to avoid over-aggressive pruning. Special handling for animations with owning elements will be adding in a later patch. CommitStyle will also be added in a later patch. Note that removal of replaced animations can introduce a visual change if the composite mode is not replace. This is intentional (https://github.com/w3c/csswg-drafts/issues/3689) as the memory leak was seen as the more serious issue, and can be addressed via use of persist and commitStyle. https://www.chromestatus.com/feature/5127767286874112 https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/H5sz_dg6fKc/1X7K7U4XCgAJ Bug: 981905 Change-Id: I704cb3964aae0336266984ad3da8e37578b3bcb9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994014Reviewed-by:
Robert Flack <flackr@chromium.org> Reviewed-by:
Yi Gu <yigu@chromium.org> Commit-Queue: Kevin Ellis <kevers@chromium.org> Cr-Commit-Position: refs/heads/master@{#734454}
-
Vladislav Kuzkokov authored
This is a reland of 3e49c929 Original change's description: > [CrOS Printing] Don't send username and filename unencrypted > > This situation may come up if policy was changed after printer was > selected. We reject printing job since silently omitting username and > filename could be confusing. > > Bug: 1042798 > Change-Id: Iba385503d8f7e960291728d6515ca7c236220847 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2004992 > Reviewed-by: Sean Kau <skau@chromium.org> > Reviewed-by: Lei Zhang <thestig@chromium.org> > Commit-Queue: Lei Zhang <thestig@chromium.org> > Cr-Commit-Position: refs/heads/master@{#734128} TBR=thestig@chromium.org,skau@chromium.org,yoichio@chromium.org Bug: 1042798 Change-Id: I75d30cc7c94d843cbbc32318907165bfede6df69 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015029Reviewed-by:
Vladislav Kuzkokov <vkuzkokov@chromium.org> Commit-Queue: Vladislav Kuzkokov <vkuzkokov@chromium.org> Cr-Commit-Position: refs/heads/master@{#734453}
-
Vitor Carvalho authored
Bug: 940454 Change-Id: I6c0062752dabb9f39a8d02ff7cb3261835ee2ebb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010921 Commit-Queue: Vitor Carvalho <vtrmc@chromium.org> Reviewed-by:
Aga Wronska <agawronska@chromium.org> Cr-Commit-Position: refs/heads/master@{#734452}
-
Alice Wang authored
This CL adds espresso tests for signin and signout workflow and fixes a bug that signout was recorded twice when confirmed or dismissed. Bug: 1038326,1038924 Change-Id: I1c7d9d75f0e32c2d9fde6b9b62f928a562b59ea5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1986083 Commit-Queue: Alice Wang <aliceywang@chromium.org> Reviewed-by:
Boris Sazonov <bsazonov@chromium.org> Reviewed-by:
Tanmoy Mollik <triploblastic@chromium.org> Cr-Commit-Position: refs/heads/master@{#734451}
-
Steve Anton authored
WebRTC is moving the implementation of reference counting into the base class which means classes inheriting from RefCountInterface will no longer be able to define a copy operator. Bug: webrtc:11308 Change-Id: I74570c04b7e9724c4a3a4263ea13f3a56667af80 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015981 Auto-Submit: Steve Anton <steveanton@chromium.org> Commit-Queue: Henrik Boström <hbos@chromium.org> Reviewed-by:
Henrik Boström <hbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#734450}
-
Colin Blundell authored
All //chrome-level dependencies have been cleaned in preceding CLs, so the componentization is straightforward. We leave the componentization of the unittest to a followup as it still has //chrome-level dependencies to be cleaned. We also defer putting the files in the captive_portal namespace until all of the related componentizations have been completed to avoid churn on files that are currently in //chrome but will shortly be moved to //components/captive_portal/content. This componentization is necessary as part of the ongoing effort to componentize //chrome's SSLErrorHandler. TBR=jochen@chromium.org Bug: 1030692 Change-Id: I84bd90cd026cd461a349f8e5a95a6b8965837b05 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2011926 Commit-Queue: Colin Blundell <blundell@chromium.org> Reviewed-by:
Christian Dullweber <dullweber@chromium.org> Reviewed-by:
Matt Menke <mmenke@chromium.org> Cr-Commit-Position: refs/heads/master@{#734449}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/5cddf9e222f6..878a52cac350 Created with: gclient setdep -r src-internal@878a52cac350 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 jbudorick@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/+/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: chromium:1042208 Tbr: jbudorick@google.com Change-Id: I5856bdd8f7bef56cfc75a6bdc5c9491a5b8ec5d3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016862Reviewed-by:
-
Ian Kilpatrick authored
As above. There should be no behaviour change. Change-Id: I2af0b4064569df403bf993f8c32a655c0c1cd149 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015053Reviewed-by:
Christian Biesinger <cbiesinger@chromium.org> Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#734447}
-
Henrique Ferreiro authored
Since obj files are loaded lazily, in order to set up breakpoints for a component build, the program needs to run at least once. Add a notice regarding this behaviour. Bug: 1044564 Change-Id: Id2b90ebcbc658d1d2ad84b4fb8d09ac9a83e16db Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2014967Reviewed-by:
Nico Weber <thakis@chromium.org> Commit-Queue: Henrique Ferreiro <hferreiro@igalia.com> Cr-Commit-Position: refs/heads/master@{#734446}
-
Yutaka Hirano authored
Bug: 1011392 Change-Id: Ibe0f4ae6978c6ed62a1d0df7d9afe0fa9d413a06 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015910Reviewed-by:
Adam Rice <ricea@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Commit-Queue: Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#734445}
-
Internal Frameworks Autoroller authored
TBR=eugenebut@google.com Change-Id: I6f82a9e4ffbd1e5d89d7044646165bb6c9b9c2d4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016842Reviewed-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@{#734444}
-
Anatoliy Potapchuk authored
Currently we were displaying permission prompts in web kiosk mode for origins of not the main app. To keep it consistent with other types of kiosks, we should deny those requests. We are not explicitly denying them, but leaving them unanswered, this preventing them from being stored into prefs. Bug: 1044551 Change-Id: Ic6f1a260d3f03b92fc52f8f341c6259155b791d5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2014403 Commit-Queue: Balazs Engedy <engedy@chromium.org> Reviewed-by:
Balazs Engedy <engedy@chromium.org> Cr-Commit-Position: refs/heads/master@{#734443}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/4ae5f4f5ce1e..4b64b3f2634c git log 4ae5f4f5ce1e..4b64b3f2634c --date=short --first-parent --format='%ad %ae %s' 2020-01-23 aerotwist@chromium.org [Global] Remap refs to Common.moduleSetting 2020-01-23 mathias@chromium.org Update Chromium builds for tests 2020-01-23 aerotwist@chromium.org [Global] Update refs to Common.settings Created with: gclient setdep -r src/third_party/devtools-frontend/src@4b64b3f2634c 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/+/master/autoroll/README.md Bug: chromium:1006759,chromium:1042269,chromium:1043142,chromium:848823 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: If4b35bb2f4d5cad4b3e49a6d68f31170bde78ff0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015528Reviewed-by:
-
Stephen Nusko authored
NOTRY=true TBR=crouleau@chromium.org CC=sadrul@chromium.org,vmiura@chromium.org BUG=1044962 Change-Id: I71932bea0c6fe2814a5a566fcb19752ea9af2e53 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016646Reviewed-by:
-
Nikita Podguzov authored
Actual usage will be introduced in follow-up CL. TBR=battre@chromium.org Bug: 996785 Change-Id: Iba78e17959c27ed7dee1618b191690559346c066 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2002622Reviewed-by:
Sergey Poromov <poromov@chromium.org> Reviewed-by:
Dominic Battré <battre@chromium.org> Reviewed-by:
Sean Kau <skau@chromium.org> Commit-Queue: Nikita Podguzov <nikitapodguzov@chromium.org> Cr-Commit-Position: refs/heads/master@{#734440}
-
Rob Buis authored
Implement the <mspace> element [1] by adding support for it on the DOM and adding a layout algorithm for it. Also map attribute width to the width property and map height and depth to the height property using calc(). Bug: 6606 [1] https://mathml-refresh.github.io/mathml-core/#space-mspace Change-Id: Ic52832edd6a73d896c2d42041756ded5d50fcb95 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1936251 Commit-Queue: Rob Buis <rbuis@igalia.com> Reviewed-by:
Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by:
Frédéric Wang <fwang@igalia.com> Reviewed-by:
Morten Stenshorne <mstensho@chromium.org> Reviewed-by:
Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#734439}
-
Askar Aitzhan authored
The results of rolling out to 1% Stable: * PolicyInvalidationsRegistrationResult: https://screenshot.googleplex.com/pnbpqVwsRU9 * DevicePolicyInvalidations: https://screenshot.googleplex.com/MEWsE7RkOwk * DevicePolicyRefresh2: https://screenshot.googleplex.com/VWuHQvxsKx3 * PolicyInvalidations: https://screenshot.googleplex.com/EqoY7uBTVO7 * PolicyRefresh2: https://screenshot.googleplex.com/qEXcoLEXziK The results are as expected. The issue regarding Klopf-Klopf devices not receiving remote commands b/141327786 was confirmed that it was not caused by "Invalidation Service Migration". Bug: 939039 Change-Id: Idd37c358e7bc9d4a69e204c1a91e6a44c376675b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2014966Reviewed-by:Marc Treib <treib@chromium.org> Commit-Queue: Askar Aitzhan <askaraitzhan@google.com> Cr-Commit-Position: refs/heads/master@{#734438}
-
Benoît Lizé authored
Local testing shows that async scripts miss more often in the memory cache. Add a histogram to check whether this is the case. As a consequence, extend the expiration date of the related histograms, and add a "team" owner for these histograms. Bug: 1043679 Change-Id: Ia2bf6145d864470f6c964938aba851ed94ca773e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010847Reviewed-by:
Alex Ilin <alexilin@chromium.org> Reviewed-by:
Hiroshige Hayashizaki <hiroshige@chromium.org> Commit-Queue: Benoit L <lizeb@chromium.org> Cr-Commit-Position: refs/heads/master@{#734437}
-
Alex Ilin authored
This CL disables flaky VrBrowserTransitionTest#testIncognitoLearnMoreTriggersDoff test. TBR=bsheedy@chromium.org Bug: 1032769 Change-Id: I3675e75c1b3573acb06b56b786f75308cb9f97c3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015027Reviewed-by:
-
Stephen Nusko authored
Both of these are failing: system_health.memory_mobile/background:tools:gmail:2019 system_health.common_mobile/background:tools:gmail:2019 NOTRY=true TBR=crouleau@chromium.org CC=pasko@chromium.org,crouleau@chromium.org,chrome-android-perf-status@chromium.org,charliea@chromium.org,sullivan@chromium.org,tdresser@chromium.org,chrome-speed-metrics-dev@chromium.org BUG=1044953 Change-Id: I631729ec70d5a1ebe40c4b31c16b0c71d364ed57 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2014911Reviewed-by:
-
Stephen Nusko authored
Both of these are failing: system_health.memory_mobile/load:games:bubbles system_health.common_mobile/load:games:bubbles NOTRY=true TBR=crouleau@chromium.org CC=pasko@chromium.org,crouleau@chromium.org,chrome-android-perf-status@chromium.org,charliea@chromium.org,sullivan@chromium.org,tdresser@chromium.org,chrome-speed-metrics-dev@chromium.org BUG=1044953 Change-Id: I2fb571bd8f08cdcb4e6615c0af23c40609973237 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015086Reviewed-by:
-
Rushan Suleymanov authored
Generate unique identifier for each message and store it in a new field in specifics. This id is used by bridge as storage key and client tag. Changing tag numbers in the proto is fine because it is not used anywhere yet. Bug: 1034932 Change-Id: I5c79fdb70d8897ac300e49e98e78760b8394e52c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015024 Commit-Queue: Rushan Suleymanov <rushans@google.com> Reviewed-by:
Alex Chau <alexchau@chromium.org> Reviewed-by:
vitaliii <vitaliii@chromium.org> Cr-Commit-Position: refs/heads/master@{#734433}
-
Robbie Gibson authored
Bug: 1006215 Change-Id: I3844da9d76e7778c028482e8394a27a61ab0ad47 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016632Reviewed-by:
Javier Ernesto Flores Robles <javierrobles@chromium.org> Commit-Queue: Robbie Gibson <rkgibson@google.com> Cr-Commit-Position: refs/heads/master@{#734432}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/313d98ee7b49..5cddf9e222f6 Created with: gclient setdep -r src-internal@5cddf9e222f6 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 jbudorick@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/+/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: None Tbr: jbudorick@google.com Change-Id: I8289650be3e1bd36ffe6f53ed1ac4da0834eacb4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015527Reviewed-by:
-
Torne (Richard Coles) authored
A number of apps hit cases where they're sure they only have one process but the data dir lock can't be acquired, and there appears to be a possible issue in Android where a process might be restarted in a race with a previous instance being killed under rare conditions. Retry acquiring the lock a few times to allow for the possible race, and write out the process info of the process holding the lock to the file so that if we still fail after retrying, we can show more helpful information. Log a histogram for how many retries it required, so we can validate whether this is helping. Move the data directory locking code into its own class, as it's now more complex and its internal details aren't relevant to the rest of AwBrowserProcess. Bug: 558377 Change-Id: I75a13262138856b58febbcec3203f9984269b215 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1918160 Commit-Queue: Richard Coles <torne@chromium.org> Reviewed-by:
Tobias Sargeant <tobiasjs@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Cr-Commit-Position: refs/heads/master@{#734430}
-
Peter Marshall authored
This is a reland of a5afd47a Original change's description: > DevTools: Block SIGPROF during CPU throttling > > The V8 CPU profiler schedules SIGPROF signals. It is very likely that > the signal handler for these will run while the throttling signal > handler is already running. V8 can't properly read the stack when > there is already a signal handler present. > > Fix this by using sa_mask to block V8's SIGPROFs while the > throttling handler is running. This makes more sense overall as well. > Our CPU samples would be skewed by whichever stacks we encounter > during throttling pauses. > > Bug: 1027242 > Change-Id: I80e856ce1e7b4744a9af7e36c2022b6d8610cf60 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2012280 > Reviewed-by: Sigurd Schneider <sigurds@chromium.org> > Reviewed-by: Sami Kyöstilä <skyostil@chromium.org> > Commit-Queue: Peter Marshall <petermarshall@chromium.org> > Cr-Commit-Position: refs/heads/master@{#733592} Bug: 1027242 Change-Id: I2c5c1e462f9f6f16739e773dda112bacd8b354f9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2014404 Commit-Queue: Peter Marshall <petermarshall@chromium.org> Reviewed-by:
Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#734429}
-
