GitLab

BUG=591832

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

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

When we detect a segment boundary we reinitialize the decoder. Currently
on Windows that results in tearing down the decoder instance the
D3D9/D3D11 device objects, the output picture buffers etc.

We don't need to tear down the output picture buffers and the d3d device
objects. This fixes the black frame which shows up due to the picture
buffers getting destroyed and new ones getting created.

In any case if the resolution changes we do request new output buffers
anyways.

I tested the test case in bug 594266 which was the reason for the config
change code in the first place. That still works in D3d9 and D3D11.

BUG=616349

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

The assert is no longer hit in WebGL conformance tests.
It seems that the bug is already fixed.

BUG=537922

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

MessageLoop::PostTask/PostDelayedTask/DeleteSoon/ReleaseSoon
are deprecated. This CL makes the following replacements to
remove some uses of these methods:

"MessageLoop::current()->PostTask" ->
  "ThreadTaskRunnerHandle::Get()->PostTask"
"MessageLoop::current()->PostDelayedTask" ->
  "ThreadTaskRunnerHandle::Get()->PostDelayedTask"
"MessageLoop::current()->DeleteSoon" ->
  "ThreadTaskRunnerHandle::Get()->DeleteSoon"
"MessageLoop::current()->ReleaseSoon" ->
  "ThreadTaskRunnerHandle::Get()->ReleaseSoon"

In files where these replacements are made, it adds these includes:
  #include "base/location.h"
  #include "base/single_thread_task_runner.h"
  #include "base/threading/thread_task_runner_handle.h"

And removes this include if it is no longer required:
  #include "base/message_loop/message_loop.h"

Why ThreadTaskRunnerHandle::Get() instead of
MessageLoop::current()->task_runner()?
 - The two are equivalent on threads that run a MessageLoop.
 - MessageLoop::current() doesn't work in base/task_scheduler
   because the scheduler's thread don't run MessageLoops.
   This CL will therefore facilitate the migration of browser
   threads to base/task_scheduler.

Steps to generate this patch:
1. Run message_loop_cleanup.py (see code on the bug).
2. Run tools/sort-headers.py on modified files.
3. Run git cl format.

BUG=616447
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_site_isolation

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

https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/619acd2c51c4..5ede943f9a5e

$ git log 619acd2c5..5ede943f9 --date=short --no-merges --format='%ad %ae %s'

TBR=catapult-sheriff@chromium.org

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

This CL replaces the simple mus CompositorFrameMetadata struct with a
full fidelity struct along with StructTraits. w00t! Soon full fidelity
CompositorFrames in Mus without extra copies!

BUG=611802
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel

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

BUG=604282,597124

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

BUG=550497

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

Changes made manually because clang-tidy doesn't interact well with cross-compile.

BUG=612843

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

BUG=b/28157714
TEST=create too much ARC codecs and it should fail when reach limit

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

The width only needs to be set explicitly during animations, when the card
is position: fixed.

BUG=608134
R=dbeam@chromium.org
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:closure_compilation

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

This method is no longer used, and should be removed.

BUG=
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_site_isolation

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

There were a couple of build file issues that broke the ASAN Debug
bot and the MSAN bots on the lkgr waterfall. This CL fixes those issues,
and also flips the MSAN bots back to GYP since the main MSAN bots
are still kinda broken and it's easier to keep them all consistent.

TBR=mbarbella@chromium.org
BUG=605732

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

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

It's hard to mechanically replace specializations of OwnedPtrDeleter<T>
to std::unique_ptr equivalents, so they are converted manually.

A new typedef WebMessagePortChannelUniquePtr is introduced so people can
always use std::unique_ptr with a correct deleter.

BUG=617504

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

Also shuffle some test code around so bugs like this can be more easily
noticed by bots.

R=mmenke@chromium.org
BUG=615626

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

This CL implements LatencyInfo mojom types, and associated
StructTraits for serialization and deserialization. This will be used
by cc::CompositorFrameMetadata and ultimately cc::CompositorFrame
serialization/deserialization over mojo.

BUG=611802

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

This CL reverts r397982 ( https://codereview.chromium.org/2032613004 )
and also flips the main win CQ bots back to GYP. This will hopefully
get the cycle time and capacity issues for the CQ back under control.

TBR=brucedawson@chromium.org, phajdan.jr@chromium.org
BUG=617837

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

This is a CC-side fix which can be useful for all CC clients.

Blink side: We will need to fix the race in CompositedLayerMapping destruction vs. CompositorAnimationPlayer detachment separately.

BUG=615471
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel

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

https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/2b7a13d86594..619acd2c51c4

$ git log 2b7a13d86..619acd2c5 --date=short --no-merges --format='%ad %ae %s'

BUG=616832

TBR=catapult-sheriff@chromium.org

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

This fixes another crash when table parts are set as containment roots.

<table> elements still don't honor layout containment when calculating
their dimensions, though.

BUG=616643

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

Partition Alloc dump provider dumps bucket stats for the case of
DirectMap objects even for ligth dumps. This CL fixes this issue.

BUG=613198

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

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

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=tryserver.blink:linux_blink_rel

TBR=hablich@chromium.org,machenbach@chromium.org,yangguo@chromium.org,vogelheim@chromium.org

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

This adds support for mailboxes to ScopedWriteLockGL. Using the mailbox
requires using ScopedTextureProvider/ScopedSkSurfaceProvider which
ensures that the texture id for the mailbox is destroyed after use on
the worker context.

This CL also includes the following cleanup:
1. ResourceProvider locks don't keep resource pointers around.
2. ScopedSamplerGL does not inherit from ScopedReadLockGL.
3. GpuRasterizer is folded back into GpuRasterBufferProvider.
4. TileTaskManager does not own RasterBufferProvider.

BUG=525259
R=piman@chromium.org
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel

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

BUG=602407

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

To expand field trials, enable flags on waterfall for testing.

BUG=591245

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

No intended behavior change.

BUG=579255

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

The Mac and iOS GN bots don't currently limit the number of concurrent
links. The official continuous win bots aren't on MB because they can't
limit the number of concurrent links through MB.

This CL adds a 'concurrent_links' arg to GN, which calls the
get_concurrent_links script to get the appropriate default value
(making this consistent across platforms), and also adds a hack
to MB to translate a gyp_link_concurrent "GYP_DEFINE" to the
GYP_LINK_CONCURRENCY env var.

The CL also adds a test for this MB hack and the similar, already existing
LLVM_FORCE_HEAD_REVISION hack.

R=scottmg@chromium.org, brettw@chromium.org
BUG=602480, 611491, 616390

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

mbstate_t is defined in <wchar.h>, which is often indirectly included
through <string>. However, that's not true for all implementations of
C++ standard library. This CL adds the missing inclusion of <wchar.h> in
base/strings/string16.h for the definition of mbstate_t.

BUG=None

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

There seems to be data cached by the OS which is not deleted by
DexLoader#deleteCachedDexes() which is causing the test to be flaky.
This CL changes DexLoaderTest#testLoadAfterDeleteCachedDexes() to test
DexLoader#deleteCachedDexes() in a scenario which is closer to how the function
is used in production.

The test used to test that calling DexLoader#deleteCachedDexes() would make
DexLoader#load() load a dex file from scratch.

The CL changes the test to test that:
- DexLoader#deleteCachedDexes() deletes previously extracted dexes from the local
data directory
- It is possible to use reuse a data directory to load several dexes

BUG=616923

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

BUG=617559

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

This allows the renderer to correctly interpret NV12 and other pixel formats.

BUG=574292

Committed: https://crrev.com/1ace3b00d9dad163255b8e73deaad53c0a43a79a
Review-Url: https://codereview.chromium.org/1942123002
Cr-Original-Commit-Position: refs/heads/master@{#396634}
Cr-Commit-Position: refs/heads/master@{#398196}

Currently this logic needs to be copied and called every time
chrome::AttemptRestart() is called. Moving it within chrome::AttemptRestart()
allows it to be reused. Moreover, it seems that calling
chrome::AttemptRestart() without the said logic (there are such occurrences),
is not correct.

This is in preparation of reducing the number of "Restart" codepaths in MD
Settings.

BUG=617830

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

ExternalNavigationHandler#intentsHaveSameResolvers() will be called on each
WebAPK navigation. Removing the duplicate call to
PackageManager#queryIntentActivities() saves 2ms per navigation.

BUG=609122
TEST=None

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

This CL mistakenly disabled the 'detach' behavior for ScrollbarManager:

https://codereview.chromium.org/1930183002

... because it seemed like DelayScrollPositionClampScope would be sufficient
to preserve all the necessary state for scrollbars as they were added and
removed during the multiple layout passes of flex layout.  However, that
was premature: even though the scroll positions were preserved, destroying
and recreating scrollbars during layout will invalidate the
ScrollingCoordinator's mapping from Scrollbar to WebScrollbarLayer.

One side effect is that if a scroll event handler forces layout to run during
a scrollbar drag, and the Scrollbar/WebScrollbarLayer association is broken,
then the compositor will think that the scrollbar drag has ended, even though
mouse-up has not yet happened.

This CL also sneaks in a tiny optimization: if auto scrollbars are frozen,
then childFlexBasSizeRequiresLayout should not return true due to the child
having auto scrollbars (since the scrollbars cannot change).

BUG=617498
R=eae@chromium.org,cbiesinger@chromium.org

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

This change decouples DesktopView(Interface) and TouchInputHandler(Interface) by
removing routing functions
DesktopViewInterface.onSoftInputMethodVisibilityChanged and
DesktopViewInterface.setInputStrategy. After this change, TouchInputHandler
takes responsibility to listen to onInputModeChanged and
onSoftInputMethodVisibilityChanged events of Desktop activity directly.

This is part remoting desktop Android client refactor work, a design doc is @
https://goo.gl/MA6zjx.

BUG=615277

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

BUG=610086

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

Spec: https://drafts.css-houdini.org/css-typed-om/#the-stylepropertymap

BUG=545318

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

When --isolate-extensions or --site-per-process modes are enabled, all
extensions frames run in extension processes and are not mixed in regular
web renderers. This causes a problem with security checks for
web_accessible_resources, which allow all navigations to extension pages
when they are performed in extension process. This is no longer true and
this patch addresses this by using a NavigationThrottle to perform the
proper checks on the UI thread (also PlzNavigate compatible).

BUG=616488
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_site_isolation

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

It had been a while since I'd run `mb audit` and there were
a few new builders that didn't have entries. This adds those,
removes some builders that are gone, and fixes some typos.

TBR=brettw@chromium.org
BUG=605732

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