GitLab

The NetworkConnectionTracker instance currently lives in
g_browser_process, but we need the tracker in //content, which can't
access //chrome. This adds a static getter in
network_service_instance.h, which can be used in //content.

Bug: 821009
Cq-Include-Trybots: luci.chromium.try:linux_mojo
Change-Id: Iaedb89cf2d27f75e0b896d7fd7389ceab3fe4682
Reviewed-on: https://chromium-review.googlesource.com/1162888Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Commit-Queue: Robbie McElrath <rmcelrath@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581697}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/94ec5e5e83b9..e41df534852b


git log 94ec5e5e83b9..e41df534852b --date=short --no-merges --format='%ad %ae %s'
2018-08-08 dgarrett@google.com chromeos_config: Add eve-chrome-pfq.


Created with:
  gclient setdep -r src/third_party/chromite@e41df534852b

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: I0dee8a6e981cbbb712efb0557e00979f8aebecb7
Reviewed-on: https://chromium-review.googlesource.com/1167822Reviewed-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@{#581696}

The set_bounds request, which supersedes set_window_geometry, allows
the client to specify a target display such that window bounds are
expressed in display rather than screen coordinates.

Bug: b:77972398
Test: None
Change-Id: I6c229e72bf2160b86067e768b31f1ac5148d4aff
Reviewed-on: https://chromium-review.googlesource.com/1164553
Commit-Queue: Dominik Laskowski <domlaskowski@chromium.org>
Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581695}

This change creates a service for hosting desktop VR devices so
they can be run at the appropriate level of sandboxing required to ship.

The browser process will consume this service to enable WebVR/WebXR
support to ship on Windows.

Currently the service runs in a utility process with no sandbox. A
subsequent change will enable an appropriate sandbox behind a flag to
enable testing.

Bug: 795510
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:linux_vr;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Change-Id: I5d602f4db91bcd1ddb5a3edf535f90e126004d4a
Reviewed-on: https://chromium-review.googlesource.com/1155754Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Commit-Queue: Bill Orr <billorr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581694}

Bug: 367595
Change-Id: I940257b49fce15310dc680c0b7c283f48ae681cf
Reviewed-on: https://chromium-review.googlesource.com/1164580Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Reviewed-by: agrieve <agrieve@chromium.org>
Commit-Queue: Wei-Yin Chen (陳威尹) <wychen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581693}

This reverts commit f86a758d.

Reason for revert: Breaks x86 bots
https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Android%20x64%20Builder%20%28dbg%29/28950

Original change's description:
> [vr] Make VR Java android_library and separate VR JNI registration
> 
> This CL does two things:
> 
> - In order to move VR Java code into its own module move the code into a
>   separate android_library target.
> 
> - As a result of the separate library target we may miss making the VR
>   JNI registrations (in case VR moves out of chrome_public_apk). Thus,
>   separate the JNI registration generation for VR and register VR JNI
>   calls in VR code.
> 
> Bug: 862694
> Change-Id: I2b78cea7b30725d5f2b51afbcac1a6add555f355
> Reviewed-on: https://chromium-review.googlesource.com/1158715
> Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org>
> Reviewed-by: agrieve <agrieve@chromium.org>
> Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#581576}

TBR=mthiesse@chromium.org,agrieve@chromium.org,tiborg@chromium.org

Change-Id: Iccac3c8981c21fe105799e045f1629dbd99fb7c6
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 862694
Reviewed-on: https://chromium-review.googlesource.com/1168043Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Ted Choc <tedchoc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581692}

BUG=800033

Change-Id: I0007ae432782e4222f1eed4aad03259a9e25a784
Reviewed-on: https://chromium-review.googlesource.com/1167556Reviewed-by: Theresa <twellington@chromium.org>
Commit-Queue: Ted Choc <tedchoc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581691}

Bug: 864705
Change-Id: I8ebce1fd5911f90b8313a27f9d9e11e229ec0b6b
Reviewed-on: https://chromium-review.googlesource.com/1162757
Commit-Queue: Vlad Tsyrklevich <vtsyrklevich@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581690}

This change drops GeoTrust from the pinning set and adds GIA G3 and
another GTS intermediate, 1O1. GIA G2 remains in the pinning set because
it's still valid until the end of 2018 and some Google properties
may be using it. But the vast majority of Google properties are now
using GlobalSign R2 and the GIA G3 and 1O1 intermediates.

Change-Id: Ia4765525f419e654295199aa654e25c955affb47
Reviewed-on: https://chromium-review.googlesource.com/1166224Reviewed-by: Ryan Sleevi <rsleevi@chromium.org>
Commit-Queue: Adam Langley <agl@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581689}

Background:
There are several corner cases that home launcher is not shown:
1. Drag app list from shelf, meanwhile switch to tablet mode.
2. Drag app list to shelf after being opened, meanwhile switch to tablet
   mode.
3. Close app list and, during the close animation, switch to tablet
   mode.

Changes:
1. Ignore drag event from both shelf or app list and reset dragging
   state when tablet mode is on.
2. Immediately stop close animation before reshow app list when tablet
   mode is on.

Bug: 872072,871923
Change-Id: I5bd7dae242d84e2f0a82839693fbd36930f8e613
Reviewed-on: https://chromium-review.googlesource.com/1167658Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Weidong Guo <weidongg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581688}

Previously, MediaCodecVideoDecoder would only release codec buffers
when starting a drain if it wasn't going to elide the drain itself.
However, since the drain (elided or not) is going to be followed
by a codec flush or destruction, we still invalidate any unrendered
output buffers.

While this isn't techincally required, AVDA did it and seems to
have much fewer codec hangs.

Bug: 869365
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
Change-Id: I903301950e190b64d8618b06689cbf9d184a96c9
Reviewed-on: https://chromium-review.googlesource.com/1167797Reviewed-by: Dan Sanders <sandersd@chromium.org>
Commit-Queue: Frank Liberato <liberato@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581687}

Bug: 729848
Cq-Include-Trybots: luci.chromium.try:linux_mojo
Change-Id: I47030b560c2187c6cb48217338f071400539cd08
Reviewed-on: https://chromium-review.googlesource.com/1167801Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Commit-Queue: Clark DuVall <cduvall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581686}

Enabling the experimental UI flag, chrome://flags#upcoming-ui-features,
will now enable the text suggestions touch bar.

Bug: 717553
Change-Id: Ib78dc1298d548bd3548441667ab4f46e62f3b98a
Reviewed-on: https://chromium-review.googlesource.com/1167800
Commit-Queue: Tessa Nijssen <tnijssen@google.com>
Commit-Queue: Avi Drissman <avi@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Sarah Chan <spqchan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581685}

Seems no one is using these UMAs any more, removing them

BUG=871462

Change-Id: Ifd8e4c3cb5af7dfe4866c97f1b2cdb279c4697ab
Reviewed-on: https://chromium-review.googlesource.com/1166161Reviewed-by: Jialiu Lin <jialiul@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Commit-Queue: Min Qin <qinmin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581684}

This reverts commit a173bcea.

Reason for revert: <INSERT REASONING HERE>
Still hunting chromeos dbg failures.

Original change's description:
> Reland "Always build ChromeVox as compressed js"
> 
> This reverts commit 9871f52a.
> 
> Reason for revert: <INSERT REASONING HERE>
> Was not the culprit of failing chromeos dbg SpokenFeedbackTests.
> 
> 
> Original change's description:
> > Revert "Always build ChromeVox as compressed js"
> > 
> > This reverts commit 725ceeda.
> > 
> > Reason for revert: Broke lots of tests on https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/linux-chromeos-dbg
> > 
> > chromevox test:
> > BackgroundTest.NavigationEscapesEdit
> > 
> > interactive_ui_tests
> > TestAsNormalAndGuestUser/SpokenFeedbackTest.OverviewMode/0
> > TestAsNormalAndGuestUser/SpokenFeedbackTest.OverviewMode/1
> > TestAsNormalAndGuestUser/SpokenFeedbackTest.OpenStatusTray/0
> > TestAsNormalAndGuestUser/SpokenFeedbackTest.OpenStatusTray/1
> > TestAsNormalAndGuestUser/SpokenFeedbackTest.ChromeVoxNextTabRecovery/0
> > TestAsNormalAndGuestUser/SpokenFeedbackTest.ChromeVoxShiftSearch/0
> > TestAsNormalAndGuestUser/SpokenFeedbackTest.FocusToolbar/1
> > TestAsNormalAndGuestUser/SpokenFeedbackTest.ChromeVoxShiftSearch/1
> > TestAsNormalAndGuestUser/SpokenFeedbackTest.ChromeVoxNextTabRecovery/1
> > LoggedInSpokenFeedbackTest.KeyboardShortcutViewer
> > TestAsNormalAndGuestUser/SpokenFeedbackTest.FocusToolbar/0
> > TestAsNormalAndGuestUser/SpokenFeedbackTest.FocusShelf/0
> > TestAsNormalAndGuestUser/SpokenFeedbackTest.FocusShelf/1
> > GuestSpokenFeedbackTest.FocusToolbar
> > 
> > 
> > Original change's description:
> > > Always build ChromeVox as compressed js
> > > 
> > > ChromeVox can be run as both compressed (minified js) and uncompressed. The latter facilitates faster development.
> > > 
> > > It appears that in some instances, with the kevin board in particular, gn evaluates the ChromeVox build file incorrectly.
> > > 
> > > The end result is we end up with both uncompressed and compressed js files in ChromeVox leading to duplicate js objects.
> > > 
> > > Bug: 868579
> > > Test: clean build for
> > > 1. prior to this patch
> > > 2. after this patch
> > > 
> > > Before each deployment, ensure we delete the chromevox folder on-device. This should be equilvanet to a new image.
> > > 
> > > Change-Id: I64cf826bda9239edc7764ba598bfed6dd0572d56
> > > Reviewed-on: https://chromium-review.googlesource.com/1165787
> > > Reviewed-by: Alex Newcomer <newcomer@chromium.org>
> > > Commit-Queue: David Tseng <dtseng@chromium.org>
> > > Cr-Commit-Position: refs/heads/master@{#581325}
> > 
> > TBR=dtseng@chromium.org,newcomer@chromium.org,oxyflush@google.com
> > 
> > Change-Id: Ifb3c2556f44b07161f491b18b49d556e364963fb
> > No-Presubmit: true
> > No-Tree-Checks: true
> > No-Try: true
> > Bug: 868579
> > Reviewed-on: https://chromium-review.googlesource.com/1167442
> > Reviewed-by: Avi Drissman <avi@chromium.org>
> > Commit-Queue: Avi Drissman <avi@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#581564}
> 
> TBR=avi@chromium.org,dtseng@chromium.org,newcomer@chromium.org,oxyflush@google.com
> 
> Change-Id: Ifb1ec50fd3cbaa1e0b97a5b5cfdb7b3b9712b353
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Bug: 868579
> Reviewed-on: https://chromium-review.googlesource.com/1167604
> Reviewed-by: David Tseng <dtseng@chromium.org>
> Commit-Queue: David Tseng <dtseng@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#581609}

TBR=avi@chromium.org,dtseng@chromium.org,newcomer@chromium.org,oxyflush@google.com

Change-Id: I8beec8a3003a2a7254fb987650410bd7289b4478
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 868579
Reviewed-on: https://chromium-review.googlesource.com/1168042Reviewed-by: David Tseng <dtseng@chromium.org>
Commit-Queue: David Tseng <dtseng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581683}

Instead, copy the runtime to the build dir at build time and find it there
at test time.

Matches how things work on other platforms with the asan runtime in a shared
library (mac/ios/win).

This also makes things do the right thing with a custom clang_base_path.

Bug: 872278
Change-Id: I930bd88206f973c10eb47bfd2f132e70167235f4
Reviewed-on: https://chromium-review.googlesource.com/1167465Reviewed-by: Hans Wennborg <hans@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581682}

This is needed to avoid duplicating the list of supported Perfetto
platforms everywhere, and there's additionally situations where it's
tricky to enable feature flags conditionally per platform (perf tests).
Print out an error message instead, for debugging.

R=primiano@chromium.org

Change-Id: I4bdce82c4d8d8a9bad13aec482c06c78510cb360
Reviewed-on: https://chromium-review.googlesource.com/1162758
Commit-Queue: oysteine <oysteine@chromium.org>
Reviewed-by: Primiano Tucci <primiano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581681}

Ash uses 0 - 100 while assistant uses 0.0 - 1.0 for volume. We convert
it in assistant platform volume control impl.

Bug: b/111768214
Test: None
Change-Id: I5e01c1512065e5711f7463662e4f286068599b65
Reviewed-on: https://chromium-review.googlesource.com/1166449Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Commit-Queue: Muyuan Li <muyuanli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581680}

This reverts commit 545410e6.

Reason for revert: A different fix for the initialization had already landed by now, see https://chromium-review.googlesource.com/c/chromium/src/+/1158316. I need to remove the extra initialization changes from my CL.

Original change's description:
> Reland [Media Recorder] Fix video freeze on short recording. Fix tab crash on initialize.
> 
> Patch Set 1 is the original CL that got reverted.
> Patch Set 2 fixes the reason for the revert.
> 
> Reason for the revert was a memory leak during a unit test. This was caused by
> a newly added DeleteSoon() causing the test to exist before all objects had
> been released. The fix is to add a ScopedTaskEnvironment::RunUntilIdle() at
> test teardown.
> 
> Original CL description:
> 
> Fixes an issue where VideoTrackRecorder when used in combination with
> VEAEncoder and very short recording durations (just 1 frame) would
> occasionally hold on to video frames forever, causing frame buffers
> from the buffer pool to become permanently blocked, eventually leading
> to video capture freezing.
> 
> The cause was a circular ownership that would happen if only 1 frame
> is recorded.
> 
> This CL additionally fixes a crash that could happen on initialization
> of VEAEncoder. This issue was revealed during testing of the above fix.
> Since it is not 100% if this crash was masked by the other issue, and
> would only start occurring with the above fix, I am making a fix for that
> part of this CL as well.
> 
> The cause for the crash issue was that class VEAEncoder, which uses
> RefCountedThreadSafe<>, would post an asynchronous task from its
> constructor. If this task would finish executing before the newly
> constructed instance was assigned to a scoped_refptr<> by however
> called the constructor, the instance would destroy itself, because
> of the AddRef() and subsequent Release() done by the posting and
> running of the asynchronous task.
> 
> The fix for this is to use a new method Initialize() instead of
> posting a task from the constructor.
> 
> TBR=emircan@chromium.org
> 
> Bug: 859610
> Change-Id: I120b60b4b5cdf7462e38a74b7c757af6b5e1a7d6
> Reviewed-on: https://chromium-review.googlesource.com/1167742
> Reviewed-by: Christian Fremerey <chfremer@chromium.org>
> Commit-Queue: Christian Fremerey <chfremer@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#581672}

TBR=emircan@chromium.org,chfremer@chromium.org

Change-Id: I4794d8d76b78bd1ab86860230bc01f0f20d3bd18
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 859610
Reviewed-on: https://chromium-review.googlesource.com/1167768Reviewed-by: Christian Fremerey <chfremer@chromium.org>
Commit-Queue: Christian Fremerey <chfremer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581679}

https://chromium.googlesource.com/angle/angle.git/+log/c93eeaab1526..c86c8b0cecf0


git log c93eeaab1526..c86c8b0cecf0 --date=short --no-merges --format='%ad %ae %s'
2018-08-08 jmadill@chromium.org D3D9: Use angle::Result error pattern.


Created with:
  gclient setdep -r src/third_party/angle@c86c8b0cecf0

The AutoRoll server is located here: https://angle-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.

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=ynovikov@chromium.org

Change-Id: Ifd7d79a2fab4fd8f5ccce36d8ebb8277dbd9ef4e
Reviewed-on: https://chromium-review.googlesource.com/1167584Reviewed-by: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#581678}

https://pdfium.googlesource.com/pdfium.git/+log/f90277e7f4bd..6d9897b103ae


git log f90277e7f4bd..6d9897b103ae --date=short --no-merges --format='%ad %ae %s'
2018-08-08 rharrison@chromium.org Limit size of expression list in FormCalc parser


Created with:
  gclient setdep -r src/third_party/pdfium@6d9897b103ae

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.



BUG=chromium:870385
TBR=dsinclair@chromium.org

Change-Id: Ib8c25301849b63f476191caa4b969b013dec8deb
Reviewed-on: https://chromium-review.googlesource.com/1167702Reviewed-by: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#581677}

From the stack trace of the current crash report, we are not able to
tell the gesture sequence, which makes it hard to debug.

This CL adds a CrashKeyString in TouchActionFilter, and push necessary
events into that string. When it crashes, we should be able to retrieve
the gesture sequence from that crash key.

Bug: 869375
Change-Id: Ieb7cf0839e4a062c23ec48cbaca72bd641f28a30
Reviewed-on: https://chromium-review.googlesource.com/1165586Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Commit-Queue: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581676}

There isn't a separate "classic" mode for ash anymore.

Bug: 842365
Test: ash_unittests
Change-Id: I52d758904cb0dc579e69e84c8ebd259e81aef7e2
Reviewed-on: https://chromium-review.googlesource.com/1167748Reviewed-by: Jun Mukai <mukai@chromium.org>
Commit-Queue: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581675}

This cl provides an implementation of ViewStub that inflates the view on
a background thread. It also has an implementation of AsyncViewProvider
which is basically a promise of a view to allow deferring code to run
until after the view is inflated.

Bug: 762120
Change-Id: I1f01fbfde5a2717f2a0daacd7ec6a1421f81f3c6
Reviewed-on: https://chromium-review.googlesource.com/1159226
Commit-Queue: Mohamed Heikal <mheikal@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581674}

Bug: 869570, 871948
Change-Id: I92312b385c7e38610aa92ad2e25a1b2fa0f192ff
Reviewed-on: https://chromium-review.googlesource.com/1166205Reviewed-by: Sunny Sachanandani <sunnyps@chromium.org>
Commit-Queue: ccameron <ccameron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581673}

Patch Set 1 is the original CL that got reverted.
Patch Set 2 fixes the reason for the revert.

Reason for the revert was a memory leak during a unit test. This was caused by
a newly added DeleteSoon() causing the test to exist before all objects had
been released. The fix is to add a ScopedTaskEnvironment::RunUntilIdle() at
test teardown.

Original CL description:

Fixes an issue where VideoTrackRecorder when used in combination with
VEAEncoder and very short recording durations (just 1 frame) would
occasionally hold on to video frames forever, causing frame buffers
from the buffer pool to become permanently blocked, eventually leading
to video capture freezing.

The cause was a circular ownership that would happen if only 1 frame
is recorded.

This CL additionally fixes a crash that could happen on initialization
of VEAEncoder. This issue was revealed during testing of the above fix.
Since it is not 100% if this crash was masked by the other issue, and
would only start occurring with the above fix, I am making a fix for that
part of this CL as well.

The cause for the crash issue was that class VEAEncoder, which uses
RefCountedThreadSafe<>, would post an asynchronous task from its
constructor. If this task would finish executing before the newly
constructed instance was assigned to a scoped_refptr<> by however
called the constructor, the instance would destroy itself, because
of the AddRef() and subsequent Release() done by the posting and
running of the asynchronous task.

The fix for this is to use a new method Initialize() instead of
posting a task from the constructor.

TBR=emircan@chromium.org

Bug: 859610
Change-Id: I120b60b4b5cdf7462e38a74b7c757af6b5e1a7d6
Reviewed-on: https://chromium-review.googlesource.com/1167742Reviewed-by: Christian Fremerey <chfremer@chromium.org>
Commit-Queue: Christian Fremerey <chfremer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581672}

Disable the ControllerHandlesTouchscreenGestureFling and
ControllerSendsWheelEndWhenTouchpadFlingIsOver tests, which appear to
have timing-dependent flakiness.

Bug: 836996
Change-Id: I42b7b23489b4cf2dbb2fdacf89c77bd102ac03a8
Reviewed-on: https://chromium-review.googlesource.com/1166328Reviewed-by: Sahel Sharify <sahel@chromium.org>
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Commit-Queue: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581671}

https://webrtc.googlesource.com/src.git/+log/8e5014a3925e..a837dd790d96


git log 8e5014a3925e..a837dd790d96 --date=short --no-merges --format='%ad %ae %s'
2018-08-08 aleloi@webrtc.org Reset Agc2 on analog gain changes.
2018-08-08 srte@webrtc.org Limits reported cumulative packets lost to 0.
2018-08-08 nisse@webrtc.org Fix comment on RtpVideoSender's ownership of Rtp modules.
2018-08-08 nisse@webrtc.org Change Channel::GetRtpRtcp to return only RtpRtcp, not RtpReceiver.
2018-08-08 sakal@webrtc.org Release output buffer when dropping frame in HardwareVideoDecoder.


Created with:
  gclient setdep -r src/third_party/webrtc@a837dd790d96

The AutoRoll server is located here: https://webrtc-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.

CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng
TBR=webrtc-chromium-sheriffs-robots@google.com

Change-Id: I072b7a9f02e84dcb8d21d80ffef97ac18561cb59
Reviewed-on: https://chromium-review.googlesource.com/1167583Reviewed-by: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#581670}

When there are nested oopifs, an out-of-process subframe may have
nested out-of-process subframe of its own. In such cases, we
should link custom data field of PaintRecord to its place-holder
SkPicture as well. This CL adds such processing in subframe
printing.

BUG=853942

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Ib81e376839be8bd28258fd92ba22e29da566548d
Reviewed-on: https://chromium-review.googlesource.com/1163829
Commit-Queue: Wei Li <weili@chromium.org>
Reviewed-by: enne <enne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581669}

The interaction between & and std::move() caused this DCHECK to be
hit on Windows: https://cs.chromium.org/chromium/src/net/server/http_server.cc?q=http_server.cc&dr&l=61

Change-Id: I5899b9030e4eaae872f9663d852634edf0087a0f
Reviewed-on: https://chromium-review.googlesource.com/1167559Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Commit-Queue: Fabio Tirelo <ftirelo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581668}

Due to a bug (https://crbug.com/750512) even if the lower layer returned
null, a session description was surfaced from content to blink with
default sdp and type "".

With this CL, null is surfaced as a blink::WebRTCSessionDescription
whose IsNull() returns true. blink::RTCPeerConnection already correctly
handles this case and returns null for localDescription and
remoteDescription.

WPT expectations updated accordingly.

Bug: 750512
Change-Id: I51737f55165e767a5a1d1e9c519af9a535b5de70
Reviewed-on: https://chromium-review.googlesource.com/1167055
Commit-Queue: Henrik Boström <hbos@chromium.org>
Reviewed-by: Florent Castelli <orphis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581667}

This is a heuristic intended to allow the toolbars to be shown when
navigating to an AMP page, assuming that these navigations are coupled
with URL-changing history state updates (i.e. navigating to AMP pages
from the Google search results page).  This is likely too broad of a
condition, and should be updated to include a more robust heuristic that
checks the DOM of loaded iframes for AMP markup.

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

NSS 3.30 introduced PK11_HasAttributeSet, which allows callers
to query the PKCS#11 tokens for given PKCS#11 attributes. The
same release also added attributes to the default NSS trust
store indicating they were part of the default store - i.e.
they were not added by admins.

Prior to NSS 3.30, the only way for determining 'default'
trust was to query the token and slot name, as nssckbi.so,
the read-only default trust store. Unfortunately, other
libraries, such as p11-kit-trust, decided to emulate that, but
also included administrative and user-added roots in the store,
resulting in user-added roots being subjected to public trust
requirements.

While the issue is in p11-kit-trust not observing the
semantics that NSS relied on (e.g. by adding themselves as a
separate token/slot, or preserving the 'default-only' nature
of the .so), work around this by adding a short-circuit when
the PK11_HasAttributeSet symbol is resolved.

This short-circuit can be reasoned about as safe, as the other
change in M68 - to use GetNetTrustAnchorHistogramForSPKI -
ensures that publicly trusted roots are recognized as such. This
path only handles the "old Chrome, new trust store" scenario,
which is quite rare.

Bug: 868811
Change-Id: I21989ee3e0c59dd9bfd199a6b13334637f0772c5
Reviewed-on: https://chromium-review.googlesource.com/1167479Reviewed-by: Eric Roman <eroman@chromium.org>
Commit-Queue: Ryan Sleevi <rsleevi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581665}

While this does not fix the complete set of synchronization issues, it does result in smooth playback on my Linux machine.

Bug: 819914
Change-Id: I66f78e2d22d276c8dc2c67cb96626aab42ce0efe
Reviewed-on: https://chromium-review.googlesource.com/1162928
Commit-Queue: Dan Sanders <sandersd@chromium.org>
Reviewed-by: Daniele Castagna <dcastagna@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581664}

Using Googletests's testing::_ eliminates the need to separate
mock methods into the actual and a private mock method solely
for the purpose of ignoring untested parameters.

Leaving two methods unchanged as the override test method
does (or wants to do) extra work.

This is a cleanup CL and is only related to issue 840390 in that
it factors some of the cleanup done in that CL to simplify that
review.

Bug: 840390
Change-Id: Iaaba1d1d259df621fee0d9b98173f7f42ad261a9
Reviewed-on: https://chromium-review.googlesource.com/1163902Reviewed-by: Wei Li <weili@chromium.org>
Commit-Queue: Chris Mumford <cmumford@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581663}

Also ProcessControllerInput is now private to RenderLoop, to reduce the
risk of updating the controller more than once per frame.

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:linux_vr;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Change-Id: Iae8b797027d7be147f2139276acd3b6e1264a4fe
Reviewed-on: https://chromium-review.googlesource.com/1165834Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Commit-Queue: Aldo Culquicondor <acondor@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581662}

This is an update per request from the favicon service owners.

Bug: 870583
Change-Id: I93b466ee704ac0eb3b0c2d90b5ba40c639b89a55
Reviewed-on: https://chromium-review.googlesource.com/1163836Reviewed-by: Mikel Astiz <mastiz@chromium.org>
Commit-Queue: Filip Gorski <fgorski@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581661}

When a user selects a suggestion, the editing word range is selected
for replacement with the suggestion's text. Currently, that selection
causes a call to WebContentsObserver::DidChangeTextSelection() which
updates the TextSuggestionsTouchBarController's text selection to the
editing word range. This change in text selection modifies the
appearance of the touch bar which is undesired.

The change in text selection for replacing the editing word should be
ignored by the TextSuggestionsTouchBarController. A variable,
|shouldIgnoreReplacementSelection_|, is set to YES when the
TextSuggestionsTouchBarController modifies the current text selection
to replace the editing word. When the that text selection update
reaches TextSuggestionsTouchBarController, the selection will be
ignored and |shouldIgnoreReplacementSelection_| will be reset to NO.
This fixes the behavior where the touch bar appearance changes before
showing suggestions post-replacement.

A browser test was added,
TextSuggestionsTouchBarControllerTest.IgnoreReplacementSelection, to
test that a text selection is only ignored when necessary and that
other selection updates are not ignored.

Bug: 717553
Change-Id: Ib442d98b96e499acd73856399bcd89adf0f9c1d9
Reviewed-on: https://chromium-review.googlesource.com/1164167Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Sarah Chan <spqchan@chromium.org>
Commit-Queue: Tessa Nijssen <tnijssen@google.com>
Cr-Commit-Position: refs/heads/master@{#581660}

Bug: 776589, 715630
Cq-Include-Trybots: luci.chromium.try:linux_mojo
Change-Id: I5a9bb9c857e3ec68df8c8ef1133cb418071f1e41
Reviewed-on: https://chromium-review.googlesource.com/1167553Reviewed-by: Min Qin <qinmin@chromium.org>
Commit-Queue: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581659}

BUG=851090
TBR=hubbe@chromium.org
NOTRY=true

Change-Id: I445f06df0d88d0f840d1d82829aa2d4cac92fa67
Reviewed-on: https://chromium-review.googlesource.com/1167909
Commit-Queue: Avi Drissman <avi@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581658}