- 19 Aug, 2018 16 commits
-
-
Nico Weber authored
This reverts commit 740a6c4c. Reason for revert: views_unittests WidgetTest.FullscreenStatePropagated , WidgetTest.FullscreenStatePropagated_DesktopWidget consistently started failing on 10.10 (other versions seem happy): https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Mac10.10%20Tests/34348 Original change's description: > RemoteMacViews: Re-separate test code > > This removes parts of crrev.com/583350, preserving the following > - explicitly require that NSWindows be NativeWidgetMacNSWindow > - return a scoped_nsobject from CreateNSWindow, and remove requirement > of autoreleasing the result, to clarify lifetimes > > This removes the ability to create an NSWindow in the AppShim process > for now. That will be re-added later. > > Bug: 859152 > Change-Id: Ife70a91ac9557f2ec7a488a8714f907eaecea0e3 > Reviewed-on: https://chromium-review.googlesource.com/1177276 > Commit-Queue: ccameron <ccameron@chromium.org> > Reviewed-by: Trent Apted <tapted@chromium.org> > Cr-Commit-Position: refs/heads/master@{#584323} TBR=tapted@chromium.org,ccameron@chromium.org Change-Id: I9c16deb13126c51171bdd180200025cbcf808a03 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 859152 Reviewed-on: https://chromium-review.googlesource.com/1180762Reviewed-by:
Nico Weber <thakis@chromium.org> Commit-Queue: Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#584340}
-
Nico Weber authored
This reverts commit 5f99a2c0. Reason for revert: WebDialogBrowserTest.SizeWindow fails on max 10.11, 10.12 (10.10 and 10.13 seem happy): https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Mac10.11%20Tests/28636 https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Mac10.12%20Tests/14984 Original change's description: > RemoteMacViews: Remove browser dependencies of SetBounds > > The function BridgedNativeWidget::SetBounds calls back into the > NativeWidgetMac to determine > - the minimum content size > - if the widget's position should be relative to the parent or the > screen (and the offset to do that computation) > - if the widget is a modal sheet > This call will eventually be running in the app shim process, where > these values will not be available (without adding a synchronous IPC). > > Change NativeWidgetMac::SetBounds to call BridgedNativeWidgetHostImpl:: > SetBounds, and have that function pre-compute the required parameters, > - minimum content size > - offset necessary to be applied to compensate for position being > relative to the parent or the screen > - (but not if the widget is a modal sheet, that's coming later) > and pass these as parameters to BridgedNativeWidget::SetBounds. > > Split out the SetBounds calls made during initialization from > being within BridgedNativeWidget::Init to being made by its caller, > BridgedNativeWidgetHostImpl::InitWindow, to allow the additional > parameters to be passed in. > > Bug: 859152 > Change-Id: I2f33ab08f60d2ed1bc3b6af5ecf3402e3715ffd4 > Reviewed-on: https://chromium-review.googlesource.com/1178813 > Commit-Queue: ccameron <ccameron@chromium.org> > Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org> > Cr-Commit-Position: refs/heads/master@{#584327} TBR=ellyjones@chromium.org,ccameron@chromium.org Change-Id: I1300db812416881fb539b586e7d7fab2597d60c5 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 859152 Reviewed-on: https://chromium-review.googlesource.com/1180761Reviewed-by:
Nico Weber <thakis@chromium.org> Commit-Queue: Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#584339}
-
Nico Weber authored
One recently re-enabled test fails, so to be able run the whole suite, also: Revert "Reland "[Sync:USS] Enable more two client bookmarks integration tests"" This reverts commit f846b651. Reason for revert: One of the tests fails on win/asan, https://crbug.com/875239 Original change's description: > Reland "[Sync:USS] Enable more two client bookmarks integration tests" > > This is a reland of 94d8037b > > Original change's description: > > [Sync:USS] Enable more two client bookmarks integration tests > > > > This CL enables more integration tests for bookmarks to run > > against USS archiecture. > > > > > > Bug: 516866 > > Change-Id: Icece27bdf1b2070ca72d667b1a70e623c45c315f > > Reviewed-on: https://chromium-review.googlesource.com/1158691 > > Commit-Queue: Mohamed Amir Yosef <mamir@chromium.org> > > Reviewed-by: Mikel Astiz <mastiz@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#580434} > > Bug: 516866 > Change-Id: Ia922ab75b92c013cc2e06cb3ec5a549875390316 > Reviewed-on: https://chromium-review.googlesource.com/1161882 > Reviewed-by: Mikel Astiz <mastiz@chromium.org> > Commit-Queue: Mohamed Amir Yosef <mamir@chromium.org> > Cr-Commit-Position: refs/heads/master@{#580499} TBR=mastiz@chromium.org,mamir@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 516866, 875239 Change-Id: I85e49dbfd4e6c2aba675854efb42c4a87d3243b8 Reviewed-on: https://chromium-review.googlesource.com/1180661 Commit-Queue: Nico Weber <thakis@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#584338}
-
erikchen authored
All the logic was hooked up for calculation of the metric but the UMA metric itself was missing. Bug: 859155 Change-Id: Iab4e3c726e2627d1f1325ee30bebd1ee9eae6f76 Reviewed-on: https://chromium-review.googlesource.com/1179985Reviewed-by:
Ilya Sherman <isherman@chromium.org> Reviewed-by:
Timothy Dresser <tdresser@chromium.org> Commit-Queue: Erik Chen <erikchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#584337}
-
skia-chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/ae7229480cbe..fb65db10aa31 git log ae7229480cbe..fb65db10aa31 --date=short --no-merges --format='%ad %ae %s' 2018-08-19 reed@google.com show inflextion on cubic Created with: gclient setdep -r src/third_party/skia@fb65db10aa31 The AutoRoll server is located here: https://autoroll.skia.org 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=master.tryserver.blink:linux_trusty_blink_rel;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=fmalita@chromium.org Change-Id: I6bccee3e00ab11f2ed6be2420b524e7d0a9246b6 Reviewed-on: https://chromium-review.googlesource.com/1180723Reviewed-by:
skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#584336}
-
Emil A Eklund authored
The methods for computing start and end index for a shape result compute the values on demand, while not too expensive these methods are called a lot during both layout and paint. By pre-computing the values text paint performance is improved by about 10% for LayoutNG & about 2% for legacy. Bug: 714962 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng Change-Id: Ib652b947d6cc670e657d72d753e96ecb4e2aa85d Reviewed-on: https://chromium-review.googlesource.com/1176202 Commit-Queue: Emil A Eklund <eae@chromium.org> Reviewed-by:
Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#584335}
-
skia-chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/5cc10c8cd6db..ae7229480cbe git log 5cc10c8cd6db..ae7229480cbe --date=short --no-merges --format='%ad %ae %s' 2018-08-19 skia-recreate-skps@skia-swarming-bots.iam.gserviceaccount.com Update SKP version Created with: gclient setdep -r src/third_party/skia@ae7229480cbe The AutoRoll server is located here: https://autoroll.skia.org 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=master.tryserver.blink:linux_trusty_blink_rel;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=fmalita@chromium.org Change-Id: I8ec3f5bcb57e1a90af908c53cc2a70ca54c95a20 Reviewed-on: https://chromium-review.googlesource.com/1180721Reviewed-by:
skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#584334}
-
Chromite Chromium Autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/df1dcd998db4..0e1fc1042fe0 git log df1dcd998db4..0e1fc1042fe0 --date=short --no-merges --format='%ad %ae %s' 2018-08-19 dhanyaganesh@chromium.org CreateTarball: Refactor and clean up debug code Created with: gclient setdep -r src/third_party/chromite@0e1fc1042fe0 The AutoRoll server is located here: https://chromite-chromium-roll.skia.org 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=chrome-os-gardeners@chromium.org Change-Id: I605ad564f6aad6c6d52b727d48b7697452590910 Reviewed-on: https://chromium-review.googlesource.com/1180722Reviewed-by:
Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#584333}
-
Ned Nguyen authored
Bug:676612 Change-Id: Ia884ea757f60c625442a7564955f4f0eea8a1164 TBR=ksakamoto@chromium.org, kouhei@chromium.org NOTRY=true Change-Id: Ia884ea757f60c625442a7564955f4f0eea8a1164 Reviewed-on: https://chromium-review.googlesource.com/1180213 Commit-Queue: Ned Nguyen <nednguyen@google.com> Reviewed-by:
Ned Nguyen <nednguyen@google.com> Cr-Commit-Position: refs/heads/master@{#584332}
-
afdo-chromium-autoroll authored
This CL may cause a small binary size increase, roughly proportional to how long it's been since our last AFDO profile roll. For larger increases (around or exceeding 100KB), please file a bug against gbiv@chromium.org. Additional context: https://crbug.com/805539 The AutoRoll server is located here: https://afdo-chromium-roll.skia.org 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=gbiv@chromium.org Change-Id: I631e2f562686bafc3a78b8fd7a251edc984dcf0c Reviewed-on: https://chromium-review.googlesource.com/1180660 Commit-Queue: afdo-chromium-autoroll <afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Reviewed-by:
afdo-chromium-autoroll <afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#584331}
-
Trent Apted authored
This is a precursor to https://crrev.com/c/1053338 which introduces base::CheckedObserver. Existing observers will be unchecked (as they are already). There is no behavior change with this CL. The CL is mechanical. The bulk was done with variations on a sed script: git grep -l ' base::ObserverList<.*> .*;' -- '*.cc' '*.h' '*.mm' | \ xargs -IX sed -i -r 's/(^[ ]*)base::ObserverList<([^>]*)> (.*);/'\ '\1base::ObserverList<\2>::Unchecked \3;/' X With some manual follow-ups to get special cases. TBR=gab@chromium.org Bug: 842987 Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:ios-simulator-full-configs;luci.chromium.try:linux_layout_tests_slimming_paint_v2;luci.chromium.try:linux_mojo;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.mac:ios-simulator-cronet Change-Id: Idffe88e2b52f67f9226eb7b6d922070349dacc22 Reviewed-on: https://chromium-review.googlesource.com/1175511 Commit-Queue: Trent Apted <tapted@chromium.org> Reviewed-by:
Gabriel Charette <gab@chromium.org> Cr-Commit-Position: refs/heads/master@{#584330}
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=mmoss@chromium.org Change-Id: Ic65a498a89afdaa77da052cd7378deb16c75665d Reviewed-on: https://chromium-review.googlesource.com/1180702Reviewed-by:
chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/heads/master@{#584329}
-
Julie Jeongeun Kim authored
It introduces wayland_util.cc/h and moves the code to create shared memory buffer and draw bitmap on it from WaylandCursor, as it could be used generally rather than specific to cursor area. On upcoming patch for drag and drop on Wayland, it's also required to pass the drag icon surface to Wayland. It doesn't bring behavioral changes. Bug: 578890, 875164 Change-Id: I0cd4603c2abacaa899a9fcf19d97186d6f493146 Reviewed-on: https://chromium-review.googlesource.com/1179487 Commit-Queue: Julie Jeongeun Kim <jkim@igalia.com> Reviewed-by:
Antonio Gomes <tonikitoo@igalia.com> Reviewed-by:
Maksim Sisov <msisov@igalia.com> Cr-Commit-Position: refs/heads/master@{#584328}
-
Christopher Cameron authored
The function BridgedNativeWidget::SetBounds calls back into the NativeWidgetMac to determine - the minimum content size - if the widget's position should be relative to the parent or the screen (and the offset to do that computation) - if the widget is a modal sheet This call will eventually be running in the app shim process, where these values will not be available (without adding a synchronous IPC). Change NativeWidgetMac::SetBounds to call BridgedNativeWidgetHostImpl:: SetBounds, and have that function pre-compute the required parameters, - minimum content size - offset necessary to be applied to compensate for position being relative to the parent or the screen - (but not if the widget is a modal sheet, that's coming later) and pass these as parameters to BridgedNativeWidget::SetBounds. Split out the SetBounds calls made during initialization from being within BridgedNativeWidget::Init to being made by its caller, BridgedNativeWidgetHostImpl::InitWindow, to allow the additional parameters to be passed in. Bug: 859152 Change-Id: I2f33ab08f60d2ed1bc3b6af5ecf3402e3715ffd4 Reviewed-on: https://chromium-review.googlesource.com/1178813 Commit-Queue: ccameron <ccameron@chromium.org> Reviewed-by:
Elly Fong-Jones <ellyjones@chromium.org> Cr-Commit-Position: refs/heads/master@{#584327}
-
Chromium WPT Sync authored
Using wpt-import in Chromium e57c623d. Build: https://ci.chromium.org/buildbot/chromium.infra.cron/wpt-importer/22916 Note to sheriffs: This CL imports external tests and adds expectations for those tests; if this CL is large and causes a few new failures, please fix the failures by adding new lines to TestExpectations rather than reverting. See: https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md NOAUTOREVERT=true TBR=robertma No-Export: true Change-Id: Id7f2b07592d744cd563d75f7bf95bb2ba03ad8d3 Reviewed-on: https://chromium-review.googlesource.com/1180652 Commit-Queue: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> Reviewed-by:
Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> Cr-Commit-Position: refs/heads/master@{#584326}
-
Nico Weber authored
This reverts commit ee9ee634. Reason for revert: Likely broke remoting tests on Win7, https://crbug.com/875619 Original change's description: > [Windows Host] Prevent connection hang for hosts with 3D Display Mode enabled > > This change prevents a hang when connecting to a Windows machine > which has curtain mode and 3d display mode enabled. The root cause > of the hang is that creating a D3D11 device takes several seconds so > function calls which used to take a few milliseconds now take 5+ > seconds. I did not see a mechanism to control this display mode > programatically so I am adding code which can detect the condition > and the logic to prevent D3D usage when 3D mode is enabled. > > Of note is the change in BasicDesktopEnvironment where I requery the > D3D apis. DesktopEnvironmentOptions are queried in Session 0 and > then passed on to the Desktop process. There is a non-obvious > problem with this as many D3D methods cannot be queried or will > not return reliable results. This results in a base set of options > being set in Session 0 (which includes user / experiment overrides) > and then passed into a session where D3D will return new values. In > this CL, I requery the D3D APIs and update the capturer options if > they should be disabled. > > BUG=836007 > > Change-Id: Ib7a6e61fa7987bd093e93a6100b97cc49e3aff05 > Reviewed-on: https://chromium-review.googlesource.com/1164403 > Commit-Queue: Joe Downing <joedow@chromium.org> > Reviewed-by: Jamie Walch <jamiewalch@chromium.org> > Cr-Commit-Position: refs/heads/master@{#583276} TBR=jamiewalch@chromium.org,joedow@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 836007 Change-Id: I464ba6eb37560ef6fc687516e9e33682bee4ac7a Reviewed-on: https://chromium-review.googlesource.com/1180681Reviewed-by:
Nico Weber <thakis@chromium.org> Commit-Queue: Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#584325}
-
- 18 Aug, 2018 24 commits
-
-
James Cook authored
When the user clicks on the shutdown button in the system tray we start a process that tears down ash::Shell and closes the tray bubble. This dispatches mouse exit events to windows as the system is being torn down. In production this sometimes crashes. I cannot repro on device, on linux-chromeos, or under ASAN, using the M69 code. The crash started after we turned off the new unified system tray in M69, so it's likely related to the old system tray. It should go away when we switch to the new tray. As a workaround, skip dispatch of mouse exits during shutdown and don't process any new events. Bug: 874156 Test: manually exercise sign out and shutdown Change-Id: Ic898d15270661b3275a4f396d154ad2c02ba0644 Reviewed-on: https://chromium-review.googlesource.com/1180070 Commit-Queue: James Cook <jamescook@chromium.org> Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Cr-Commit-Position: refs/heads/master@{#584324}
-
Christopher Cameron authored
This removes parts of crrev.com/583350, preserving the following - explicitly require that NSWindows be NativeWidgetMacNSWindow - return a scoped_nsobject from CreateNSWindow, and remove requirement of autoreleasing the result, to clarify lifetimes This removes the ability to create an NSWindow in the AppShim process for now. That will be re-added later. Bug: 859152 Change-Id: Ife70a91ac9557f2ec7a488a8714f907eaecea0e3 Reviewed-on: https://chromium-review.googlesource.com/1177276 Commit-Queue: ccameron <ccameron@chromium.org> Reviewed-by:
Trent Apted <tapted@chromium.org> Cr-Commit-Position: refs/heads/master@{#584323}
-
Ben L. Titzer authored
Keep these owners up to date: remove bradnelson@ and eholk@ from WASM metrics (sadly). R=adamk@chromium.org Change-Id: Iaec80eb69da6159b2547e57d1ad618057c6cdc13 Reviewed-on: https://chromium-review.googlesource.com/1156597Reviewed-by:
Adam Klein <adamk@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Commit-Queue: Ben Titzer <titzer@chromium.org> Cr-Commit-Position: refs/heads/master@{#584322}
-
Rouslan Solomakhin authored
Speed up builds in /components/payments with "use_jumbo_build = true" setting in GN args. Bug: NONE Change-Id: I18890875b46450dde461e126573e44958e6ac7d9 Reviewed-on: https://chromium-review.googlesource.com/1180555 Commit-Queue: Rouslan Solomakhin <rouslan@chromium.org> Reviewed-by:
Ganggui Tang <gogerald@chromium.org> Cr-Commit-Position: refs/heads/master@{#584321}
-
Nico Weber authored
The test was comparing two wchar_ts for pointer equality. In non-asan builds, equal constant strings in different TUs got merged, but in asan builds this seems ot not happen. Do a string comparison instead. Bug: 875225 Change-Id: I6a4031d1d6bca5697fb0a2dd6224323667711a81 Reviewed-on: https://chromium-review.googlesource.com/1180552Reviewed-by:
Reid Kleckner <rnk@chromium.org> Commit-Queue: Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#584320}
-
Wei Li authored
When an oopif is printed along with its parent, this frame should not use printing layout. Instead, its size is confined by its parent. Before this change, ShouldUsePrintingLayout() works correctly in LocalFrame::SetPrinting() since it also checks |use_printing_layout| variable. But ShouldUsePrintingLayout() doesn't work correctly during layout code where it is also called to decide whether printing layout should be applied for style etc. This CL fixes ShouldUsePrintingLayout() to return the correct value for all cases. BUG=853942 Change-Id: I6cad75fd6db59d00d4c07ea8b23dbaf6a4a47afc Reviewed-on: https://chromium-review.googlesource.com/1175404 Commit-Queue: Wei Li <weili@chromium.org> Reviewed-by:
Ken Buchanan <kenrb@chromium.org> Reviewed-by:
Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#584319}
-
Philip Rogers authored
This patch marks 33 tests as passing. Many of the android/fullscreen tests were fixed by chaopeng's recent patch https://crrev.com/584169. Bug: 836886 Cq-Include-Trybots: luci.chromium.try:linux-blink-gen-property-trees;luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel Change-Id: I978cf46b333f81f0688dea6ca5023f5d59d0b01d Reviewed-on: https://chromium-review.googlesource.com/1180620 Commit-Queue: Philip Rogers <pdr@chromium.org> Reviewed-by:
Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#584318}
-
Joshua Peraza authored
https://chromium.googlesource.com/breakpad/breakpad.git/+log/79ba6a494fb2..1459e5df74dd $ git log 79ba6a494..1459e5df7 --date=short --no-merges --format='%ad %ae %s' 2018-08-17 jperaza Fix debug build after 16e0852 2018-08-17 jperaza Make a parameter a const reference 2018-08-16 jperaza Treat high_pc as an address for DW_FORM_GNU_addr_index 2018-08-15 mark Fix Windows client_tests GYP build after 88d8114fda3e 2018-08-14 gsvelto Fixed a typo introduced in revision 16e08520e6027df4bf1934abbfd5e1a088ffb69c 2018-08-04 gsvelto Add support for parsing the DW_AT_ranges attributes 2018-08-06 jperaza Set new ARM64 context flags 2018-08-01 jperaza processor: Fix memory leak after 88d8114f 2018-08-01 jperaza Define and use a a new MDRawContextARM64 2018-07-31 jperaza Rename MDRawContextARM64 and its context flags 2018-07-31 jperaza mac: Fix broken xcode projects 2018-07-19 ivanpe Add path_helper.cc and path_helper.h to dump_syms.xcodeproj. 2018-07-10 jperaza Update lss to a89bf7903f3169e6bc7b8efc10a73a7571de21cf 2018-07-09 jperaza ios: Fix build of exception_handler_no_mach 2018-07-09 jperaza Use hash_map and hash_set from __gnu_cxx 2018-07-06 jperaza iOS: disable using CFI in stackwalking Created with: roll-dep src/third_party/breakpad/breakpad Bug: 870908 Change-Id: Ib24fd9b8cb35783745191a3442bf8634e9444e7f Reviewed-on: https://chromium-review.googlesource.com/1180598Reviewed-by:
Mark Mentovai <mark@chromium.org> Commit-Queue: Joshua Peraza <jperaza@chromium.org> Cr-Commit-Position: refs/heads/master@{#584317}
-
Christian Biesinger authored
We need to relayout whenever scrollbars change. The change in https://chromium-review.googlesource.com/1162657 was not quite correct. The change to CopyFragmentDataToLayoutBox is necessary to not break virtual/layout_ng_experimental/fragmentation/auto-overflow.html Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng Change-Id: I589d6a1bd1b3f06224e6c4aeae3e7cdf163206cc Reviewed-on: https://chromium-review.googlesource.com/1178804Reviewed-by:
Emil A Eklund <eae@chromium.org> Commit-Queue: Christian Biesinger <cbiesinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#584316}
-
Chromium WPT Sync authored
Using wpt-import in Chromium c8635904. Build: https://ci.chromium.org/buildbot/chromium.infra.cron/wpt-importer/22867 Note to sheriffs: This CL imports external tests and adds expectations for those tests; if this CL is large and causes a few new failures, please fix the failures by adding new lines to TestExpectations rather than reverting. See: https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md Directory owners for changes in this CL: bjonesbe@adobe.com: external/wpt/css/css-shapes bugsnash@chromium.org, ericwilligers@chromium.org, meade@chromium.org, nainar@chromium.org, rjwright@chromium.org, shend@chromium.org: external/wpt/css/css-cascade ericwilligers@chromium.org: external/wpt/css/motion kojii@chromium.org: external/wpt/css/css-writing-modes rego@igalia.com: external/wpt/css/css-ui NOAUTOREVERT=true TBR=robertma No-Export: true Change-Id: I499748d80324c6854cf2862f5e410ea9a8fabd8d Reviewed-on: https://chromium-review.googlesource.com/1180617 Commit-Queue: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> Reviewed-by:
Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> Cr-Commit-Position: refs/heads/master@{#584315}
-
Alex Clarke authored
This reverts commit 6410ee3d. Reason for revert: This is causing some crashes. Original change's description: > Second try at using LazilyDeallocatedDeque instead of circular_deque in TaskQueue > > Previous patch: https://chromium-review.googlesource.com/c/chromium/src/+/1080792 > > Our usage pattern is unfortunate for existing queues such as > base::circular_deque. We tend to fill up an empty queue and then drain all > those tasks until it's empty. This means the queue yo-yos in size which > confuses the memory reclamation schemes of most queues. > > As an optimisation we introduce a deque specialised for TaskQueueManager's > usage patterns. For performance (memory allocation isn't free) we don't > automatically reclaim memory when the queue becomes empty. Instead we rely > on the surrounding code periodically calling MaybeShrinkQueue, ideally when > the queue is empty. > > We keep track of the maximum recent queue size and rate limit > how often MaybeShrinkQueue actually shrinks the buffer to avoid unnecessary > churn. > > This yields a nice win on our microbenchmark: > > Patch: us/run for 10000 delayed tasks with N queues > 1 queue 4 queues 8 queues 32 queues > 33448.166666666664 33215.75496688742 33484.34 34018.37414965987 > 33972.18243243243 33846.91891891892 34489.737931034484 34727.90277777778 > 33367.90666666667 33167.54304635762 33392.96 33906.89864864865 > 33392.13333333333 33107.17763157895 33340.18 33718.73825503356 > 37921.01515151515 39379.06299212598 38851.27906976744 39366.03125 > 38171.564885496184 37401.72388059701 37640.32330827068 37800.51127819549 > 34691.2275862069 34359.61643835616 34993.468531468534 35366.795774647886 > 35981.20863309353 35089.18881118881 38530.230769230766 39280.3515625 > 39262.8671875 36411.384057971016 33576.10067114094 33939.69594594595 > 37913.59848484849 38324.076335877864 38061.59848484849 39921.00793650794 > Average 35812.1871 35430.24471 35636.02188 36204.63076 > > ToT: us/run for 10000 delayed tasks with N queues > 1 queue 4 queues 8 queues 32 queues > 40459.540322580644 40536.04838709677 38994.573643410855 38696.2 > 39422.149606299216 39299.5 37888.18939393939 37874.74436090225 > 38419.70229007633 38025.742424242424 37844.41353383459 38020.469696969696 > 35052.72027972028 38147.80303030303 35504.89361702128 34138.02721088436 > 37096.77777777778 34942.541666666664 37003.529411764706 37579.60447761194 > 38818.67441860465 38233.068702290075 37978.628787878784 37867.57142857143 > 38455.49618320611 37903.05303030303 38106.143939393936 38129.5 > 40609.33064516129 37721.75187969925 34656.441379310345 34294.33561643836 > 35273.704225352114 34646.324137931035 34335.643835616436 34311.82876712329 > 35821.41428571429 35362.035211267605 37522.27611940299 35429.281690140844 > Average 37942.951 37481.78685 36983.47337 36634.15632 > > Percentage improvement > 5.61570422 5.473437399 3.643388159 1.172472933 > > NB the reason the improvement goes down with the number of queues is because > we're saving malloc overhead in the queue, but a constant number of tasks are > posted across N queues. This means the more queues we have in this test, the > less loaded the queues are individually. > > Change-Id: I975d7f864dc55715fb9f949ef65321da93e4cef4 > Reviewed-on: https://chromium-review.googlesource.com/1169043 > Reviewed-by: Sami Kyöstilä <skyostil@chromium.org> > Commit-Queue: Alex Clarke <alexclarke@chromium.org> > Cr-Commit-Position: refs/heads/master@{#582586} TBR=skyostil@chromium.org,alexclarke@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Change-Id: Id8290646dba1dcea9fcf92d490b9ce4ac63ae702 Reviewed-on: https://chromium-review.googlesource.com/1177561Reviewed-by:
Alex Clarke <alexclarke@chromium.org> Reviewed-by:
Sami Kyöstilä <skyostil@chromium.org> Commit-Queue: Alex Clarke <alexclarke@chromium.org> Cr-Commit-Position: refs/heads/master@{#584314}
-
Nico Weber authored
LayerTreeHostBlendingPixelTest.BlendingWith* still timeout on win/asan after the switch to swiftshader, so bump up the timeout even more. Bug: 875223 Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel Change-Id: I30eb5e3717ed7c5f55a478b8e2e1323c8e59d974 Reviewed-on: https://chromium-review.googlesource.com/1180282Reviewed-by:
Alexis Hétu <sugoi@chromium.org> Reviewed-by:
enne <enne@chromium.org> Commit-Queue: Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#584313}
-
skia-chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/d18d79130163..5cc10c8cd6db git log d18d79130163..5cc10c8cd6db --date=short --no-merges --format='%ad %ae %s' 2018-08-18 angle-skia-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com Roll third_party/externals/angle2 43a2762db19a..5055fba5692f (3 commits) Created with: gclient setdep -r src/third_party/skia@5cc10c8cd6db The AutoRoll server is located here: https://autoroll.skia.org 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=master.tryserver.blink:linux_trusty_blink_rel;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=kjlubick@chromium.org Change-Id: Ibe9b01f470991e072fe9b5bdfe649664483f6e58 Reviewed-on: https://chromium-review.googlesource.com/1180450Reviewed-by:
skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#584312}
-
Roger McFarlane authored
The current implementation uses a vector to store all the forms that we parse. The code to find cached forms the searches that vector starting from the back. This CL changes the cache to a map instead, so each form will be saved only once. The key is the FormSignature and the value is a unique ptr to the FormStructure. Notable differences - AutofillHandler now holds a map, by form signature, of FormStructure unique_ptrs instead of a vector. - Parsing/updating FormData associated with a given signature now delete any previously cached FormStructure for that signature. - form_structure_browsertests sorts currently known form structures by their earliest parse time, to preserve the output ordering. - AutofillHandler::FindCachedForm To update an existing form signature, this function is O(lg n). when inserting a new form signaure this function is O(n + log n). Bug: 769617, 864469, 864503, 865640, 866504 Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet Change-Id: I630336d6672a57acbe0257501c44f540b39341de Reviewed-on: https://chromium-review.googlesource.com/1175456 Commit-Queue: Roger McFarlane <rogerm@chromium.org> Reviewed-by:
Moe Ahmadi <mahmadi@chromium.org> Cr-Commit-Position: refs/heads/master@{#584311}
-
afdo-chromium-autoroll authored
This CL may cause a small binary size increase, roughly proportional to how long it's been since our last AFDO profile roll. For larger increases (around or exceeding 100KB), please file a bug against gbiv@chromium.org. Additional context: https://crbug.com/805539 The AutoRoll server is located here: https://afdo-chromium-roll.skia.org 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=gbiv@chromium.org Change-Id: I9e73cac82282e6db8425fea7c990e559d860129a Reviewed-on: https://chromium-review.googlesource.com/1180616Reviewed-by:
afdo-chromium-autoroll <afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: afdo-chromium-autoroll <afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#584310}
-
Zhiqiang Zhang authored
Previously we made CastMessage & CastSessionImpl (now CastSessionController) lifecycle bound to per connection, which makes the session management over-complicated. This CL makes those classes having the same lifecycle as CafBaseMRP/CafMRP, so there's no need to create/set/unset instances any more. These instances will only be active when there's currently an active session. Bug: 711860 Change-Id: I1736bb7085cd1ffbffed8ec40f3410ebe997e64e Reviewed-on: https://chromium-review.googlesource.com/1171582Reviewed-by:
Thomas Guilbert <tguilbert@chromium.org> Commit-Queue: Zhiqiang Zhang <zqzhang@chromium.org> Cr-Commit-Position: refs/heads/master@{#584309}
-
Christopher Cameron authored
The methods NativeWidgetMac::GetWindowBoundsInScreen, GetClientAreaBoundsInScreen, and GetWorkAreaBoundsInScreen compute their results by querying the underlying NSWindow. When the NSWindow is a separate process, this won't be an option. Instead, have the BridgedNativeWidget push these properties to the BridgetNativeWidgetHost, from which the NativeWidgetMac may query them. Also have the BridgedNativeWidget (in the app shim process) query the display::Display for its NSWindow and send that to the BridgetNativeWidgetHost (in the browser process). This can then be used to update the device scale factor, vsync, and color space properties of the compositor (at present these properties updated only by attached RenderWidgetHostViewMacs). Rename BridgedNativeWidgetHost::SetSize to SetViewSize, to indicate that it is computed differently. Remove BridgedNativeWidgetHost::SetCompositorSize as its functionality can be rolled into the new function. Bug: 859152 Change-Id: If00184c31f9c493ece4ea08ace11d0be3a866786 Reviewed-on: https://chromium-review.googlesource.com/1175428 Commit-Queue: ccameron <ccameron@chromium.org> Reviewed-by:
Elly Fong-Jones <ellyjones@chromium.org> Cr-Commit-Position: refs/heads/master@{#584308}
-
Gang Wu authored
Implement Journal storage API in java Bug:875438 Change-Id: Iaaede743f66182c3bec7ffc945c37fc9204c1475 Reviewed-on: https://chromium-review.googlesource.com/1179252 Commit-Queue: Gang Wu <gangwu@chromium.org> Reviewed-by:
Filip Gorski <fgorski@chromium.org> Cr-Commit-Position: refs/heads/master@{#584307}
-
skia-chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/11378953830a..d18d79130163 git log 11378953830a..d18d79130163 --date=short --no-merges --format='%ad %ae %s' 2018-08-18 swiftshader-skia-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com Roll third_party/externals/swiftshader 80ab360d2622..94d4660dd3f1 (1 commits) 2018-08-18 kjlubick@google.com [PathKit] Add more correctness tests to gold 2018-08-18 mtklein@google.com refactor cpu configs Created with: gclient setdep -r src/third_party/skia@d18d79130163 The AutoRoll server is located here: https://autoroll.skia.org 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=master.tryserver.blink:linux_trusty_blink_rel;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=kjlubick@chromium.org Change-Id: I55794e67b77596ea74e79b97dc42cb7af26b59a6 Reviewed-on: https://chromium-review.googlesource.com/1180448Reviewed-by:
skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#584306}
-
Michael Giuffrida authored
The Highlights app is part of Chrome OS Demo Mode. It will use chrom.metricsPrivate.getIsCrashReportingEnabled() to enable/disable Google Analytics reporting, similar to other Chrome apps. There are 2 versions of this app, thus 2 entries. Bug: 819404 Change-Id: I023880eac23c332afe1fb80942c7d9f737cb369d Reviewed-on: https://chromium-review.googlesource.com/1179370Reviewed-by:
Toni Baržić <tbarzic@chromium.org> Reviewed-by:
Steven Holte <holte@chromium.org> Commit-Queue: Michael Giuffrida <michaelpg@chromium.org> Cr-Commit-Position: refs/heads/master@{#584305}
-
Ben Wells authored
Bookmark apps that are not locally installed will not be treated as installed for the installation banner checks. In the future more changes to their behaviour, in relation to the chrome://apps page will be introduced. Bug: 874841 Change-Id: I48741967a646c6aac95cde3c832b8c8860b4f7b1 Reviewed-on: https://chromium-review.googlesource.com/1177529 Commit-Queue: Ben Wells <benwells@chromium.org> Reviewed-by:
vitaliii <vitaliii@chromium.org> Reviewed-by:
Giovanni Ortuño Urquidi <ortuno@chromium.org> Cr-Commit-Position: refs/heads/master@{#584304}
-
Siddhartha authored
The startup category in background tracing is not useful to trigger with a histogram since it has to start early at startup for getting useful information. The startup category will set a flag in app preferences and start tracing next time chrome starts and upload a report. We can keep having session consistency for the trials, with startup traces being uploaded one session after the config was seen. BUG=859260 Change-Id: I588cb5ebd21e96abe9230718f69775d271f827f5 Reviewed-on: https://chromium-review.googlesource.com/1155996 Commit-Queue: Siddhartha S <ssid@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Reviewed-by:
oysteine <oysteine@chromium.org> Cr-Commit-Position: refs/heads/master@{#584303}
-
Jun Choi authored
Currently, FidoBleDiscoveryBase returns when ble adapter is not present. This is problematic as the embedder layer explicitly waits for NotifyDiscoveryStarted() to be invoked prior to launching UI. Make sure to call NotifyDiscoveryStarted(false) when Bluetooth adapter is not present. Bug: 847985 Change-Id: I968e2ff5f1408b7a5a56eb94b25240b8705b1c68 Reviewed-on: https://chromium-review.googlesource.com/1176977Reviewed-by:
Balazs Engedy <engedy@chromium.org> Commit-Queue: Jun Choi <hongjunchoi@chromium.org> Cr-Commit-Position: refs/heads/master@{#584302}
-
gogerald authored
Change-Id: Iaea43229f0fc400cc6f4c0f2415e59a60748d224 Reviewed-on: https://chromium-review.googlesource.com/1180606 Commit-Queue: Ganggui Tang <gogerald@chromium.org> Commit-Queue: Rouslan Solomakhin <rouslan@chromium.org> Reviewed-by:
Rouslan Solomakhin <rouslan@chromium.org> Cr-Commit-Position: refs/heads/master@{#584301}
-