GitLab

1. Avoids overloading in a C linkage block (mostynb)
2. Only compiles ATK support if use_x11 is true
    to avoid ChromeCast issue (gunsch)
3. Updates chrome/installer/linux expectations

Original changelist: https://codereview.chromium.org/975113002/

BUG=463671
R=thestig@chromium.org
TBR=dpranke, plundblad, sky

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

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

The regressing CLs have been reverted.

BUG=466690

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

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

This makes it possible to refer to the platform as DRI and DRM. We need
this intermediate state so we can update the CrOS builds to use DRM
rather than DRI.

BUG=none
TEST=Build ozone with DRI & DRM platform and without to verify build
(GYP and GN)

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

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

BUG=

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

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

BUG=

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

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

Adds support for long idle times in the Blink Scheduler.
A long idle time is initiated
if there are no frames being drawn and we are not in TOUCHSTART policy. Each
long idle period will be a maximum of 50 milliseconds or the time to the next
pending delayed task (whichever is sooner). Long idle periods will continually
be scheduled until a call to EndIdlePeriod is made. If there are no pending
tasks in the idle queue then the callback used to initate the next long idle
task will be posted on the control_task_after_wakeup_runner_ task runner, thus
ensuring that it won't cause the scheduler to wake up until another task
could have posted more idle work.

Currently, the long idle tasks are not enabled due to crbug.com/467655 -
once this is fixed they will be enabled.

Long idle task design doc:
https://docs.google.com/a/chromium.org/document/d/1yBlUdYW8VTIfB-DqhvQqUeP0kf-Ap1W4cao2yQq58Do/edit

BUG=455713,467655

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

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

The minimum width calculations weren't always taking effect with the omnibox
and the browser actions container. Refactor it a bit to make it:
a) more reliable (min width checked at every resize)
b) clearer (less confusing back and forth with using observer methods)

BUG=463905

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

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

Tweak update script:
https://codereview.chromium.org/993123002

Update libvpx:
https://codereview.chromium.org/1015483002

R=tomfinegan@chromium.org

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

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

Passed chrome-ui-review: https://groups.google.com/a/google.com/d/msg/chrome-ui-review/FwuQ2TWc5n8/H3PSuV4L_cAJ

BUG=467165

TBR=tsepez
(comment changes only in render_messages)

NOPRESUBMIT=true
(legacy LOG messages)

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

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

This class provides an interface, to be used on the IO thread, on top
of the NotificationDatabase class. It abstracts away the thread
requirements of the database class and is responsible for managing the
status and the lifetime of the database.

Right now it's only used in unit tests, but it will eventually live as
a member of StoragePartitionImpl, and will be used by the notification
message filter.

Design document:
  http://goo.gl/TciXVp

BUG=447628

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

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

TBR=jam@chromium.org
BUG=417518, 448592, 458204, 458194
TEST=Site Isolation FYI bots stay green.

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

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

Summary of changes available at:
https://chromium.googlesource.com/skia/+log/fdc3108..dfdec78

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

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

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

TBR=mlamouri@chromium.org
BUG=467670

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

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

It was never implemented or used; a replacement for the
principalsPrivate extension API. It's been untouched for over a year.

BUG=463335

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

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

This pulls the following changes:
r1434 6225882 Fix compatibility with Android NDK r10d.
r1433 ac07e58 Make breakpad compatible with Android NDK r10d.

Summary of changes available at:
https://chromium.googlesource.com/external/google-breakpad/src/+log/d1f8b74..2c37c22

BUG=breakpad:642

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

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

BUG=none
TEST=none

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

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

BUG=398967, 464147, 461882, 451081
TBR=jyasskin

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

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

Also avoid dereferencing it in OnMessageReceived after deletion.

BUG=461191
TEST=No more crashes in RenderFrameImpl::OnMessageReceived

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

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

* Only call ToString() for types that require conversion to string. If the value is already of type string, we can just use that value.

* For chrome://webrtc-internals, we can now pass the correct type in most cases (not in64), in the dictionary passed to the web page.  This also lowers the overhead of the PeerConnectionTracker when no page requires this data.  (I think we can still do better there though).

BUG=webrtc:2822

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

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

TBR=ncbray

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

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

Previously extensions::Dispatcher was responsible for creating ScriptContexts
then Adding them to its ScriptContextSet. Now, ScriptContextSet creates them
itself. This prepares the Extension system for later changing to lazily or
asynchronously creating ScriptContexts.

BUG=466373
R=rockot@chromium.org

Committed: https://crrev.com/75605c7fca774b95984ba67f70ba86bb5750c0f6
Cr-Commit-Position: refs/heads/master@{#320602}

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

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

Originally this wasn't turned on as it didn't work on Windows.
This passes now.

R=dpranke@chromium.org
BUG=377980

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

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

Due to complex blur shader test still has timeout.
http://build.chromium.org/p/chromium.memory.fyi/waterfall?builder=Windows%20Unit%20(DrMemory%20full)%20(5)
I made test even simpler in terms of layer size and blur parameter.

R=enne

BUG=435632

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

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

cc::RendererCapabilities was defined in cc/trees/layer_tree_host.h
which had a few subtle implications. First, cc/output/renderer.h needed
to #include layer_tree_host even though cc/output/ logically should not
depend on cc/trees/. Second, since layer_tree_host.h includes pretty
much the entire world, everything that was #including renderer.h was
implicitly pulling in many other headers that it may have used. In the
spirit of IWYU these files should either include or forward declare
types they use.

This puts RendererCapabilities in cc/output/renderer_capabilities and
fixes up includes in many other files.

R=danakj@chromium.org

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

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

This picks the following changes:
- convert plist and strings to binary for iOS
- bump Xcode compatibility version to 46 (Xcode 3.2)
- include action inputs in hybrid build
- export generator flavor to gyp scripts

BUG=None

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

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

BUG=

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

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

This implements support for in-process discardable
memory. Each in-process discardable memory instance is
associated with a discardable shared memory segment. This
is hopefully efficient enough with the limited use of
discardable memory in the browser process.
DiscardableSharedMemoryHeap can be used if this is not
enough.

This also moves the test implementation of the discardable
memory allocator into a TestDiscardableMemoryShmemAllocator
class and requires tests that use discardable memory to
explicitly use this test allocator. Browser tests uses the
real discardable memory allocator.

BUG=422953,463250

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

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

To comply with the current navigation behavior this change makes it so
that render-initiated navigations do not create a new  renderer. Once
OOPIF add proper support, this change should be reverted.

BUG=440266

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

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

R=hcarmona@chromium.org
BUG=none

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

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

This patch introduces the actual functionality for storing notification
data in the NotificationDatabase. There are three separate methods
now, ReadNotificationData() and WriteNotificationData() and
DeleteNotificationData(),, which do exactly what their names imply.

These methods are covered by a variety of unit tests, but still aren't
hooked up to any production code.

Design document:
  http://goo.gl/TciXVp

BUG=447628

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

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

This looks like a leftover from an earlier less structured era.

R=danakj@chromium.org

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

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

Html viewer is hitting a NOTREACHED due to a missing resource.
Added logging for the resource name so that it can be tracked.

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

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

BUG=none

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

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

BUG=466196
TEST=/tools/perf/run_benchmark --browser system gpu_times.gpu_rasterization.top_25_smooth --reset-results --page-filter=Maps

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

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

This is required for OSS licensing compliance.

BUG=462636
R=glider@chromium.org
NOTRY=true

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

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

Revert of Disable a test that fails under ASan and MSan (patchset #1 id:1 of https://codereview.chromium.org/1007293002/)

Reason for revert:
This test is a victim of a bigger issue of main renderer message loop being used after it is deleted. Details are in crbug.com/467369.

I've also run the test with ASAN locally and didn't reproduce after a few runs.

Original issue's description:
> Disable a test that fails under ASan and MSan
>
> It can be flaky in other configurations as well
>
> BUG=467483
> TBR=nasko
>
> Committed: https://crrev.com/992ff715f61e90562983139ac31392b72e716822
> Cr-Commit-Position: refs/heads/master@{#320713}

TBR=timurrrr@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=467483

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

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

Adding an easy(ier) to use tool to start legion-based tests. This tool handles all of the isolate archives, building the test controller command line, and running the test controller.

BUG=467618

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

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

This means each toolchain can declare arguments as it sees fit. Prior to this change each toolchain needed to declare the argument at exactly the same place, which is not always possible. For example, the following triggered an error:

declare_args() {
  foo = 1
  if (xxx) {
    foo = 2
  }

with xxx being specific to one toolchain.

TEST=covered by test
BUG=465029
R=brettw@chromium.org

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

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

R=gunsch@chromium.org
BUG=

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

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

Summary of changes available at:
https://chromium.googlesource.com/skia/+log/3675874..fdc3108

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

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

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