GitLab

This is to test grounds with UI.Fragment and custom elements v1.

Bug: none
Change-Id: I62c3867ee8da84c867d432e49bd049757ea502fa
Reviewed-on: https://chromium-review.googlesource.com/826306
Commit-Queue: Dmitry Gozman <dgozman@chromium.org>
Reviewed-by: Andrey Lushnikov <lushnikov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524460}

https://pdfium.googlesource.com/pdfium.git/+log/d92073b75627..667fa571db51

$ git log d92073b75..667fa571d --date=short --no-merges --format='%ad %ae %s'
2017-12-15 hnakashima Validate base color space of Indexed color spaces.
2017-12-15 hnakashima Validate shading pattern's ColorSpace. It cannot be a Pattern CS.

Created with:
  roll-dep src/third_party/pdfium


The AutoRoll server is located here: https://pdfium-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=dsinclair@chromium.org

Change-Id: I85043b9fd2a697d9e39521560c165cdd1e510b2f
Reviewed-on: https://chromium-review.googlesource.com/829987
Reviewed-by: <pdfium-deps-roller@chromium.org>
Commit-Queue: <pdfium-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524459}

Extend PaintLayerPainter::AdjustForPaintOffsetTranslation() which
adjusted paint_dirty_rect based on PaintOffsetTranslation to
AdjustForPaintProperties() which (if needed) maps paint_dirty_rect
from the root layer to the current layer dealing with more cases:
- The existing PaintOffsetTranslation handling;
- Fixed layer whose transform state may escape the root layer's
  transform state;
- Scroll offsets.

This fixes most of the failures of spv175+rls.

Bug: 793675
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: I400c9da7d215132247c1b4e631be692070fdb655
Reviewed-on: https://chromium-review.googlesource.com/827671
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524458}

When SetProtection is used for wasm memory, it can fail if not enough
memory is available when growing. Fix to return the result of system
calls.

As coordination in needed between V8/Gin - this change adds a
new SetProtection method with a boolean return, subsequent changes
in V8/Chromium will swap this out to be the default SetProtection
method.

Bug: 775047
Change-Id: I9f55d156c8317be8c012de60940d1698db439c86
Reviewed-on: https://chromium-review.googlesource.com/753429Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Reviewed-by: Ross McIlroy <rmcilroy@chromium.org>
Reviewed-by: Adam Klein <adamk@chromium.org>
Commit-Queue: Deepti Gandluri <gdeepti@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524457}

Transitions another set of callers to use the new unique_ptr version of
SetLayoutManager.

The only nontrivial changes are in tri_view.cc where the existing
initialization did not with well with the new pattern.

The constants in PasswordGenerationPopupController were given storage
because not having storage was causing errors passing through
std::make_unique which passes by &&.

Change-Id: Id51f1a888b7148169629aabae523530fb03b3890
Reviewed-on: https://chromium-review.googlesource.com/827668
Commit-Queue: Brett Wilson <brettw@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524456}

NGOutOfFlowLayoutPart used to have a single containing block,
and it was defined by a NGOOFLP member variables.

With inline containing blocks, we have multiple containing blocks,
defined by ContainingBlockInfo.

This CL moves definition of default containing block out of multiple
member variables into single ContainingBlockInfo.

Bug: 635619
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: I69dd499cb69c7e6fc56971e85882cd7e6241f99c
Reviewed-on: https://chromium-review.googlesource.com/829888Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Aleks Totic <atotic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524455}

Bug: 781409
Change-Id: I70d28e9f43a4747f19666fbfa9f3bb18ac1d22d7
Reviewed-on: https://chromium-review.googlesource.com/830256Reviewed-by: Ned Nguyen <nednguyen@google.com>
Reviewed-by: Charlie Andrews <charliea@chromium.org>
Commit-Queue: rnephew <rnephew@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524454}

https://chromium.googlesource.com/chromium/llvm-project/compiler-rt/lib/fuzzer.git/+log/a00e8070bea6..ba2c1cd6f87a

$ git log a00e8070b..ba2c1cd6f --date=short --no-merges --format='%ad %ae %s'
2017-12-13 morehouse [libFuzzer] Add dummy call of LLVMFuzzerTestOneInput to afl_driver.
2017-12-12 kcc [libFuzzer] change the strategy for -experimental_len_control to grow max_len slower
2017-12-09 kcc [libFuzzer] even less aggressive step function for stack depth. Also don't use asan in one test to speed it up
2017-12-09 kcc [libFuzzer] make the stack depth signal less agressive, otherwise we are sometimes exploding the corpus size. This still needs more analysis and tuning
2017-12-08 morehouse [libFuzzer] Add support for Fuchsia OS.
2017-12-08 kcc [libFuzzer] honor -use_counters, sligntly change the meaning of -experimental_len_control, call UpdateFeatureFrequency only if instructed by the flag
2017-12-06 kcc [libFuzzer] Decrease stack usage in unit tests
2017-12-06 kcc [libFuzzer] fix a minor regression in printing
2017-12-05 morehouse [libFuzzer] Make redirects happen in proper sequence.
2017-12-04 morehouse [libFuzzer] Remove const from ignoreRemainingArgs return value.
2017-12-04 morehouse [libFuzzer] Remove FuzzerCommand.cpp from build sources.
2017-12-04 morehouse [libFuzzer] Encapsulate commands in a class.
2017-12-01 kcc [libFuzzer] add a flag -malloc_limit_mb
2017-12-01 kcc [libFuzzer] remove stale flags; NFC
2017-12-01 kcc [libFuzzer] add an experimental search heuristic flag -reduce_depth
2017-11-28 delcypher [LibFuzzer] Improve comments on `CounterToFeature()` function.
2017-11-17 vitalybuka [fuzzer] Initialize PcDescr buffer before calling __sanitizer_symbolize_pc
2017-11-15 kcc libfuzzer: Fix file listing on some filesystems
2017-11-15 kcc [libFuzzer] respect max_len during merge

Created with:
  roll-dep src/third_party/libFuzzer/src

Bug: 539572
Change-Id: I8dd43d49dea0441595e9e04f1ddb61950333f896
Reviewed-on: https://chromium-review.googlesource.com/828408
Commit-Queue: Abhishek Arya <inferno@chromium.org>
Reviewed-by: Abhishek Arya <inferno@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524453}

Fixes a problem with ML not being applied correctly on a "retap", a tap
near the previous selection.  The problem is that the Search is still in
progress and the Bar still active when the retap is processed.

Adds a new Internal State TAP_GESTURE_COMMIT that allows code to run
during the initial stage of tap gesture processing.  This new state is
used to handle the retap by detecting if the panel is still open.

Loading the Ranker predictor is now moved to an earlier stage of tap
processing (using the new internal state) to allow it to be fully loaded
and ready to predict by the time all the prediction features have been
gathered.

Refactored writing the outcomes to Ranker in
ContextualSearchPanelMetrics so it can be called when appropriate.  Now
logging outcomes and resetting the CSRankerLogger is done whenever the
UI is hidden or a retap is detected.

BUG=783995

Change-Id: I3122a20200696682205379fdd619e655262520f9
Reviewed-on: https://chromium-review.googlesource.com/802540
Commit-Queue: Donn Denman <donnd@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524452}

It's seen to time out on the linux-chromeos-rel tryserver which is
affecting the CQ. Until someone is found to investigate the timeouts,
turn off the test.

BUG=794490
TBR=lazyboy@chromium.org

Change-Id: Idbf5f975df1e9b9e49f10c68bef0112e7545b541
Reviewed-on: https://chromium-review.googlesource.com/829892Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524451}

The sw_reporter_installer was getting too large and confusing.
SwReporterInstallerPolicy is not an appropriate class to hold information
about user-initiated cleanups. This CL is preliminary work for a
redesigned version of
https://chromium-review.googlesource.com/c/chromium/src/+/810086

Bug: 776538
Change-Id: I3833a06aec23fc83eba05ed2a36e014875730d3b
Reviewed-on: https://chromium-review.googlesource.com/817620Reviewed-by: Sorin Jianu <sorin@chromium.org>
Reviewed-by: Tommy Li <tommycli@chromium.org>
Reviewed-by: Joe Mason <joenotcharles@chromium.org>
Commit-Queue: proberge <proberge@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524450}

Add 'target_defaults' to the list of top level keys ignored by gypi_to_gn.py
so it can process files that contain that.

BUG=795329

Change-Id: I3733a7efb97366827febf87ec1be95ad8723be23
Reviewed-on: https://chromium-review.googlesource.com/830114Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Frank Henigman <fjhenigman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524449}

When a Read() call finished asynchronously, it was clearing its buf_
pointer after calling into its consumer. If its consumer called Read()
again, that could have resulted in populating buf_ again, which would
then incorrectly be cleared by the higher level call.

Also, if Init() interrupted a previous call to Init(), the callback to
the first Init() call was not being cancelled.

Bug: 794330
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: I71faee5bcde302acd1962e55b4f2bb75d8c31c8d
Reviewed-on: https://chromium-review.googlesource.com/825843
Commit-Queue: Matt Menke <mmenke@chromium.org>
Reviewed-by: Randy Smith <rdsmith@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524448}

It's used for poking at InputDeviceClient. As Chrome/Ash use
DeviceDataManager in classic mode InputDeviceClientTestApi handles
both. That is, if DeviceDataManager exists it pokes at it, otherwise
InputDeviceClient.

BUG=776514
TEST=test only changes

Change-Id: I4e46dbe74dbce4a37d2b4e054b8fec88d4b5a048
Reviewed-on: https://chromium-review.googlesource.com/829713Reviewed-by: kylechar <kylechar@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524447}

Change-Id: Ida79579f16af6c2d0dcd97a7d972b2444f2280c3
Reviewed-on: https://chromium-review.googlesource.com/827541Reviewed-by: Brian White <bcwhite@chromium.org>
Commit-Queue: Steven Holte <holte@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524446}

Record partner bookmark count as zero when skipped, so that
the distribution is not skewed.

Bug: 787132
Change-Id: Ie5c0c49120ff47a0fce984de823928997a1652f8
Reviewed-on: https://chromium-review.googlesource.com/826465Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Wei-Yin Chen (陳威尹) <wychen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524445}

This previously existed, but was mistakenly removed in
crrev.com/c/648076.

Bug: none
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: I09759933d8717d55de1343852827ab3289a4bee0
Reviewed-on: https://chromium-review.googlesource.com/830136
Commit-Queue: Kurt Horimoto <kkhorimoto@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Reviewed-by: Kurt Horimoto <kkhorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524444}

Because Blink depends on the WebUSB interfaces directly they shouldn't
be part of chrome_content_browser_manifest_overlay.json and should
instead be part of content_browser_manifest.json. Since these are still
implemented by Chrome and not //content the factory methods are moved
into ContentBrowserClient.

Change-Id: Ic34008eccca45dd24bace5afee8fff478bb9ba6d
Reviewed-on: https://chromium-review.googlesource.com/828025Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524443}

Remove an unused (and deprecated) overload of
ExtensionTabUtil::GetBrowserFromWindowID.

Bug: None

Change-Id: Ia5580dc63e39d0b9c01784abf69ef31383ff79ce
Reviewed-on: https://chromium-review.googlesource.com/829693Reviewed-by: catmullings <catmullings@chromium.org>
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524442}

(a) device info should be in the batch summary of the request for PLM
(b) I'd like separate Device Info messages in case they diverge, which seems like a distinct possibility.

Patchset 1 is what landed yesterday.

This is a reland of 1e920b32
Original change's description:
> Adding device memory in kb to the client config request
>
> pingback will also have this information
>
> Bug: 793373
> Change-Id: I0c999c35b5e968f6b2e19696a08a722b3399d0d9
> Reviewed-on: https://chromium-review.googlesource.com/823176
> Reviewed-by: Tarun Bansal <tbansal@chromium.org>
> Commit-Queue: Ryan Sturm <ryansturm@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#524203}

Bug: 793373
Change-Id: I4d3f6854b3b28c5c412388e27b0851e767e5f8b4
Reviewed-on: https://chromium-review.googlesource.com/830133Reviewed-by: Doug Arnett <dougarnett@chromium.org>
Commit-Queue: Ryan Sturm <ryansturm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524441}

Disabled this feature for unit test which tests old code.

Bug: 787943
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: I2aba8bcca42197bc18b390181099ba664f171646
Reviewed-on: https://chromium-review.googlesource.com/828284Reviewed-by: Gregory Chatzinoff <gchatz@chromium.org>
Commit-Queue: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524440}

It appears using external process to write to a file we hold an open handle for
isn't 100% reliable (I suspect we need an fsync somewhere or maybe gsutil is
doing 'mv' somewhere and writes to another inode, or something like that).

Reopening the file before reading from it fixes the bug, at least locally for
me.

R=scottmg@chromium.org, kbr@chromium.org
BUG=795330

Change-Id: I498540ec62439c02243b84a5577c4b225ba5e1f3
Reviewed-on: https://chromium-review.googlesource.com/830257
Commit-Queue: Sergey Ulanov <sergeyu@chromium.org>
Reviewed-by: Sergey Ulanov <sergeyu@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524439}

This patch adds the following dumps in v8 memory dump provider:
- v8/isolate/contexts/detached_context
- v8/isolate/contexts/native_context
Both dumps contain an "object_count" scalar value.

The value of detached_context is the number of contexts that were
detached (due to iframe navigation or removal) and not yet garbage
collected. This number being non-zero indicates potential memory leak.

The value of native_context is the number of the top-level contexts
created for the main window and iframes. Increase of this number
over time indicates a memory leak.

Bug: 793789
Change-Id: I4753454747c398fac4fc153fcccb1288d28f2a2d
Reviewed-on: https://chromium-review.googlesource.com/822336
Commit-Queue: Ulan Degenbaev <ulan@chromium.org>
Reviewed-by: Ross McIlroy <rmcilroy@chromium.org>
Reviewed-by: Primiano Tucci <primiano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524438}

This CL decreases the bottom padding of the In-Product Help bubbles for
Contextual Search, to overlap the panel, as per UI Review's comment.

Bug: 794013
Change-Id: I607f5ea31f3cea0cbd370b9a3b19fddd6b8db385
Reviewed-on: https://chromium-review.googlesource.com/829879
Commit-Queue: Theresa <twellington@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524437}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/eaa72a5e..7be4ef7e

Please follow these instructions for assigning/CC'ing issues:
https://github.com/v8/v8/wiki/Triaging%20issues

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,machenbach@chromium.org,kozyatinskiy@chromium.org,sergiyb@chromium.org

Change-Id: I54a79e84fd83c9641d6de2b957832bf8b6b739dd
Reviewed-on: https://chromium-review.googlesource.com/830113Reviewed-by: v8 autoroll <v8-autoroll@chromium.org>
Commit-Queue: v8 autoroll <v8-autoroll@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524436}

Bug: 
Change-Id: Iec0429a3149ee17ca53b60224684e4dc3e6bbf26
Reviewed-on: https://chromium-review.googlesource.com/828442
Commit-Queue: Jared Saul <jsaul@google.com>
Reviewed-by: Mathieu Perreault <mathp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524435}

21ece16c added support for using
the frame duration metadata in the muxed stream, but if the frame
timestamp is already int64_t::max(), computing the end timestamp
based on frame time + duration yields int64_t::max() so we can
end up with a duration of zero.

This updates the conditional to skip frame duration metadata when
we don't have a valid frame duration after the calculation.

BUG=793550
TEST=new unittest

Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: I5bb728f18fbfba7df326b44f7b6159f2395a3fb5
Reviewed-on: https://chromium-review.googlesource.com/828287Reviewed-by: Thomas Guilbert <tguilbert@chromium.org>
Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524434}

This CL enables the sharing of non-HTTPS canonical URLs if the
display URL is HTTPS, due to a requirements change. It also
updates the logging to treat HTTP canonical URLs as a success
case.

Bug: 794768
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: I741949980f2d6d804a673ac82d950cdf735021df
Reviewed-on: https://chromium-review.googlesource.com/826051Reviewed-by: Peter Lee <pkl@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Gregory Chatzinoff <gchatz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524433}

Because some intercepts run before the main binary is bound and
initialized, they cannot be instrumented on X64. This is because
the shadow memory is dynamically allocated, and so won't be available
until some time during or after binding.

Bug: 783296
Change-Id: I93b0bd81d325a452205351059bc6ba013618bb99
Reviewed-on: https://chromium-review.googlesource.com/825782
Commit-Queue: Reid Kleckner <rnk@chromium.org>
Reviewed-by: Reid Kleckner <rnk@chromium.org>
Reviewed-by: Will Harris <wfh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524432}

This reverts commit 73722a14.

Reason for revert: Breaking the Linux x64 build
https://ci.chromium.org/buildbot/chromium/Linux%20x64/55031

Original change's description:
> Remove navigation start observing from DataUseAscriber
> 
> There's no reason to PostTask a bunch of data to the IO thread to do a
> no-op method.
> 
> This CL should change no behavior.
> 
> Bug: 792524
> Change-Id: Ia0f88da99c72fa3369b164a2fd25352f77d13544
> Reviewed-on: https://chromium-review.googlesource.com/827980
> Reviewed-by: rajendrant <rajendrant@chromium.org>
> Commit-Queue: rajendrant <rajendrant@chromium.org>
> Commit-Queue: Charlie Harrison <csharrison@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#524424}

TBR=csharrison@chromium.org,rajendrant@chromium.org

Change-Id: I00a16f8e2ee77b767f4289ad01ca4a05c711fdc9
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 792524
Reviewed-on: https://chromium-review.googlesource.com/830473Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524431}

In VR, we change the dip scale of the WebContents, but cannot properly
change the dip scale of Java UI because doing so would require
reinflating said java UI.

This leads to problems when determining the offset applied by the
top/bottom controls. RenderWidgetHostViewAndroid previously converted
the shown ratio of the controls to pixel values using the dip scale
of the WebContents, while ChromeFullscreenManager converted the control
height to pixels using the Java UI dpr. It then treated a mismatch
between these two values as the control container being visible, even
if the shown ratio was 0.

This CL changes the FullscreenManager to always apply fully-hidden
control offsets while in VR since the controls will be hidden anyways.

Bug: 793430
Change-Id: If18aa601ed51ea91cef6b83060972d216a8cd6a9
Reviewed-on: https://chromium-review.googlesource.com/818116
Commit-Queue: Michael Thiessen <mthiesse@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524430}

Bug: 795089
Change-Id: I7772621479504e5797c579f6d45315f836d5bceb
Reviewed-on: https://chromium-review.googlesource.com/827809Reviewed-by: Steven Holte <holte@chromium.org>
Reviewed-by: Matt Mueller <mattm@chromium.org>
Commit-Queue: David Benjamin <davidben@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524429}

This reverts commit 12dca865.

Reason for revert: crbug.com/795223

Original change's description:
> Fix Windows touchpad lagging in first tab
>
> Currently the receiving of WM_MOUSEWHEEL messages lags when we open a
> URL on a new window until we resize. The issue was introduced by
> r384698. That CL change wait for MOUSE_EVENT to wait for SENDMESSAGE
> in MessagePumpForUI::WaitForWork to optimize the GPU thread. But the
> GPU thread does not use MessagePumpForUI anymore so it should be OK to
> just remove that code.
>
> The updated version of Chrome was tested to make sure that the hangs
> that were occasionally seen when using chrome://tracing are still gone.
>
> After this CL chaopeng@ need to monitor to make sure that the crash
> rate not increase.
>
> Bug: 713907, 596190
> Change-Id: I7545a867de4851acd4e57c9b8c7a3dd05def1dd8
> Reviewed-on: https://chromium-review.googlesource.com/809829
> Commit-Queue: Jianpeng Chao <chaopeng@chromium.org>
> Reviewed-by: Bruce Dawson <brucedawson@chromium.org>
> Reviewed-by: Lei Zhang <thestig@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#523689}

TBR=thestig@chromium.org,brucedawson@chromium.org,chaopeng@chromium.org

# Not skipping CQ checks because original CL landed > 1 day ago.

Bug: 713907, 596190, 795223
Change-Id: I3f53fd77e7a6545cd214444cac46709cff0142c9
Reviewed-on: https://chromium-review.googlesource.com/830174
Commit-Queue: Jianpeng Chao <chaopeng@chromium.org>
Reviewed-by: Jianpeng Chao <chaopeng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524428}

In order to experiment with different deadlines on different machines,
this CL introduces a command line flag to set the default deadline to
synchronize.

Bug: 672962
TBR: sky@chromium.org for services/ui.
Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel
Change-Id: I58e8fd8431c439bca35ca0a3cb400046bf0dc2b6
Reviewed-on: https://chromium-review.googlesource.com/828123
Commit-Queue: Fady Samuel <fsamuel@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524427}

Ranker also takes care of logging and deals with field trials internally.

Bug: 786472, 778468
Change-Id: Ie583616643ab8ad169df4739a4a18b81a950553f
Reviewed-on: https://chromium-review.googlesource.com/788331
Commit-Queue: Philippe Hamel <hamelphi@chromium.org>
Reviewed-by: Roger McFarlane <rogerm@chromium.org>
Reviewed-by: Donn Denman <donnd@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524426}

P2PSocketDispatcherHost is supposed to update network list even
when the system is offline (i.e. after last NIC is brought down).

Bug: 789125
Change-Id: Id732ca2e35f7ea435bc960fd37a2656b152fac32
Reviewed-on: https://chromium-review.googlesource.com/802237Reviewed-by: Paul Jensen <pauljensen@chromium.org>
Commit-Queue: Sergey Ulanov <sergeyu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524425}

There's no reason to PostTask a bunch of data to the IO thread to do a
no-op method.

This CL should change no behavior.

Bug: 792524
Change-Id: Ia0f88da99c72fa3369b164a2fd25352f77d13544
Reviewed-on: https://chromium-review.googlesource.com/827980Reviewed-by: rajendrant <rajendrant@chromium.org>
Commit-Queue: rajendrant <rajendrant@chromium.org>
Commit-Queue: Charlie Harrison <csharrison@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524424}

This reverts commit a8a1b79e.

Reason for revert: Failures on Linux MSan Tests buildbot:
https://uberchromegw.corp.google.com/i/chromium.memory/builders/Linux%20MSan%20Tests

Original change's description:
> Network Error Logging: Ignore Reporting API upload requests
> 
> Right now, the ReportingUploader cancels requests once the headers are
> received, which causes the requests to fail with ERR_ABORTED, which
> triggers a NEL report.
> 
> This CL breaks that loop by attaching user data to upload requests and
> ignoring ERR_ABORTED errors stemming from them.
> 
> TBR=mkwst@chromium.org
> 
> Bug: 793392
> Change-Id: Id26516533ec0e7531797717526b015c56a742c1b
> Reviewed-on: https://chromium-review.googlesource.com/817553
> Commit-Queue: Julia Tuttle <juliatuttle@chromium.org>
> Reviewed-by: Miriam Gershenson <mgersh@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#524390}

TBR=mgersh@chromium.org,juliatuttle@chromium.org

Change-Id: I3e86f06bed769481a2ec6bdec109bdd590493ddc
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 793392
Reviewed-on: https://chromium-review.googlesource.com/830353Reviewed-by: Mohsen Izadi <mohsen@chromium.org>
Commit-Queue: Mohsen Izadi <mohsen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524423}

Increases usage of const where appropriate in
SourceBufferRange{,ByDts,ByPts} classes. I found and am fixing this while
working on patches to fix bug 791095.

BUG=791095

Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: If8d70f80e36462fce62451a3a189485bb9774eef
Reviewed-on: https://chromium-review.googlesource.com/825965Reviewed-by: Dan Sanders <sandersd@chromium.org>
Commit-Queue: Matthew Wolenetz <wolenetz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524422}

This change modifies the U2F BLE UUIDs to have extern linkage and
renames them to comply with the style guide naming conventions for
constants.

Bug: 763303
Change-Id: Ica2cb8f62c83d3a2fdcb4cdfc265735675e9e6af
Reviewed-on: https://chromium-review.googlesource.com/829175Reviewed-by: Reilly Grant <reillyg@chromium.org>
Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524421}