GitLab

Revert of Roll internal Google Play Services (Chromium part) (patchset #3 id:40001 of https://codereview.chromium.org/2063703004/ )

Reason for revert:
downstream part broke

Original issue's description:
> Roll internal Google Play Services (Chromium part)
>
> BUG=613768
>
> Committed: https://crrev.com/27d98c86363d66c877e8ca29c1d34e3578eaa179
> Cr-Commit-Position: refs/heads/master@{#400736}

TBR=agrieve@chromium.org,mariakhomenko@chromium.org,jbudorick@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=613768

Review-Url: https://codereview.chromium.org/2085723002
Cr-Commit-Position: refs/heads/master@{#400754}

removed

BUG=None

Review-Url: https://codereview.chromium.org/2068203002
Cr-Commit-Position: refs/heads/master@{#400753}

Parse 'filter' in the same way as '-webkit-filter', and make the latter
an alias of the former.
For SVG content, only the "url(...)" function is allowed still, with the
exception of the outermost <svg> (LayoutSVGRoot), since that "has a box".

Update tests to use 'filter' where reasonable and applicable.

Intent to Ship: https://groups.google.com/a/chromium.org/d/topic/blink-dev/ZVT2kxuFMaA/discussion

Based on https://codereview.chromium.org/1987943002 by noel@chromium.org.

BUG=613441,618160,550249,535786,244295,109224

Review-Url: https://codereview.chromium.org/2065593002
Cr-Commit-Position: refs/heads/master@{#400752}

https://chromium.googlesource.com/skia.git/+log/1a48e13303ec..d7ec12e41cce

$ git log 1a48e1330..d7ec12e41 --date=short --no-merges --format='%ad %ae %s'
2016-06-20 reed assert that non-empty clips have non-empty bounds

CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
TBR=brianosman@google.com

Review-Url: https://codereview.chromium.org/2087563002
Cr-Commit-Position: refs/heads/master@{#400751}

BUG=620406
TEST=covered by unit test, manual

Review-Url: https://codereview.chromium.org/2071423003
Cr-Commit-Position: refs/heads/master@{#400750}

This class observes redirects using WebStateObserver rather than the
net stack, and can be used by both KIF and EG tests.

BUG=589968

Review-Url: https://codereview.chromium.org/2048123002
Cr-Commit-Position: refs/heads/master@{#400749}

The PRESUBMIT rule makes sure that files involving IPC are covered
by the appropriate per-file rules. See https://goo.gl/NRiIPv for
other alternatives that were considered (e.g. why not recursive
per-file rules?).

BUG=611905
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel

Review-Url: https://codereview.chromium.org/2070483002
Cr-Commit-Position: refs/heads/master@{#400748}

Prior to this if you have previously ever launched the tabbed
mode of Chrome, clicking on the back button of an elderberry
tab would refocus Chrome instead of the app that launched it
(only for versions launched with NEW_TASK).

BUG=582539

Review-Url: https://codereview.chromium.org/2077133002
Cr-Commit-Position: refs/heads/master@{#400747}

Remove the stub version of DeviceDataManager that is created in the
browser and ash processes when running under mash. The stub version
never has any input-device information because the real
DeviceDataManager is in the mus process.

Create InputDeviceClient inside ash and chrome which connects to mus and
receives input-device updates via Mojo IPC.

The mus process starts InputDeviceServer to listen for observers and
update them when new input-device information is available.

BUG=601981

Review-Url: https://codereview.chromium.org/2058853002
Cr-Commit-Position: refs/heads/master@{#400746}

https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/b03df26b6d71..e266d492515c

$ git log b03df26b6..e266d4925 --date=short --no-merges --format='%ad %ae %s'

TBR=catapult-sheriff@chromium.org

Review-Url: https://codereview.chromium.org/2086613002
Cr-Commit-Position: refs/heads/master@{#400745}

Re-land of https://codereview.chromium.org/2076083003/ but disable test for now
due to revert in https://codereview.chromium.org/2082563002/

BUG=620370
R=groby@chromium.org,dbeam@chromium.org

Review-Url: https://codereview.chromium.org/2083603003
Cr-Commit-Position: refs/heads/master@{#400744}

BUG=None

Review-Url: https://codereview.chromium.org/2079393002
Cr-Commit-Position: refs/heads/master@{#400743}

Adding gRPC was approved by Chrome Eng Review, as long as it is used only by
Blimp, which we plan to enforce by fetching it only on Linux, setting up
visibility rules in BUILD.gn files, and checkdeps.

gRPC was approved by open-source-third-party-reviews@google.com.

BUG=618889

Review-Url: https://codereview.chromium.org/2057883002
Cr-Commit-Position: refs/heads/master@{#400742}

This pulls in some strings needed for ARC++ bluetooth.

BUG=b:29268565
TEST=gclient sync, make

Review-Url: https://codereview.chromium.org/2073273002
Cr-Commit-Position: refs/heads/master@{#400741}

Changed task manager process name prefix from 'ARC' to "App|Service|System|Receiver" for Android processes.

BUG=b/29460029
TEST=manual

Review-Url: https://codereview.chromium.org/2059483003
Cr-Commit-Position: refs/heads/master@{#400740}

Slightly adjust thresholds for these tests so that they pass on OSX
10.11.  Differences are presumably because the FFT routines have
changed slightly.

BUG=621527
TESTS=osc-negative-freq, realtimeanalyser-freq-data

Review-Url: https://codereview.chromium.org/2076423003
Cr-Commit-Position: refs/heads/master@{#400739}

This is a dependency of the status area widget which I'm trying to convert to
wm common types.

Introduce a method to the message center's delegate that allows it to
compute the parent container for a popup. This cannot be a NativeView, since
on mus a NativeView is an aura::Window, but the parent container is a mus
window.

This can't move to //ash/common yet because of system tray dependencies.

BUG=619636
TEST=ash_unittests

Review-Url: https://codereview.chromium.org/2075953003
Cr-Commit-Position: refs/heads/master@{#400738}

BUG=619006

Review-Url: https://codereview.chromium.org/2076003002
Cr-Commit-Position: refs/heads/master@{#400737}

BUG=613768

Review-Url: https://codereview.chromium.org/2063703004
Cr-Commit-Position: refs/heads/master@{#400736}

Deadlock is like this:

On main or media thread:
ARMM::GetOutputDeviceInfo [takes |lock_|]
-> AOD::GetOutputDeviceInfo -> waits for device authorization, which can be signalled on IO thread only

On IO thread:
AOD::CreateStreamOnIOThread/OnStateChanged*
-> ARMM::OnRenderError [takes |lock_|],
so OnDeviceAuthorized/OnIPCClosed will never be called and device authorization will never be signalled.

*AOD::OnDeviceAuthorized itself does not deadlock it always signals event before calling OnRenderError()

That lock in ARMM::GetOutputDeviceInfo is never needed, after all

BUG=615589

Review-Url: https://codereview.chromium.org/2085603002
Cr-Commit-Position: refs/heads/master@{#400735}

While reviewing some of the other AudioOutputDevice changes, I
noticed this class is exceedingly crufty. This removes an extra
layer and associated locking from the audio callback thread.

AudioInputDevice/AudioOutputDevice both always use synchronized
buffers now, so that option is no longer necessary. Removes the
silly ref-counting from AudioDeviceThread in favor of ownership
by an already ref counted class :)

Removes the Start/Stop API from AudioDeviceThread since it's
easier to just construct and destruct it.

BUG=none
TEST=audio plays, all unittests still pass.

Review-Url: https://codereview.chromium.org/2076793002
Cr-Commit-Position: refs/heads/master@{#400734}

https://chromium.googlesource.com/skia.git/+log/52ede1d90572..1a48e13303ec

$ git log 52ede1d90..1a48e1330 --date=short --no-merges --format='%ad %ae %s'
2016-06-20 brianosman Respect color type and gamma settings in nanobench GPU configs

CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
TBR=brianosman@google.com

Review-Url: https://codereview.chromium.org/2080823002
Cr-Commit-Position: refs/heads/master@{#400733}

The GLRenderer uses the new command buffer function
glScheduleCALayerInUseQueryCHROMIUM to determine whether textures are still in
use by the system compositor. This means that GpuMemoryBufferIds no longer need
to be plumbed through to the browser process.

BUG=608026
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel

Review-Url: https://codereview.chromium.org/2061993003
Cr-Commit-Position: refs/heads/master@{#400732}

Less copy!

BUG=None

Review-Url: https://codereview.chromium.org/2078103002
Cr-Commit-Position: refs/heads/master@{#400731}

This allows GMBs created by one instance of the GPU process to
be used with another instance. It also allows the client to
synchronize creation of one buffer with destruction of another
buffer as they are now created when imported for CHROMIUM_image.

Note: GMB factory creation of buffer from handle can be
eliminated as a follow up to this.

BUG=597932, b/29239573
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_optional_gpu_tests_rel;tryserver.chromium.mac:mac_optional_gpu_tests_rel;tryserver.chromium.win:win_optional_gpu_tests_rel

Review-Url: https://codereview.chromium.org/1837703002
Cr-Commit-Position: refs/heads/master@{#400730}

Changes: https://chromium.googlesource.com/external/webrtc/trunk/webrtc.git/+log/b0d0745..3db000e

TBR=

CQ_EXTRA_TRYBOTS=tryserver.chromium.linux:linux_chromium_archive_rel_ng;tryserver.chromium.mac:mac_chromium_archive_rel_ng
BUG=

Review-Url: https://codereview.chromium.org/2082643002
Cr-Commit-Position: refs/heads/master@{#400729}

BUG=581865

Review-Url: https://codereview.chromium.org/2084633002
Cr-Commit-Position: refs/heads/master@{#400728}

Lint is still run only within android_library/android_apk targets but resources
folders and generated resources ZIPs from direct dependencies are added to this
run. ZIPs are extracted to temporary folders during linting.

This approach requires a big rewrite of existing dependencies. Before the patch
every library that needs to reference something from R.java of the other library
has to directly depend on the resource target that generates this R.java, for
example chrome_java depended on ui_java_resources while also dependening on
ui_java. This is the only way to get R.java from ui_java_resources in
chrome_java. This causes Lint to lint ui_java_resources twice (within
chrome_java and ui_java) and may produce false positives. This patch changes
these R.java dependencies to transitives, so chrome_java only depends on ui_java
and still gets all R.java from its resources.

Only resources that are the part of the library/APK should be direct
dependencies of this library otherwise Lint will not work properly.

Resource folders/ZIPs are propagated to dependent libraries via build_config
files. Each android_resources target publishes its resource folders in its
build_config; it also writes list of resources_zips of direct dependencies which
have no own package names - these are generated resources, conceptually part of
the same target. Library/APK targets expose list of folders and ZIPs from
dependencies via their own build_config which is read by Lint.

BUG=595810

Review-Url: https://codereview.chromium.org/2062633002
Cr-Commit-Position: refs/heads/master@{#400727}

BUG=612604

Review-Url: https://codereview.chromium.org/2077083002
Cr-Commit-Position: refs/heads/master@{#400726}

https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/91953db7ae2b..b03df26b6d71

$ git log 91953db7a..b03df26b6 --date=short --no-merges --format='%ad %ae %s'

TBR=catapult-sheriff@chromium.org

Review-Url: https://codereview.chromium.org/2084533003
Cr-Commit-Position: refs/heads/master@{#400725}

fixed issue 606368: early return from ProcessAcceleratorWhileMenuShowing() if chrome::IsRunningInMash()

BUG=606368

TEST=Start Chrome with mash. Right click on a webpage to open the context menu. Trigger a keyboard event by pressing the Ctrl key. Chrome should not crash.

Review-Url: https://codereview.chromium.org/2073783003
Cr-Commit-Position: refs/heads/master@{#400724}

Followup to https://codereview.chromium.org/2075153002

BUG=612337, 612563, 257943

Review-Url: https://codereview.chromium.org/2073393002
Cr-Commit-Position: refs/heads/master@{#400723}

With a few experiments making wrapper tracing incremental we realized we need to
introduce write barriers anyway, and having script wrappables in the marking
deque would make write barriers in non-script-wrappable classes complicated.
This cl changes the marking deque to hold generic raw pointers + needed function
pointers.

We need one function to do the marking and adding members to the deque, and we
need one function for getting the header, for correct invalidation of headers
when oilpan gc runs during wrapper tracing. During invalidation, we also have to
remove headers of deleted objects from m_headersToUnmark.

We also had to revert to the previous implementation, where there is
WrapperTypeInfo.traceWrappers instead of WraperTypeInfo.getHeapObjectHeader.
Before we marked the object, and then added it to the marking deque for
expansion. Now we add object to the marking deque, and marking and expansion is
done in the one incremental step.

LOG=no
BUG=468240

Review-Url: https://codereview.chromium.org/2084513002
Cr-Commit-Position: refs/heads/master@{#400722}

This pulls in two minor bug fixes and a new feature: support for
sharding via --shard-index and --total-shards.

R=nednguyen@chromium.org
BUG=620959

Review-Url: https://codereview.chromium.org/2077273002
Cr-Commit-Position: refs/heads/master@{#400721}

BUG=621141

Review-Url: https://codereview.chromium.org/2087473002
Cr-Commit-Position: refs/heads/master@{#400720}

The pingback is modulated by a float that is contained in the client
config protobuf. By default, the pingback is disabled, and the client
config can vary the probability between zero and one.

BUG=616805

Review-Url: https://codereview.chromium.org/2076663004
Cr-Commit-Position: refs/heads/master@{#400719}

Based on https://codereview.chromium.org/2044223004 by littledan@chromium.org

BUG=v8:4483, 621515
R=littledan@chromium.org, yangguo@chromium.org, dgozman@chromium.org, pfeldman@chromium.org

Review-Url: https://codereview.chromium.org/2071483002
Cr-Commit-Position: refs/heads/master@{#400718}

BUG=

Review-Url: https://codereview.chromium.org/2071983002
Cr-Commit-Position: refs/heads/master@{#400717}

We obviously want to bound the memory usage of hpack. http2 has an in-protocol
mechanism for this: send SETTINGS_MAX_HEADER_LIST_SIZE to the peer with a
suitable value. With the default 16 KB limit on header list size, the limit
removed by this CL is redundant. If we ever increased the
SETTINGS_MAX_HEADER_LIST_SIZE value then we are still limited to whatever we
set that to.

This CL lands server change 123307298 by rjshade.

BUG=488484

Review-Url: https://codereview.chromium.org/2026593002
Cr-Commit-Position: refs/heads/master@{#400716}

BUG=596401

Review-Url: https://codereview.chromium.org/2080763002
Cr-Commit-Position: refs/heads/master@{#400715}