GitLab

Also use a new method for callback chaining, which is slightly less
flexible but much less "callback hell".

BUG=377232
R=armansito@chromium.org

Review URL: https://codereview.chromium.org/628983003

Cr-Commit-Position: refs/heads/master@{#299390}

Mechanical change that adds instrumentation required to locate the source of jankiness (i.e. a long-running fragment of code executed as a part of the task that causes jank) in the code. See the bug for details on what kind of jank we are after.
A number of similar CLs were landed, and none of them caused issues. The code of the instrumentation is highly optimized and is not expected to affect performance. The code simply creates a diagnostic task which is identical to ones created by PostTask or IPC message handlers.
Landing as TBR since this is a mechanical, safe and temporary change.

This CL specifically instruments some presumably most popular callbacks invoked by “callback.Run(result);” line in TCPClientSocket::DidCompleteReadWrite.

BUG=418183
TBR=asanka@chromium.org

Review URL: https://codereview.chromium.org/652853002

Cr-Commit-Position: refs/heads/master@{#299389}

This causes a deadlock, so it's not usable. Getting rid of the window at least allows --in-process-gpu to work.

BUG=273220

Review URL: https://codereview.chromium.org/649863002

Cr-Commit-Position: refs/heads/master@{#299388}

BUG=415688
TEST=gpu_unittests, webgl_conformance_tests
R=kbr@chromium.org,bajones@chromium.org

Review URL: https://codereview.chromium.org/651543003

Cr-Commit-Position: refs/heads/master@{#299387}

In smoothness takes priority mode, we should ensure to return tiles
that are required for activation sooner than eventually bin. The reason
for this is that we don't want to starve activation and the prepainting
required for smoothness should already be covered by the soon bin.

Additionally, we have to ensure not to mark these tiles as violating
memory policy, since required for activation tiles need special
treatment (unfortunately). The reason for this is that activation is
currently tied to updating our recordings and smoothness mode would
otherwise starve activation even if we're past the recording region.

BUG=422819
R=reveman

Review URL: https://codereview.chromium.org/651503004

Cr-Commit-Position: refs/heads/master@{#299386}

Motivation:
* chromecast/service/ directory had interplay with chromecast/shell/browser
  code, since the service is all run in the browser process and mildly
  coupled (involves starting WebContents instances, etc,). Made more sense
  for chromecast/service to live in chromecast/shell/browser.
* chromecast/shell/ directory is needless hierarchy, since the entire
  chromecast/ directory represents the Chromecast content-embedder.

Highlights:
* chromecast/shell/{app,browser,common,renderer} --> chromecast/*
* chromecast/shell/browser/resources --> chromecast/app/resources
* chromecast/shell/settings --> chromecast/app/resources
* chromecast/shell/android --> chromecast/browser/android
* chromecast/metrics --> chromecast/browser/metrics
* chromecast/service --> chromecast/browser/service

R=lcwu@chromium.org,gusfernandez@chromium.org,byungchul@chromium.org
TBR=xhwang@chromium.org,asvitkine@chromium.org,thestig@chromium.org,jam@chromium.org,yfriedman@chromium.org
BUG=None

Review URL: https://codereview.chromium.org/638803002

Cr-Commit-Position: refs/heads/master@{#299385}

This change adjusts the scroll bubbling logic in LayerTreeHostImpl so
that outer viewport layer scrolls affect the top controls. Additionally,
the outer viewport's size is adjusted to match the inner viewport's
aspect ratio until a resize occurs.

Blink side: https://codereview.chromium.org/643473002
BUG=364109

Review URL: https://codereview.chromium.org/641873003

Cr-Commit-Position: refs/heads/master@{#299384}

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/c5733ed..ef3851c

TBR=caseq@chromium.org,apavlov@chromium.org,cbiesinger@chromium.org

Review URL: https://codereview.chromium.org/656543004

Cr-Commit-Position: refs/heads/master@{#299383}

This prevents an assert when running in debug mode.

BUG=none
R=sbc@chromium.org

Review URL: https://codereview.chromium.org/648763003

Cr-Commit-Position: refs/heads/master@{#299382}

This mostly just adds the chrome_shell_apk build definition and those of
a whole bunch of targets.

Adds a simple check that when DEPRECATED_java_in_dir is used, it
actually includes the "src" at the end (GYP just assumes that you really
meant that java files are in <(java_in_dir)/src).

Makes the call to process_resources only generate R.java for extra
packages when being run as part of the apk step (otherwise, for
example, both chrome resources and content resources would contain
an R.java for net resources and compilation would fail).

Depends on https://codereview.chromium.org/581273004/

Adds the following targets -- and enables ~300 more (550 counting
template-generated inner targets):

//chrome:chrome_android_core
//chrome/android:chrome_strings_grd
//chrome/android:chrome_java
//chrome/android:activity_type_ids_javagen
//chrome/android:app_banner_metrics_ids_javagen
//chrome/android:resource_id_javagen
//chrome/android:profile_account_management_metrics_javagen
//chrome/android:profile_sync_service_model_type_selection_javagen
//chrome/android:toolbar_model_security_levels_javagen
//chrome/android:tab_load_status_javagen
//chrome/android:chrome_shell_base
//chrome/android:chrome_shell
//chrome/android:chrome_sync_shell
//chrome/android:chrome_shell_resources
//chrome/android:chrome_shell_java
//chrome/android:chrome_shell_assets
//chrome/android:chrome_shell_apk
//chrome/android:chrome_sync_shell_apk
//components/bookmarks:bookmarks_java
//components/bookmarks:bookmarks_jni_headers
//components/bookmarks:bookmark_type_javagen
//components/dom_distiller/android:dom_distiller_core_java
//components/dom_distiller/android:dom_distiller_core_font_family_javagen
//components/dom_distiller/android:dom_distiller_core_theme_javagen
//components/enhanced_bookmarks:jni_headers
//components/enhanced_bookmarks/android:enhanced_bookmarks_java
//components/gcm_driver:gcm_driver_java
//components/gcm_driver:jni_headers
//components/navigation_interception/android:navigation_interception_java
//components/variations:variations_java
//components/web_contents_delegate_android:web_contents_delegate_android
//components/web_contents_delegate_android:web_contents_delegate_android_java
//components/web_contents_delegate_android:web_contents_delegate_android_jni_headers
//printing:printing_java
//sync:fake_server_jni
//sync:sync_java_test_support
//sync:test_support_sync_fake_server_android
//sync:sync_unit_tests_apk
//sync/android:sync_java
//sync/android:sync_javatests

BUG=359249
TBR=ben

Review URL: https://codereview.chromium.org/570203002

Cr-Commit-Position: refs/heads/master@{#299381}

Add more information to LOG(DFATAL) in QUIC's tcp_loss_algorithm.

Merge internal change: 77370712
https://codereview.chromium.org/644123003/

Fix a bug where packet received times aren't sent if the approximate now
time is less than the packet's actual receive time.

Merge internal change: 77056400
https://codereview.chromium.org/643313003/

Change the pacing sender to always pacing the initial burst, even when
an RTT sample hasn't been taken.

Merge internal change: 77004656
https://codereview.chromium.org/644233002/

Set the server's idle timeout to 2s longer than the negotiated value(30s
by default) instead of 1s, in order to prevent failed requests.

Merge internal change: 76821863
https://codereview.chromium.org/651463004/

Call SetDefaults from the QuicConfig constructor instead of requiring
all callers to do so.

Merge internal change: 76709273
https://codereview.chromium.org/647933002

Allow the number of undecryptable QUIC packets buffered before the
CHLO/SHLO to be configured in QuicConfig.

Merge internal change: 76707156

On chromium side: set max undecryptable packets to the initial
congestion window size in QuicStreamFactory.

https://codereview.chromium.org/647923002/

QUIC - Minor formatting changes to keep in sync with internal source.

Found these changes while merging changes from chromium CLs:
  605733006, 605163004

  Chromium code review URL:
      https://codereview.chromium.org/605733006/
      https://codereview.chromium.org/605163004/

Merge internal change: 76636673
https://codereview.chromium.org/651513002/

Remove QuicSentPacketManager::DebugVisitor's OnSentPacket, since it's
redundant to QuicConnection::DebugVisitor's OnPacketSent.

Refactored QuicConnection::DebugVisitor's OnPacketSent in order to add
necessary fields for the trace... visitor.

Merge internal change: 76595983
https://codereview.chromium.org/627583002/

QUIC: if client provides an STK which includes CachedNetworkParams, then
store these and echo them back in future STKs if we have no newer
estimate to send. Flag protected behind disabled
FLAGS_quic_store_cached_network_params_from_chlo.

This is the followup to adding timestamp to the SourceAddressToken proto.
This allowed us to copy a previously provided CachedNetworkParams into
new STKs without losing timestamp data.

It also paves the way for recording BW estimate accuracy in the server:
we now have the client's provided BW estimate stored per connection, so
we can compare against BW that we see on the new connection (this will
be in a future CL).

Merge internal change: 76455340

chromium: this code doesn't impact client side code because we don't
parse SourceAddressToken (we keep it as a string). For QUIC server,
we are not parsing optional cached_network_params. Added a TODO
to convert SourcAddressToken and CachedNetworkParams to protobuf.

https://codereview.chromium.org/623003002/

R=rch@chromium.org

Review URL: https://codereview.chromium.org/648933003

Cr-Commit-Position: refs/heads/master@{#299380}

Previously, it only detected ports that were bound to *, localhost or
127.0.0.1. This detects ports bound to any interface. I noticed this
while investigating 294878, and it could certainly be a source of
flake, but I don't think it's the main one.

BUG=294878

Review URL: https://codereview.chromium.org/634803002

Cr-Commit-Position: refs/heads/master@{#299379}

- app_list_syncable_service is unnecessary at all
- browser_navigator is not necessary, we've introduced OpenURL

BUG=None
R=xiyuan@chromium.org
TEST=build succeeds

Review URL: https://codereview.chromium.org/650473002

Cr-Commit-Position: refs/heads/master@{#299378}

R=jshin@chromium.org
BUG=

Review URL: https://codereview.chromium.org/627083003

Cr-Commit-Position: refs/heads/master@{#299377}

BUG=159234
NOTRY=true

Review URL: https://codereview.chromium.org/639903003

Cr-Commit-Position: refs/heads/master@{#299376}

(But don't use it yet.)

Also change the terminology slightly, and just use the all-around
confusing term "remote ID" (since what we really mean is
"remotely-allocated local ID" or "locally-allocated remote ID", both of
which mean the same thing but are used in different contexts ... and
both of which are very long phrases).

R=yzshen@chromium.org

Review URL: https://codereview.chromium.org/649303002

Cr-Commit-Position: refs/heads/master@{#299375}

This removes the "malloc" implementation of discardable memory.
This implementation exists for test and debugging purproses but
we currently don't have any tests that depend on it so it can be
removed to reduce code size.

This implementation can still be very useful to manually track
down bugs and performance issues in discardable memory clients
but can be maintained separately to reduce code size.

BUG=422953
TBR=danakj@chromium.org

Review URL: https://codereview.chromium.org/651913003

Cr-Commit-Position: refs/heads/master@{#299374}

BUG=422688

Review URL: https://codereview.chromium.org/650963002

Cr-Commit-Position: refs/heads/master@{#299373}

BUG=418577

Review URL: https://codereview.chromium.org/647443003

Cr-Commit-Position: refs/heads/master@{#299372}

BUG=386048

Review URL: https://codereview.chromium.org/638143003

Cr-Commit-Position: refs/heads/master@{#299371}

avformat/os_support: Add _DEFAULT_SOURCE to hide warning about _SVID_SOURCE depreciation

BUG=420149
NOTRY=true

Review URL: https://codereview.chromium.org/652433003

Cr-Commit-Position: refs/heads/master@{#299370}

This patch un-disables the rightware browsermark benchmark. Manually
testing shows this finishes in under 5m on a Nexus 5.

BUG=423018

Review URL: https://codereview.chromium.org/649283002

Cr-Commit-Position: refs/heads/master@{#299369}

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/36ba250..c5733ed

TBR=caseq@chromium.org,apavlov@chromium.org,cbiesinger@chromium.org

Review URL: https://codereview.chromium.org/649233003

Cr-Commit-Position: refs/heads/master@{#299368}

back via chrome.cast.channel.onError.

BUG=410109

Review URL: https://codereview.chromium.org/580923002

Cr-Commit-Position: refs/heads/master@{#299367}

This test has been experiencing flaky timeouts.

BUG=423094
TBR=ygorshenin@chromium.org
NOTRY=true

Review URL: https://codereview.chromium.org/648383002

Cr-Commit-Position: refs/heads/master@{#299366}

Mechanical change that adds instrumentation required to locate the source of jankiness (i.e. a long-running fragment of code executed as a part of the task that causes jank) in the code. See the bug for details on what kind of jank we are after.
A number of similar CLs were landed, and none of them caused issues. The code of the instrumentation is highly optimized and is not expected to affect performance. The code simply creates a diagnostic task which is identical to ones created by PostTask or IPC message handlers.
Landing as TBR since this is a mechanical, safe and temporary change.

BUG=422489
TBR=asanka@chromium.org

Review URL: https://codereview.chromium.org/654683002

Cr-Commit-Position: refs/heads/master@{#299365}

BUG=340882

Review URL: https://codereview.chromium.org/648333002

Cr-Commit-Position: refs/heads/master@{#299364}

Summary of changes available at:
https://chromium.googlesource.com/skia/+log/9467001..6c07907

CQ_EXTRA_TRYBOTS=tryserver.blink:linux_blink_rel,linux_blink_dbg
TBR=rmistry@google.com

Review URL: https://codereview.chromium.org/650983002

Cr-Commit-Position: refs/heads/master@{#299363}

Also various other fixes, e.g. condensing code, converting DCHECK_LT(0, a) -> DCHECK_GT(a, 0) (and the like) for readability, inserting a few typecasts.

BUG=none
TEST=none

Review URL: https://codereview.chromium.org/637023002

Cr-Commit-Position: refs/heads/master@{#299362}

never writes data again.

Merge internal change: 77265365

R=rch@chromium.org
BUG=423022

Review URL: https://codereview.chromium.org/644243002

Cr-Commit-Position: refs/heads/master@{#299361}

This is a refactor of the CHROMIUM_image extension that allows
the compositor to map/unmap GpuMemoryBuffers on worker threads
and potentially also allocate these buffers on worker threads.

CreateImageCHROMIUM now takes an opaque ClientBuffer as first
parameter. ClientBuffer is implementation specific and in the
case of chromium a gfx::GpuMemoryBuffer. Or more specifically
a content::GpuMemoryBufferImpl when used with the content layer.

This allows the compositor to allocate and use GpuMemoryBuffers
without a GLES2Interface.

A GpuMemoryBufferManager interface has been introduced. This
interface provides a mechanism for the compositor to allocate
GpuMemoryBuffer instances in the renderer and browser process.

BUG=418553

Review URL: https://codereview.chromium.org/634083002

Cr-Commit-Position: refs/heads/master@{#299360}

This test is experiencing flaky timeouts.

BUG=423077
TBR=nkostylev@chromium.org
NOTRY=true

Review URL: https://codereview.chromium.org/649293002

Cr-Commit-Position: refs/heads/master@{#299359}

Right now BrowserPlugins don't handle find in page. This CL adds support for find in page in MIMEHandlerView BrowserPlugin instances.

Find in page is only handled for "full page" plugins, that is when the BrowserPlugin as loaded at the top level. The reason is because supporting find in embedded BrowserPlugins would require recursively searching which is far more complicated to implement and we (jam@, fsamuel@) have decided to defer implementing for the time being.

Detecting whether the BrowserPlugin is loaded at the top level requires detecting whether the main frame is a "plugin document" in blink, which needs to be sent to the browser from the renderer. It isn't sufficient to determine whether the BrowserPlugin is merely loaded in the main frame, because it may be <embed>ed inside a html document in the main frame. In that case we don't want find in page to search the document.

BUG=303491

Review URL: https://codereview.chromium.org/597753003

Cr-Commit-Position: refs/heads/master@{#299358}

Renaming variable name (browser_backend, browser) and function names
(under platform) where applicable.

BUG=

Review URL: https://codereview.chromium.org/647193002

Cr-Commit-Position: refs/heads/master@{#299357}

BUG=None
NOTRY=True

Review URL: https://codereview.chromium.org/633213002

Cr-Commit-Position: refs/heads/master@{#299356}

R=estade@chromium.org
BUG=422906

Review URL: https://codereview.chromium.org/651993002

Cr-Commit-Position: refs/heads/master@{#299355}

By request.

R=agl@chromium.org

Review URL: https://codereview.chromium.org/620223002

Cr-Commit-Position: refs/heads/master@{#299354}

With delegated frames, we either want to display the frame itself or a single color (white). Default the layer for delegated frames to be solid color, and allow the layer to be switched from delegated to solid color when the delegated contents go away.

BUG=420832

Review URL: https://codereview.chromium.org/634113002

Cr-Commit-Position: refs/heads/master@{#299353}

wjia is no longer working on chrome.

Review URL: https://codereview.chromium.org/650993002

Cr-Commit-Position: refs/heads/master@{#299352}

Disabling this test due to flaky timeouts.

BUG=423053
TBR=stevenjb@chromium.org
NOTRY=true

Review URL: https://codereview.chromium.org/649263002

Cr-Commit-Position: refs/heads/master@{#299351}