- 30 Jul, 2019 40 commits
-
-
Charlie Andrews authored
There are existing POSIX implementations for these methods in stack_sampler_posix.cc. We now use stack_sampler_android.cc on Android and stack_sampler_posix.cc on all other POSIX platforms. Note that there's an existing StackSamplerAndroid that exists in the tracing namespace. However, that implementation is only used for the "cpu_profiler" tracing category, whereas this implementation will be used for stack sampled metrics. Once this new Android profiler is sufficiently complete, it will also be used for tracing. This stack_sampler_android.cc defers to StackSamplerImpl for its core logic (also used by the Windows and Mac sampling profiler implementations), whereas tracing's stack_sampler_android doesn't use StackSamplerImpl and implements its own core logic. R=wittman@chromium.org,gab@chromium.org Bug: 988574 Change-Id: Ia1f20a22ac1421ff02d4beecff4beb6b7a0e065f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1727230Reviewed-by:
Gabriel Charette <gab@chromium.org> Reviewed-by:
Mike Wittman <wittman@chromium.org> Commit-Queue: Charlie Andrews <charliea@chromium.org> Cr-Commit-Position: refs/heads/master@{#682446}
-
danakj authored
Without using this, the Platform object is not replaced when the test class shuts down. This makes the next test to run have a Platform pointer to a deleted object, and causes a crash if any future tests in the shard will try to use the Platform. R=avi@chromium.org, pdr@chromium.org Bug: 419087, 745091 Change-Id: I09145e6a6a8ad1b0b1f9d0d77f04dc147a90972a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726730Reviewed-by:
Avi Drissman <avi@chromium.org> Reviewed-by:
Philip Rogers <pdr@chromium.org> Commit-Queue: danakj <danakj@chromium.org> Cr-Commit-Position: refs/heads/master@{#682445}
-
Kyle Milka authored
Remove the ability for a selected tile to be clicked again and deselected. When the picker is opened pre-select the tile corresponding to the current page background. http://go/scrcast/NjMxOTc2MzM0MzAxNTkzNnw1MTAyN2QxOC1iYg Bug: 984353 Change-Id: I02081460e1bdc2b7679a704b01a6e91ca531a939 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1719809Reviewed-by:
Kristi Park <kristipark@chromium.org> Commit-Queue: Kyle Milka <kmilka@chromium.org> Cr-Commit-Position: refs/heads/master@{#682444}
-
Andrei Polushin authored
When there are multiple switches having the same key within the argv array, CommandLine constructor only puts one of them within the parsed-out switches map. On the other hand, CommandLine::RemoveSwitch removes a switch from the switches map. It should also drop all the switches having the same key from the argv array. BUG=957138 TEST=base_unittests --gtest_filter="CommandLineTest.*" Change-Id: Ia4cf08bc497d4d53e0213879df71f85d945a4fec Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1724079 Auto-Submit: Andrei Polushin <anpol@yandex-team.ru> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Commit-Queue: Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#682443}
-
Ryan Sleevi authored
These three files were omitted from the move due to an out-of-date branch. Finish moving them so that the directory goes away. Bug: 987648 Change-Id: Ib4fb890d01dd9ad0ed5a85e68c0bfc6988394db1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1727089 Commit-Queue: Ryan Sleevi <rsleevi@chromium.org> Commit-Queue: Matt Menke <mmenke@chromium.org> Auto-Submit: Ryan Sleevi <rsleevi@chromium.org> Reviewed-by:
Matt Menke <mmenke@chromium.org> Cr-Commit-Position: refs/heads/master@{#682442}
-
Sean Gilhuly authored
Following a recent roll of the macOS SDK to 10.14, the tests FaceDetectionImplMacTest.ScanOneFace/3 and /4 are now detecting four faces in an image of the four Beatles, where they were previously detecting three. Update the test expectations if the macOS version is at least 10.14, otherwise use the old expectations. Bug: 988495 Change-Id: I3e5fc16d6f0639ad1fb86dae7189c6125e95f7ca Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726309Reviewed-by:
Reilly Grant <reillyg@chromium.org> Commit-Queue: Sean Gilhuly <sgilhuly@chromium.org> Cr-Commit-Position: refs/heads/master@{#682441}
-
Daniel Cheng authored
This reverts commit fb0f9e39. Reason for revert: breaks rendering on https://svelte.dev/tutorial/basics Original change's description: > location.hash = '' should always result in an empty fragment, not no-fragment > > So far in |setHash|, old fragment identifier and new fragment identifier are > compared ignoring nullity. > > When fragment has never been set, |old_fragment_identifier| is null. > In this situation, |location.hash = ''| is called, > |new_fragment_identifier| is not null empty value. > |EqualIgnoringNullity| treats these as the same, |setHash| does nothing. > > So, this patch compare old and new fragment by == operator > not |EqualIgnoringNullity|. > > Bug: 615300 > Change-Id: Id509bc5066eeee83236ecb4ee816ecb90540a260 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1647298 > Commit-Queue: Daniel Cheng <dcheng@chromium.org> > Reviewed-by: Daniel Cheng <dcheng@chromium.org> > Cr-Commit-Position: refs/heads/master@{#670795} TBR=dcheng@chromium.org,japhet@chromium.org,bluewhale.marc@gmail.com # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 615300 Change-Id: I6e47d0d1711b197c6e8e35af7dc43e67a6cb4ebb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726953Reviewed-by:
-
Brandon Goddard authored
This change adds the headers for datagrids into the first filler row, which is empty, so that the column header information can be available to screen readers when navigating the datagrid. This data was previously unavailable since dataGrid headers are in a separate table from the data table. Before: https://imgur.com/aenXMyL After: https://imgur.com/XZliDFH Bug: 963183 Change-Id: I7ba1e47e26d821aad9da19b802c48d781a680532 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1663368 Commit-Queue: Brandon Goddard <brgoddar@microsoft.com> Reviewed-by:
Joel Einbinder <einbinder@chromium.org> Reviewed-by:
Alice Boxhall <aboxhall@chromium.org> Cr-Commit-Position: refs/heads/master@{#682439}
-
Chris Sharp authored
Change-Id: I71975e2b88bf5178febd03cc079fb549814b8091 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1727209 Commit-Queue: Chris Sharp <csharp@chromium.org> Commit-Queue: proberge <proberge@chromium.org> Auto-Submit: Chris Sharp <csharp@chromium.org> Reviewed-by:
proberge <proberge@chromium.org> Cr-Commit-Position: refs/heads/master@{#682438}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/d5acde64a3a5..6ce7935230e8 git log d5acde64a3a5..6ce7935230e8 --date=short --no-merges --format='%ad %ae %s' 2019-07-30 treehugger-gerrit@google.com Merge "traced: Send empty OnTraceData response if tracing not started" Created with: gclient setdep -r src/third_party/perfetto@6ce7935230e8 The AutoRoll server is located here: https://autoroll.skia.org/r/perfetto-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=perfetto-bugs@google.com Bug: None Change-Id: Ifc4696eef53eb546d992387e16865614b7f41034 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726811Reviewed-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@{#682437}
-
Gabriel Charette authored
This will make it possible to define a default move-assign/construct on classes that use a THREAD/SEQUENCE_CHECKER.. e.g. https://chromium-review.googlesource.com/c/chromium/src/+/1693302 R=fdoray@chromium.org Bug: 946657 Change-Id: Ie2b40984b664fa1dcdcdd093ab546625db685430 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1696845 Commit-Queue: Gabriel Charette <gab@chromium.org> Commit-Queue: kylechar <kylechar@chromium.org> Reviewed-by:
kylechar <kylechar@chromium.org> Auto-Submit: Gabriel Charette <gab@chromium.org> Cr-Commit-Position: refs/heads/master@{#682436}
-
Henrik Grunell authored
Code using it was removed in https://chromium-review.googlesource.com/c/chromium/src/+/1697624. Bug: 879133, 975502 Change-Id: I92c26ace2aa5b0f6c60982e8c7c2ee1bd34f4946 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1724681 Auto-Submit: Henrik Grunell <grunell@chromium.org> Reviewed-by:
Armando Miraglia <armax@chromium.org> Reviewed-by:
Jesse Doherty <jwd@chromium.org> Commit-Queue: Jesse Doherty <jwd@chromium.org> Cr-Commit-Position: refs/heads/master@{#682435}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/8cbf662b296a..95d8ceb955cc git log 8cbf662b296a..95d8ceb955cc --date=short --no-merges --format='%ad %ae %s' 2019-07-30 csmartdalton@google.com Add GrMipMapsStatus to GrTextureProxy 2019-07-30 robertphillips@google.com Propagate GrRenderable flag to GrCaps::getBackendFormatFromColorType 2019-07-30 mtklein@google.com more unit tests 2019-07-30 bsalomon@google.com Lift GrRenderTarget::transferFrom to GrSurfaceContext. 2019-07-30 halcanary@google.com editor: try to fix moltenvk bots Created with: gclient setdep -r src/third_party/skia@95d8ceb955cc The AutoRoll server is located here: https://autoroll.skia.org/r/skia-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel TBR=benjaminwagner@google.com Bug: None Change-Id: I8504a8e006de94b784bd27bd2def1e678e01bcb9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726891Reviewed-by:
-
Patrick Monette authored
Bug: 986926 Change-Id: I863c3490217de5417e00ec528d9eb17e78021740 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1715967 Commit-Queue: Patrick Monette <pmonette@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Reviewed-by:
Chris Sharp <csharp@chromium.org> Cr-Commit-Position: refs/heads/master@{#682433}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/2613cdba80a3..8b2dfa0fc657 git log 2613cdba80a3..8b2dfa0fc657 --date=short --no-merges --format='%ad %ae %s' 2019-07-30 geofflang@chromium.org GL: Implement EXT_external_objects 2019-07-30 geofflang@chromium.org GL: Load external object extension entry points. 2019-07-30 geofflang@chromium.org Support the SearchType argument for loading libraries with posix. Created with: gclient setdep -r src/third_party/angle@8b2dfa0fc657 The AutoRoll server is located here: https://autoroll.skia.org/r/angle-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. 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_optional_gpu_tests_rel TBR=geofflang@google.com Bug: chromium:982294 Change-Id: I3a7463d36fd4701b21b533aa262736a5de266600 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726894Reviewed-by:
-
Kevin Marshall authored
Allows the Agent to control some runtime aspects of Cast applications. Bug: 953796,953958 Change-Id: Ie168cfa36d975882223cd2c95f7d95dafd96afbd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1666452 Commit-Queue: Kevin Marshall <kmarshall@chromium.org> Reviewed-by:
Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#682431}
-
Justin Cohen authored
Bug: 976259 Change-Id: I6f487fd16096209478be37be0bb8aa9e7ea859c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726793 Auto-Submit: Justin Cohen <justincohen@chromium.org> Commit-Queue: Peter Lee <pkl@chromium.org> Reviewed-by:
Peter Lee <pkl@chromium.org> Cr-Commit-Position: refs/heads/master@{#682430}
-
Nathan Zabriskie authored
This reverts commit b5f58b9a. Reason for revert: Makes conformance/canvas/buffer-offscreen-test.html fail consistently on Win 7 FYI Debug AMD. The failures occured when Surfaces were destroyed before Display::DidReceivePresentationFeedback() was called. This prevented CompositorFrameSinkSupport from clearing the appropriate entry in |received_compositor_frame_times_|. The issue was resolved by changing Surface::PresentationHelper to call SurfaceClient::OnSurfacePresented() directly instead of a wrapper function on the Surface. Original change's description: > Add Viz timestamps to FrameTimingDetails > > This CL starts adding more timestamps to the new FrameTimingDetails that > is sent back to Viz clients after a frame is presented. Eventually these > timings will be used to determine abnormally long stages of the > rendering pipeline in the case of missed frames. This CL simply adds > the timestamp of when the display compositor receives a submitted > compositor frame and when it begins the DrawAndSwap. > > Bug: 963780 > Change-Id: I3ca4715689401d0544c7efb17a9a096e2534131d > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1655738 > Commit-Queue: Nathan Zabriskie <nazabris@microsoft.com> > Reviewed-by: Ken Buchanan <kenrb@chromium.org> > Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org> > Cr-Commit-Position: refs/heads/master@{#676207} Bug: 963780 Change-Id: I834f171d7735eb9942ec6a117e186a313fb5f650 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1705158 Commit-Queue: Nathan Zabriskie <nazabris@microsoft.com> Reviewed-by:
Ken Buchanan <kenrb@chromium.org> Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Cr-Commit-Position: refs/heads/master@{#682429}
-
Chase Phillips authored
As part of cleanup from CL https://crrev.com/c/1626660, this CL moves creation of CursorImpl into IndexedDBDispatcherHost by refactoring AddCursorBinding into CreateCursorBinding. As a result, the OpenCursor calling path no longer needs to pass the origin and sequenced task runner into the OpenCursorOperation task and ownership of CursorImpl and the mojo binding steps is made simpler. Bug: 988868 Change-Id: Iab0be1d24d98fc6b0088d01c67c1b778c5c13318 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1725318Reviewed-by:
Daniel Murphy <dmurph@chromium.org> Commit-Queue: Chase Phillips <cmp@chromium.org> Cr-Commit-Position: refs/heads/master@{#682428}
-
Mounir Lamouri authored
Bug: None Change-Id: I0e37df2a199df5cd5e6a3bd42270383133638a62 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726653Reviewed-by:
Bruce Dawson <brucedawson@chromium.org> Commit-Queue: Mounir Lamouri <mlamouri@chromium.org> Cr-Commit-Position: refs/heads/master@{#682427}
-
Henrique Nakashima authored
BEST_EFFORT does not work in background (crbug.com/988604). Bug: 988604, 984559 Change-Id: I99f3793d9bb949570cd78c9f969b05fea138aed7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726870 Commit-Queue: Henrique Nakashima <hnakashima@chromium.org> Commit-Queue: Mohamed Heikal <mheikal@chromium.org> Reviewed-by:
Mohamed Heikal <mheikal@chromium.org> Cr-Commit-Position: refs/heads/master@{#682426}
-
Tibor Goldschwendt authored
Bug: 955494 Change-Id: I01bd565e37f354e1ddb7ba74a318ede9a3a7ed9d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1717779 Auto-Submit: Tibor Goldschwendt <tiborg@chromium.org> Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Reviewed-by:
Samuel Huang <huangs@chromium.org> Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org> Cr-Commit-Position: refs/heads/master@{#682425}
-
Mounir Lamouri authored
Bug: None Change-Id: Id05cede1d4cf7f8ff3202c531575868c8b56265b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726934Reviewed-by:
-
Ian Kilpatrick authored
A cleanup of the cleanup! Upon further inspection the node parameter isn't strictly needed anymore. This has one slight behaviour change, which I think was incorrect: flexItem.computedStyleMap().get('min-height') == 0px now. This is more correct I believe as computedStyleMap should act as if a box isn't attached, which is the same behaviour if elem wasn't attached to the document. Change-Id: I4522d1f591cdfe7ec88522f6da49be599d2db4ea Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1716089 Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by:Xida Chen <xidachen@chromium.org> Reviewed-by:
Anders Hartvoll Ruud <andruud@chromium.org> Reviewed-by:
Mike West <mkwst@chromium.org> Reviewed-by:
Mounir Lamouri <mlamouri@chromium.org> Auto-Submit: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#682423}
-
Michael Achenbach authored
This is a no-op on iOS, since there the system or recipe side sdk is used. Bug: chromium:986701 Change-Id: I1daffa748b0dadd074a9c8ca2b756416c197ca1b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1725914Reviewed-by:
Erik Chen <erikchen@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#682422}
-
Ian Prest authored
This change sets the kPreviousOnLineId and kNextOnLineId attributes on PDF content if two text runs are determined to be on the same line. This is determined using a threshold, similar to the current paragraph detection. Any delta-y greater than 1.2x the median line spacing is considered a new paragraph (unchanged), and now any delta-y greater than 0.8x the median line spacing is considered a new line. Bug: 985604 Change-Id: If821bb6e5faadf244417f083d439a9460157f48e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1709808Reviewed-by:
Lei Zhang <thestig@chromium.org> Reviewed-by:
Kevin Babbitt <kbabbitt@microsoft.com> Commit-Queue: Ian Prest <iapres@microsoft.com> Cr-Commit-Position: refs/heads/master@{#682421}
-
Ionel Popescu authored
This CL includes the following changes: - calendar_picker_refresh.css was added as a way to extend the current style used for date popup - calendarPicker.js was changed: - to support different sizes for cells - to provide different icons for forward, back month buttons - todayButton was moved to a different position - locale_win | icu | mac to change the label used for weekdays to the shortest one provided by each platform Added tests to validate the new UI for input type="date". Although the current change affects other types (datetime-local, week, month) this change is the first of a series of changes which will update the popup UI for all these types and tests will be added for each type. Bug: 988155 Change-Id: Ibfbddd9f523f4adad79b6af2520989c3980bc18c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1721842 Commit-Queue: Ionel Popescu <iopopesc@microsoft.com> Reviewed-by:Mason Freed <masonfreed@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#682420}
-
Ren-Pei Zeng authored
This CL extends MJDA interface to support DMA-buf backed VideoFrame with pixel format not limited to I420, and focuses on the implementation in VAAPI backend. In the VA pipeline, the input JPEG image is first decoded into an internal VASurface, and then Video Processing Pipeline (VPP) is used to convert it into target VASurface, which is imported from client's VideoFrame. For cases VPP doesn't support the conversion, it fallbacks to get VAImage from decoded surface and do software conversion. The pixel formats supported by VPP can be queried by vaQuerySurfaceAttribs(), but the internal surface format from a JPEG decoding is hidden and may not be supported (e.g., Mesa driver's VPP doesn't support conversion from a decoded 4:2:2 JPEG). To work around this, VaapiWrapper::IsJpegDecodeVppSupportedSurfaceFourCC() is deduced from some observations to filter unsupported cases. V4L2 backend is not implemented in this CL. It will return error if the output frame given is backed by DMA-bufs. The JDA unittest is extended to test with DMA-buf and shared memory output buffers. CQ-DEPEND=CL:1645712 Bug: b:120057531 Test: jpeg_decode_accelerator_unittest Change-Id: I5a9a46f7b7e9b142c7dfbf59acd0125f90c70288 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1558746Reviewed-by:
Ricky Liang <jcliang@chromium.org> Reviewed-by:
Steven Holte <holte@chromium.org> Reviewed-by:
Daniele Castagna <dcastagna@chromium.org> Reviewed-by:
Andres Calderon Jaramillo <andrescj@chromium.org> Commit-Queue: Ren-Pei Zeng <kamesan@chromium.org> Cr-Commit-Position: refs/heads/master@{#682419}
-
Daniel Rubery authored
A few Download metrics expired in M77, and we don't have any near-term plans for these metrics, so remove them. Bug: 975143 Change-Id: I63c480286e271c668c57bb7d65a8d2581ae278af Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1724867 Auto-Submit: Daniel Rubery <drubery@chromium.org> Reviewed-by:
Min Qin <qinmin@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Commit-Queue: Ilya Sherman <isherman@chromium.org> Cr-Commit-Position: refs/heads/master@{#682418}
-
Sergey Ulanov authored
By default media demuxer buffers 150MB of video and 12MB of audio. This may be to much for some Fuchsia devices. Use low values of 30MB and 2MB. Bug: ZX-4768 Change-Id: I084f85dcc92fa54c56fd06ab8270f4fb73762410 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1725240 Auto-Submit: Sergey Ulanov <sergeyu@chromium.org> Reviewed-by:
Dan Sanders <sandersd@chromium.org> Commit-Queue: Sergey Ulanov <sergeyu@chromium.org> Cr-Commit-Position: refs/heads/master@{#682417}
-
Scott Violet authored
Specifically Memory.Renderer.PrivateMemoryFootprint. This refactors existing code in hopes of sharing names and some portions of the logic. This doesn't include Memory.Browser as it's not really under our control (I'm starting an email thread on this one). Logging is only enabled for the non-single process case. This patch is exactly the same as the first patch. I fixed the reason that lead to the revert here: https://chromium-review.googlesource.com/c/chromium/src/+/1716584 BUG=981102 TEST=covered by integration tests TBR=bcwhite@chromium.org, changwan@chromium.org, chrisha@chromium.org Change-Id: Iabb1193481600c208fe56207aaef01d1fd3b9401 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726410Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Chris Hamilton <chrisha@chromium.org> Reviewed-by:
Brian White <bcwhite@chromium.org> Reviewed-by:
Changwan Ryu <changwan@chromium.org> Commit-Queue: Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#682416}
-
Mohsen Izadi authored
While adding a test to //ui/compositor/layer_unittes.cc, I noticed that there are a bunch of factory functions that return raw pointers that the call sites wrap in unique_ptr's. Changed them to return unique_ptr's to make ownership more clear. BUG=none Change-Id: I7f54855265fadc7692c7ca7e40937642ed809f00 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726897Reviewed-by:
danakj <danakj@chromium.org> Commit-Queue: Mohsen Izadi <mohsen@chromium.org> Cr-Commit-Position: refs/heads/master@{#682415}
-
Philip Jägenstedt authored
The ones in the past that remain unfortunately still have deprecations referencing them, which should be fixed. This only makes it clearer. Change-Id: I7ec07fa5a1e543739851c59e0770b99fc121b908 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1724645 Auto-Submit: Philip Jägenstedt <foolip@chromium.org> Reviewed-by:
Ian Clelland <iclelland@chromium.org> Commit-Queue: Ian Clelland <iclelland@chromium.org> Cr-Commit-Position: refs/heads/master@{#682414}
-
John Abd-El-Malek authored
Bug: 934009, 791049 Change-Id: Id0fcc731e78511f3b8f54105b4fbfec5ccd8a06e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1727029Reviewed-by:
Clark DuVall <cduvall@chromium.org> Reviewed-by:
Robert Sesek <rsesek@chromium.org> Commit-Queue: John Abd-El-Malek <jam@chromium.org> Cr-Commit-Position: refs/heads/master@{#682413}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/1157607f2f54..3b361d1e1281 git log 1157607f2f54..3b361d1e1281 --date=short --no-merges --format='%ad %ae %s' 2019-07-30 jazbel@chromium.org usergroup_baseline: Expect cfm-monitor in video. Created with: gclient setdep -r src/third_party/chromite@3b361d1e1281 The AutoRoll server is located here: https://autoroll.skia.org/r/chromite-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:chromeos-kevin-rel TBR=chrome-os-gardeners@google.com Bug: None Change-Id: I697e0cce45db5bd50a4bf1a397240bb4928e3a0b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726890Reviewed-by:
-
chromium-autoroll authored
The AutoRoll server is located here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast TBR=cr-fuchsia+bot@chromium.org Change-Id: Ia99207b6155c08bdc6f24e2f719501f4a7386c20 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726293 Commit-Queue: Wez <wez@chromium.org> Reviewed-by:
-
Carlos IL authored
Mixed content autoupgrade experiment is still ongoing, so the histograms are still needed. Bug: 893647 Change-Id: I893d443c7b43970eb4d91124dd07c94541811ad5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726311 Auto-Submit: Carlos IL <carlosil@chromium.org> Commit-Queue: Ilya Sherman <isherman@chromium.org> Reviewed-by:
-
Ben Kelly authored
When we load the cache_storage index we try to determine if its fresh or stale by comparing its timestamp against the timestamp of the various simple disk_cache directories. Both cache_storage and simple disk_cache write their index files out using a delay. The cache_storage delay is 5 seconds and the simple disk_cache delay is 20 seconds. This means that the simple disk_cache index is always written last and as a result the cache_storage index is almost always considered stale. This CL fix this by extending the cache_storage delay to match the simple disk_cache delay. It also implements a shorter delay on android when in the background like simple disk_cache uses to avoid losing data when the app is killed by the operating system. Finally, the CL also now properly flushes the index to disk if there is a pending write when the cache_storage subsystem is torn down. Over time this should cause ServiceWorkerCache.UsedIndexFileSize to show more cases where the index file is used to provide the size. Bug: 988001 Change-Id: Idaa09b956edcfa9e70ac1fdb9b43adcd73ec0508 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1721389 Commit-Queue: Daniel Murphy <dmurph@chromium.org> Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/da76f1d1887d..cde7deb536fa Created with: gclient setdep -r src-internal@cde7deb536fa The AutoRoll server is located here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome TBR=jbudorick@google.com Bug: chromium:None,chromium:None Change-Id: I5b72f6d006aa9eae2f8d6b26bae3c56027454143 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726892Reviewed-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@{#682408}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/e73fe02a406e..2568b37b25f5 git log e73fe02a406e..2568b37b25f5 --date=short --no-merges --format='%ad %ae %s' 2019-07-30 rmhasan@google.com [Telemetry] Create an IsLowEnd function for the AndroidPlatformBackend class Created with: gclient setdep -r src/third_party/catapult@2568b37b25f5 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. 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_optional_gpu_tests_rel TBR=simonhatch@google.com Bug: chromium:973936 Change-Id: I6bc51cc89472e9dca0c1808862c8ba8229fb50e2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726809Reviewed-by:
-
