This is a merge to M52 of:
https://codereview.chromium.org/2084143002
https://codereview.chromium.org/2091253003

Android MediaCodec creation will sometimes never come back.  On a
N7 (2013) with Lollipop, this can happens when an attempt to allocate
a hardware codec fails, and falls back to a software codec.  Once
mediaserver gets into a bad state, future attempts to create a
hardware codec will hang.  As a result, no additional AVDA instances
will get codecs.  Further, destroying any of them will hang the gpu
process when it tries to join the thread that handles construction.

This CL does several things:
    - Don't join the construction thread if there are outstanding
      MediaCodec creations on it.  While this may sometimes not
      shut down the thread if the AVDA is destroyed while the
      creation is pending (and would return if we just waited a bit
      longer), the thread will be shut down the next time an AVDA
      instance is destroyed.  It isn't leaked permanently.

    - Fall back to requesting a software codec if we believe that
      construction of a hardware codec is hung.  We don't attempt
      to salvage the AVDA instance(s) that have pending HW codecs,
      but future AVDA instances will fall back to software.  If
      those HW codecs are eventually allocated, then we will start
      requesting HW codecs again.  For example, if we simply time
      out too quickly, or if mediaserver is restarted, then we can
      try for hardware codecs for future AVDA instances.

    - Release hardware codecs on a separate thread, since that can
      hang too if mediaserver is in a bad state.

BUG=613238, 622927
[email protected]
NOPRESUBMIT=true
NOTRY=true

Review-Url: https://codereview.chromium.org/2106133003
Cr-Commit-Position: refs/branch-heads/2743@{#519}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

When processing the set of dirty output nodes, nodes further down the
chain may be marked as dirty as a result. Take that into account
when iterating over the current set.

R=hoch
BUG=610643, 613902

Review-Url: https://codereview.chromium.org/2006883002
Cr-Commit-Position: refs/heads/master@{#395643}
(cherry picked from commit 7b953ca)

Drop unique audio thread ID requirement.

r391848 introduced the requirement that, once set, the audio thread ID
could not be changed. This is proving too burdensome a constraint to
keep, in case audio device threads do end up being stopped and new
ones created.

While r395182 took care of some cases where audio threads end up
stopping, carefully resetting the recordeed audio thread ID, other
cases remain (see associated bug.) While those could be similarly
handled, precisely tracking the current audio thread ID is proving
to not be worth the overhead. Hence, retire the constraint and let
the audio thread processing a render quantum set its thread ID as
part of executing, irrespective of what audio thread executed
the previous quantum.

This effectively reverts r395182.

R=
BUG=613902

(cherry picked from commit 94a98a7)

Review-Url: https://codereview.chromium.org/2008903002
Cr-Original-Commit-Position: refs/heads/master@{#395682}
Cr-Commit-Position: refs/branch-heads/2743@{#520}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

Device state broadcast receiver is registered after the sync backend
initialized callback. It should be registered when precache GCM task
starts, since WiFi/Power state changes may occur while the sync is
being initialized.

BUG=619225

(cherry picked from commit 411c94f)

Review-Url: https://codereview.chromium.org/2064213002
Cr-Original-Commit-Position: refs/heads/master@{#400803}
Cr-Commit-Position: refs/branch-heads/2743@{#521}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

…shKey.

Allows Blink to use base::debug::ScopedCrashKey.

BUG=621730

Review-Url: https://codereview.chromium.org/2105763002
Cr-Commit-Position: refs/heads/master@{#402602}
(cherry picked from commit 28dd2ed)

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

Cr-Commit-Position: refs/branch-heads/2743@{#522}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

Currently, getting an unsatisfiable range error will crash multibuffers.
That shouldn't normally happen if the server is sane, which is of course not guaranteed.

(cherry picked from commit 625ddd9)

Review-Url: https://codereview.chromium.org/2078833003
Cr-Original-Commit-Position: refs/heads/master@{#400766}
Cr-Commit-Position: refs/branch-heads/2743@{#523}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

…rrent set."

This reverts commit d0b96fe.

Spoke with security TPM and we don't need this for M52.  Reverting.

Cr-Commit-Position: refs/branch-heads/2743@{#524}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

This change can be reverted after a day or two of data.

BUG=621730
[email protected], [email protected]

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

Cr-Commit-Position: refs/heads/master@{#402609}
(cherry picked from commit d0210f3)

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

Cr-Commit-Position: refs/branch-heads/2743@{#525}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

Cr-Commit-Position: refs/branch-heads/2743@{#526}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

If multiple windows all tried to create a warning bubble at the same
time, it would be handled incorrectly. Though only one bubble would
show, the others would be destructed and potentially undo the work the
first did (like highlighting extensions on the toolbar).

Instead, link the warning bubbles with the toolbar model, which is per-
profile and handles the highlighting logic. Also add a regression test,
and beef up some existing tests.

BUG=620434

Review-Url: https://codereview.chromium.org/2076093004
Cr-Commit-Position: refs/heads/master@{#400849}
(cherry picked from commit af64c8c)

[Extensions UI] Fix a crash when clicking on a bubble's learn more

Clicking on a bubble's learn more link causes a tab to open, which in
turn causes the bubble to be cleaned up (as part of losing focus to the
new tab). Fix the order so that we clean up before opening the new tab
and add a regression test. Also add end-to-end tests for clicking on the
action and dismiss buttons.

BUG=622117

Review-Url: https://codereview.chromium.org/2086193002
Cr-Commit-Position: refs/heads/master@{#401412}
(cherry picked from commit bb826f1)

[email protected]
[email protected]

Manual Merge Note: Merging the fix for crbug.com/620434 along with the
fix for the crash related to that patch.

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

Cr-Commit-Position: refs/branch-heads/2743@{#527}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

Cr-Commit-Position: refs/branch-heads/2743@{#528}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

BUG=622219

Review-Url: https://codereview.chromium.org/2107953003
Cr-Commit-Position: refs/heads/master@{#402698}
(cherry picked from commit a54d742)

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

Cr-Commit-Position: refs/branch-heads/2743@{#529}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

There are several corner cases with in-page navigations where non-web
URLs (e.g., about:blank, file) may look cross-origin.  This was
leading to renderer kills when a subframe went back/forward.

A followup CL will account for these cases more accurately, but since
this is just second line of defense against URL spoofs, we can loosen
it to only check web URLs for the time being to avoid the kills.

BUG=613732
TEST=See bug comment 10 for repro steps.
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_site_isolation

Review-Url: https://codereview.chromium.org/2054013003
Cr-Commit-Position: refs/heads/master@{#399228}
(cherry picked from commit 37988b9)

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

Cr-Commit-Position: refs/branch-heads/2743@{#530}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

…becomes out-of-flow-positioned

This is required when there are descendants needing overflow recalc.
Otherwise during overflow recalc because the containing block's
positioned descendant list didn't contain the new out-of-flow-positioned
object we would not reach the descendants needing overflow recalc.

BUG=623867
TEST=fast/overflow/add-visual-overflow-and-change-container-position.html

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

Review-Url: https://codereview.chromium.org/2103843003
Cr-Original-Commit-Position: refs/heads/master@{#402550}
Cr-Commit-Position: refs/branch-heads/2743@{#531}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

… URLs. (patchset crosswalk-project#1 id:1 of https://codereview.chromium.org/2111633002/ )

Reason for revert:
Sigh, test failed to compile on builder:

https://uberchromegw.corp.google.com/i/official.desktop.continuous/builders/win%20beta/builds/3447/steps/compile/logs/stdio

FAILED: obj/content/browser/frame_host/content_browsertests.navigation_controller_impl_browsertest.obj
ninja -t msvc -e environment.x86 -- "C:\b\depot_tools\win_toolchain\vs_files\95ddda401ec5678f15eeed01d2bee08fcbc5ee97\VC\bin\amd64_x86\cl.exe" /nologo /showIncludes /FC @obj\content\browser\frame_host\content_browsertests.navigation_controller_impl_browsertest.obj.rsp /c ..\..\content\browser\frame_host\navigation_controller_impl_browsertest.cc /Foobj\content\browser\frame_host\content_browsertests.navigation_controller_impl_browsertest.obj /Fdobj\content\content_browsertests.cc.pdb
c:\b\build\slave\win_beta\build\src\content\browser\frame_host\navigation_controller_impl_browsertest.cc(749): error C2664: 'bool content::ExecuteScript(const content::ToRenderFrameHost &,const std::string &)': cannot convert argument 1 from 'content::FrameTreeNode *' to 'const content::ToRenderFrameHost &'

Original issue's description:
> Avoid incorrect NC_AUTO_SUBFRAME renderer kills for non-web URLs.
>
> There are several corner cases with in-page navigations where non-web
> URLs (e.g., about:blank, file) may look cross-origin.  This was
> leading to renderer kills when a subframe went back/forward.
>
> A followup CL will account for these cases more accurately, but since
> this is just second line of defense against URL spoofs, we can loosen
> it to only check web URLs for the time being to avoid the kills.
>
> BUG=613732
> TEST=See bug comment 10 for repro steps.
> CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_site_isolation
>
> Review-Url: https://codereview.chromium.org/2054013003
> Cr-Commit-Position: refs/heads/master@{#399228}
> (cherry picked from commit 37988b9)
>
> Committed: https://chromium.googlesource.com/chromium/src/+/38453aec59e45d2685bb327f3a9033554489e4e8

[email protected]
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=613732

Review-Url: https://codereview.chromium.org/2110183003
Cr-Commit-Position: refs/branch-heads/2743@{#532}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

There are several corner cases with in-page navigations where non-web
URLs (e.g., about:blank, file) may look cross-origin.  This was
leading to renderer kills when a subframe went back/forward.

A followup CL will account for these cases more accurately, but since
this is just second line of defense against URL spoofs, we can loosen
it to only check web URLs for the time being to avoid the kills.

[email protected]
BUG=613732
TEST=See bug comment 10 for repro steps.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
Review-Url: https://codereview.chromium.org/2054013003
Cr-Commit-Position: refs/heads/master@{#399228}
(cherry picked from commit 37988b9)

Review-Url: https://codereview.chromium.org/2111713002
Cr-Commit-Position: refs/branch-heads/2743@{#533}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

… invalidation.

BUG=610287

Review-Url: https://codereview.chromium.org/2099383003
Cr-Commit-Position: refs/heads/master@{#402404}
(cherry picked from commit 034b0a2)

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

Cr-Commit-Position: refs/branch-heads/2743@{#534}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

…e once per client.

When a new automation API client is added but accessibility is already
enabled (like if you disable and then re-enable ChromeVox), we have to
reset the accessibility state of every frame to ensure that the new
accessibility client gets a clean accessibility tree.

On a site with iframes, this resulted in the accessibility tree getting
reset once per each frame, leading to a performance regression that was
especially noticeable on Mac. Fix it by only resetting once per frame tree.

BUG=619113

Review-Url: https://codereview.chromium.org/2095393003
Cr-Commit-Position: refs/heads/master@{#402490}
(cherry picked from commit 333a09d)

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

Cr-Commit-Position: refs/branch-heads/2743@{#535}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

Caused by incorrect merge conflict resolution.

BUG=624571

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

Cr-Commit-Position: refs/branch-heads/2743@{#536}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

It was done for WebKit in http://wkrev.com/192805

Without it, the renderer process can't talk to the font server on macOS
10.12 Sierra and spawns an entire font server in each renderer process.

This CL reduces the memory footprint of each renderer process by ~600MB
on macOS 10.12 Beta (16A201w).

BUG=619981

Review-Url: https://codereview.chromium.org/2075953002
Cr-Commit-Position: refs/heads/master@{#402523}
(cherry picked from commit 56fd33c)

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

Cr-Commit-Position: refs/branch-heads/2743@{#537}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

Cr-Commit-Position: refs/branch-heads/2743@{#538}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

BUG=618763

Review-Url: https://codereview.chromium.org/2082723002
Cr-Commit-Position: refs/heads/master@{#402634}
(cherry picked from commit a840351)

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

Cr-Commit-Position: refs/branch-heads/2743@{#539}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

In Material Design we display a white tab spinner for Incognito mode
tabs, but we need to also do so for dark themes.

[email protected]
BUG=624106

Review-Url: https://codereview.chromium.org/2103073003
Cr-Commit-Position: refs/heads/master@{#402643}
(cherry picked from commit f61958a)

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

Cr-Commit-Position: refs/branch-heads/2743@{#540}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

An edge case was missed due to a typo in a DCHECK, during the original
fallback decoder submission.

Currently, the following scenario can happen:
- DecoderStream requests buffers from the demuxer
  (STATE_PENDING_DEMUXER_READ).
- |decoder_| returns a DECODE_ERROR before a frame was ouptutted,
  initiating a decoder fallback (STATE_REINITIALIZING_DECODER).
- OnDecoderSelected() successfully completes (STATE_NORMAL).
- OnBufferReady() is called back (the typo in the DCHECK meant we never
  considered when we enter the function in STATE_NORMAL). We return at
  line 601 because the state is not STATE_PENDING_DEMUXER_READ, and drop
  the buffer.

This CL fixes the typo, and changes so we only drop the buffer whilst in
STATE_ERROR, and also handles the case where we had saved buffers in the
fallback buffer queue.

BUG=597605, 615141
TEST= Setup GpuVideoDecoder to fail 10% and refreshed the page for
several minutes. Hard to test the end to end though...

Review-Url: https://codereview.chromium.org/2012293002
Cr-Commit-Position: refs/heads/master@{#396371}
(cherry picked from commit 4849043)

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

Cr-Commit-Position: refs/branch-heads/2743@{#541}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

…stable."

The pending demuxer read state is overwritten in too many cases to
be reliable, instead always use the flag instead of trying to have
it both ways.

The main issue this fixes is where there are parallel decodes and a
demuxer read outstanding, one decode completes with an error, and
the new decoder is initialized before the demuxer read completes.

Previously this would stomp the pending read state and we'd try to
issue a new demuxer read when the decoder initialization completed,
blowing up the demuxer in the process.

BUG=597605
TEST=new unittest

Review-Url: https://codereview.chromium.org/2110463003
Cr-Commit-Position: refs/heads/master@{#402667}
(cherry picked from commit 5d162a6)

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

Cr-Commit-Position: refs/branch-heads/2743@{#542}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

Merge to M52 on behalf of warx@.

When getting screensize for powerwash reset, making sure the currentScreen is 'reset', not 'account-picker'.

BUG=615088
[email protected], [email protected]
TEST=Multiple tests on M52, the corrupted powerwash proposal UI doesn't happen any more.
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2109763003
Cr-Commit-Position: refs/heads/master@{#402676}
(cherry picked from commit 956d75c)

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

Cr-Commit-Position: refs/branch-heads/2743@{#543}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

This reverts commit 706549d.

Causing crashes

BUG=624482

Cr-Commit-Position: refs/branch-heads/2743@{#544}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

Cr-Commit-Position: refs/branch-heads/2743@{#545}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

…t's not stable.""

This reverts commit ee1dfc7.

Reverting from M52 branch, broke the build

BUG=597605

Cr-Commit-Position: refs/branch-heads/2743@{#546}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

Cr-Commit-Position: refs/branch-heads/2743@{#547}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

…stable."

The pending demuxer read state is overwritten in too many cases to
be reliable, instead always use the flag instead of trying to have
it both ways.

The main issue this fixes is where there are parallel decodes and a
demuxer read outstanding, one decode completes with an error, and
the new decoder is initialized before the demuxer read completes.

Previously this would stomp the pending read state and we'd try to
issue a new demuxer read when the decoder initialization completed,
blowing up the demuxer in the process.

BUG=597605
TEST=new unittest

Updates:
- Includes missing base::RunLoop() header present in M53.

Review-Url: https://codereview.chromium.org/2110463003
Cr-Commit-Position: refs/heads/master@{#402667}
(cherry picked from commit cb4f8d08c791b49fed65b02818d01a818b4ec944)

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

Cr-Commit-Position: refs/branch-heads/2743@{#548}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

BUG=624503

Review-Url: https://codereview.chromium.org/2102883005
Cr-Commit-Position: refs/heads/master@{#403167}
(cherry picked from commit ef5b4a2)

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

Cr-Commit-Position: refs/branch-heads/2743@{#549}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

This CL reduces the conditions on dropping frames to just
|waiting_for_idr_|. We don't need to consider whether there is a pending
config change (this should be a decode error if we are not waiting) or
whether |session_| is set (|waiting_for_idr_| covers this).

BUG=623892

Review-Url: https://codereview.chromium.org/2101183004
Cr-Commit-Position: refs/heads/master@{#402853}
(cherry picked from commit fcd0ee5)

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

Cr-Commit-Position: refs/branch-heads/2743@{#550}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

Cr-Commit-Position: refs/branch-heads/2743@{#551}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

BUG=617786

Review-Url: https://codereview.chromium.org/2098973002
Cr-Commit-Position: refs/heads/master@{#402033}
(cherry picked from commit 8fe1d53)

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

Cr-Commit-Position: refs/branch-heads/2743@{#552}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

Only the network prediction enabled preference should be used to
schedule or cancel periodic GCM task. The GCM task itself will run only
when suitable for precaching.

BUG=616956

Review-Url: https://codereview.chromium.org/2037913002
Cr-Commit-Position: refs/heads/master@{#398119}
(cherry picked from commit 2fd4cfe)

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

Cr-Commit-Position: refs/branch-heads/2743@{#553}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

It's possible that NotifyError() is called between Initialize() and
CompleteInitialization() which would previously result in a null pointer
dereference. Now initialization is completed with an error.

BUG=623740

Review-Url: https://codereview.chromium.org/2109343002
Cr-Commit-Position: refs/heads/master@{#403251}
(cherry picked from commit 3154c1f)

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

Cr-Commit-Position: refs/branch-heads/2743@{#554}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

Fetcher pool accepts limited number of requests which are fetched in
parallel. If the pool is full, precache manifest resources should not be
added to it.

BUG=606231

Review-Url: https://codereview.chromium.org/2037903002
Cr-Commit-Position: refs/heads/master@{#399387}
(cherry picked from commit b2754f7)

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

Cr-Commit-Position: refs/branch-heads/2743@{#555}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

When Chrome is started by the user, periodic task will be scheduled in
stable build, if user is part of field trial.

Remove boot receiver intent to schedule periodic task. Since the GCM
task is persisted, this is not needed.

When Chrome apk upgrade completes, schedule the periodic task if
precache has been enabled in shared preferences.

BUG=619212

Review-Url: https://codereview.chromium.org/2064313002
Cr-Commit-Position: refs/heads/master@{#402025}
(cherry picked from commit 00a48bb)

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

Cr-Commit-Position: refs/branch-heads/2743@{#556}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

…s full"

This reverts commit b2754f7.

BUG=624936

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

Cr-Commit-Position: refs/branch-heads/2743@{#557}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

… press

When opening tabs in other windows or moving tabs between windows in Android
N+ multi-window mode, include intent extras so that Chrome knows the intent
came from Chrome and does not close the app when the 'back' button is pressed.

BUG=624022
[email protected]

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

Original-Review-Url: https://codereview.chromium.org/2106953002
Original-Cr-Commit-Position: refs/heads/master@{#403030}
Cr-Commit-Position: refs/branch-heads/2743@{#558}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

Cr-Commit-Position: refs/branch-heads/2743@{#559}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

…" to M52

This CL optimize HTMLSelectElement::resetToDefaultSelection(). We can quit the
loop if a selected OPTION was removed.

Removing 20,000 OPTIONs: 7,595ms -> 6,358ms

BUG=620142, 624220

Review-Url: https://codereview.chromium.org/2108883003
Cr-Commit-Position: refs/heads/master@{#402709}
(cherry picked from commit 6aa0504)

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

Cr-Commit-Position: refs/branch-heads/2743@{#560}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

…o M52

Replace Vector::clear() with Vector::resize(0) to avoid to deallocate Vector
buffers.

Removing 20,000 OPTIONs: 7,595ms -> 5,779ms

BUG=624220

Review-Url: https://codereview.chromium.org/2105863003
Cr-Commit-Position: refs/heads/master@{#402720}
(cherry picked from commit 8881397)

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

Cr-Commit-Position: refs/branch-heads/2743@{#561}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

…chor()." to M52.

Do not update m_cachedStateForActiveSelection if it's a
menulist. m_cachedStateForActiveSelection is used only in listboxes.

Removing 20,000 OPTIONs: 4,787ms -> 3,772ms

BUG=624220

Review-Url: https://codereview.chromium.org/2104883004
Cr-Commit-Position: refs/heads/master@{#402765}
(cherry picked from commit 25445ac)

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

Cr-Commit-Position: refs/branch-heads/2743@{#562}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

…ion()." to M52.

If we remove a selected OPTION from a SELECT element, selectOption() called from
resetToDefaultSelection() doesn't need to call deselectItemsWithoutValidation()
because there are no other selected OPTIONs.

- !multiple() doesn't imply DeselectOtherOptions.  Updates existing callsites of
  selectOption().
- Make SelectOptionFlags mandatory.

Removing 20,000 OPTIONs: 6,348ms -> 5,324ms

BUG=624220

Review-Url: https://codereview.chromium.org/2110003002
Cr-Commit-Position: refs/heads/master@{#402767}
(cherry picked from commit 454e595)

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

Cr-Commit-Position: refs/branch-heads/2743@{#563}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

https://helpx.adobe.com/security/products/flash-player/apsb16-18.html

BUG=412078
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:closure_compilation
[email protected]

Review-Url: https://codereview.chromium.org/2113703002
Cr-Commit-Position: refs/heads/master@{#403184}
(cherry picked from commit d5299ed)

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

Cr-Commit-Position: refs/branch-heads/2743@{#564}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

When a panel is requested to show, it may not be visible yet and
isShowing will return false. If two panels try to show simultaneously
this can cause the incorrect panel to appear. This change keeps track
of whether peek has been called so there can be a corresponding close
call, regardless of panel visibility. closePanel(...) and
requestPanelShow(...) are not used in every case that closes or opens
the panel; the close and peek methods are used instead.

BUG=624054, 623017

Review-Url: https://codereview.chromium.org/2109823002
Cr-Commit-Position: refs/heads/master@{#402843}
(cherry picked from commit 296d30e)

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

Cr-Commit-Position: refs/branch-heads/2743@{#565}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

Previous CL on authorization timeout decrease is being reverted https://codereview.chromium.org/2106373002/, this one should be landed instead.

The reason is we hit authorization timeout on platforms other than Windows (https://uma.googleplex.com/p/chrome/timeline_v2?sid=74e6fc3b3d0ef041f64f37272402ebb1), but the goal was to address windows driver hangs only.

BUG=615589

Review-Url: https://codereview.chromium.org/2116443002
Cr-Commit-Position: refs/heads/master@{#403164}
(cherry picked from commit b9debcd)

[email protected]
NOTRY=true
NOPRESUBMIT=true

Review-Url: https://codereview.chromium.org/2119843003
Cr-Commit-Position: refs/branch-heads/2743@{#566}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

…ction errors.

BUG=622537

Review-Url: https://codereview.chromium.org/2090703003
Cr-Commit-Position: refs/heads/master@{#401526}
(cherry picked from commit cd5f1c6)

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

Cr-Commit-Position: refs/branch-heads/2743@{#567}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

Download was cancelled when a dangerous download infobar is dismissed.
We missed it in the previous CL.

[email protected],[email protected]
BUG=618864

Review-Url: https://codereview.chromium.org/2111983002
Cr-Commit-Position: refs/heads/master@{#403274}
(cherry picked from commit 513a888)

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

Cr-Commit-Position: refs/branch-heads/2743@{#568}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

BUG=621068
[email protected]

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

Cr-Commit-Position: refs/branch-heads/2743@{#569}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

This patch prevents the thread watching a USB device connection file
descriptor from entering a brief loop when the device is disconnected
by canceling the watch on the FD when it encounters an ENODEV. Otherwise
the FileThreadHelper will continue attempting to read from the
descriptor until UsbDeviceHandleUsbfs::OnDisconnect is called.

BUG=422562

Review-Url: https://codereview.chromium.org/2011653005
Cr-Commit-Position: refs/heads/master@{#396064}
(cherry picked from commit 3f0cce7)

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

Cr-Commit-Position: refs/branch-heads/2743@{#570}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

Forces all input devices to use xinput1, the previous path,
until all the kinks are worked out with the new xinput2 path.

BUG=616308

Review-Url: https://codereview.chromium.org/2108283002
Cr-Commit-Position: refs/heads/master@{#402966}
(cherry picked from commit f7e731e)

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

Cr-Commit-Position: refs/branch-heads/2743@{#571}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

Previously, Page::pluginData() returned nullptr when the Page's main
frame was a RemoteFrame.  This caused navigator.plugins and
navigator.mimeTypes to both return empty arrays from an OOPIF.

Page::pluginData() needed the main frame to run the
FrameLoader::allowPlugins check on it.  This CL moves this check to
happen on the actual LocalFrame that needs to access
Page::pluginData().

BUG=612200, 607981, 616445

Review-Url: https://codereview.chromium.org/1990343002
Cr-Commit-Position: refs/heads/master@{#394942}
(cherry picked from commit fb92f3e)

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

Cr-Commit-Position: refs/branch-heads/2743@{#572}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

Prior to this, the client ID was being counted on initial startup
as well as any cold start refocuses of the CustomTabs.  This moves
the tracking to match StartedInitially which checks for the
existence of getSavedInstanceState()

BUG=622366

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

Review-Url: https://codereview.chromium.org/2115613002
Cr-Original-Commit-Position: refs/heads/master@{#403220}
Cr-Commit-Position: refs/branch-heads/2743@{#573}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

Cr-Commit-Position: refs/branch-heads/2743@{#574}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

…n sync is not active.

There are two places users can update their cloud services pref:
- First run flow, with a checkbox
- Contextual menu, with a toggle

Currently, users can only update their cloud services pref if they have sync enabled. There is no technical tie-in between having sync active and using cloud services. This change makes it such that users can toggle their cloud services pref locally if sync is inactive. Now, we only check that the user is authenticated. While sync is off, however, the pref will not sync across their devices.

In the event where the user has already acknowledged the first run flow (locally on the profile), then turned on sync, we continue to enable cloud services.

[Reland Comments] This was initially reverted because it caused failures on official bots; there were #includes that were mistakenly removed.

BUG=621255, 623330
TBR=msw, imcheng
NOTRY=true
NOPRESUBMIT=true

Committed: https://crrev.com/19a9b8f1411afe64b2163261a04245f617e25e17
Cr-Commit-Position: refs/heads/master@{#402072}

patch from issue 2078213002 at patchset 160001 (http://crrev.com/2078213002#ps160001)

Review-Url: https://codereview.chromium.org/2093353002
Cr-Commit-Position: refs/heads/master@{#402596}
(cherry picked from commit eae3fc0)

Review-Url: https://codereview.chromium.org/2115203002
Cr-Commit-Position: refs/branch-heads/2743@{#575}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

Cr-Commit-Position: refs/branch-heads/2743@{#576}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

Cr-Commit-Position: refs/branch-heads/2743@{#577}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

It was possible for two touch moves that had acks to get coalesced together
and the main thread would only process one and deliver the ack for it. This
caused a situation where the hung renderer timer was getting fired because
there was an outstanding ack in the count. And this timer forced the
omnibox to not go away.

A large portion of this change (plumbing the ack_state will go away when
I land my multi-thread main_thread_event_queue design); but since this
needs to be merged back to M52 this is safest.

BUG=616991

Review-Url: https://codereview.chromium.org/2094323002
Cr-Commit-Position: refs/heads/master@{#402703}
(cherry picked from commit b08721e)

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

Cr-Commit-Position: refs/branch-heads/2743@{#578}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

Since we now route Gesture events directly to the guest renderer, there
is no longer any event to focus the BrowserPlugin in the embedder
renderer, meaning that even though touch/gesture events work properly,
the guest may not receive keyboard input.

This CL provides a temporary fix by sending a synthetic GestureTapDown
to the embedder on TouchStarti, in parallel with sending the TouchStart
directly to the guest. The synthetic event focuses the BrowserPlugin.

This CL also fixes two tests that were still sending Gestures to the
embedder.

When BrowserPlugin is removed, this code will disappear along with
RenderWidgetHostViewGuest.

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

Review-Url: https://codereview.chromium.org/2101663002
Cr-Commit-Position: refs/heads/master@{#403308}
(cherry picked from commit 347f246)

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

Cr-Commit-Position: refs/branch-heads/2743@{#579}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

This is the CL to revert the related middle button click changes. We
decided to revert those changes because the issues that were caused by
suppressing click event for middle button was hard to fix without having
that event. Particularly the ability to prevent opening a new tab which
can be done by "preventDefault"ing the click event of middle button was
removed as the result of the original change. For now we revert these
changes and we pursue the line of adding a new event for non-primary
button click to be able to fix these problem in a more clean way.

Revert "Prevent sending click event for non primary button"

This reverts commit 76fea00.

Revert "Dispatch middle click manually by tracking mouse"

This reverts commit 88eb111.

Revert "Fix history page middle click action"

This reverts commit a154aed.

BUG=255,618593,617444,611019,617875
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2107093003
Cr-Commit-Position: refs/heads/master@{#403496}
(cherry picked from commit 4d9d918)

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

Cr-Commit-Position: refs/branch-heads/2743@{#580}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

Cr-Commit-Position: refs/branch-heads/2743@{#581}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

SwapBuffersAsync is not supported on non-freon devices.
Use SupportsAsyncSwap to decide to call SwapBuffersAsync
or SwapBuffers.

BUG=chromium:565759
TEST=Run VDA test on nyan and oak.

Review-Url: https://codereview.chromium.org/2098573005
Cr-Commit-Position: refs/heads/master@{#402102}
(cherry picked from commit 3647b2d)

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

Cr-Commit-Position: refs/branch-heads/2743@{#582}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

Cr-Commit-Position: refs/branch-heads/2743@{#583}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

NOTRY=true
NOPRESUBMIT=true
[email protected], [email protected]
[email protected]

BUG=625839

Review-Url: https://codereview.chromium.org/2128433002
Cr-Commit-Position: refs/branch-heads/2743@{#584}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

BUG=625936

Review-Url: https://codereview.chromium.org/2122143002
Cr-Commit-Position: refs/heads/master@{#403899}
(cherry picked from commit 180530e)

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

Cr-Commit-Position: refs/branch-heads/2743@{#585}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

Prior to this change, native pages that did not use the default color
caused the progress bar color to be recomputed. This would cause the
progress bar to be an incorrect color when navigating a non-native
page and in the case of pages with no theme, they would never get
updated.

This change adds a parameter to the function responsible for computing
theme color to force the default progress bar color. In practice this
parameter is true if the page is native.

BUG=621847

Review-Url: https://codereview.chromium.org/2088933002
Cr-Commit-Position: refs/heads/master@{#402196}
(cherry picked from commit 0f222e2)

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

Cr-Commit-Position: refs/branch-heads/2743@{#586}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

This removes an extra '}' that accidentally got added in
http://crrev.com/20447ead8ba4b9bf3310da0d80a23a199aba1d60

BUG=625014

Review-Url: https://codereview.chromium.org/2111383002
Cr-Commit-Position: refs/heads/master@{#403395}
(cherry picked from commit 9c6b6e1)

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

Cr-Commit-Position: refs/branch-heads/2743@{#587}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

… by the browser.

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

Review-Url: https://codereview.chromium.org/2069853002
Cr-Commit-Position: refs/heads/master@{#400495}
(cherry picked from commit 92cad45)

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

Cr-Commit-Position: refs/branch-heads/2743@{#588}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

…ed setup.

Users who don't have first setup complete, but are signed in without sync
suppressed, are in an invalid state, likely from previous issues in the
sign in flow. We were purging their sync data over-aggressively on startup
previously, causing a resync of the control types on each restart. Now we
simply leave the data around, and only purge if the user is actually signed
out.

BUG=624915

Review-Url: https://codereview.chromium.org/2113453006
Cr-Commit-Position: refs/heads/master@{#403382}
(cherry picked from commit 6862397)

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

Cr-Commit-Position: refs/branch-heads/2743@{#589}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

change 5041a16 was merged into M52 but
failed on android because trunk doesn't contain the code anymore.

Patch the code manually to fix the build.

BUG=616991

(cherry picked from commit 2ad437491349565cfe2a9d38ccbc469febdb2399)

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

Cr-Commit-Position: refs/branch-heads/2743@{#590}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

Cr-Commit-Position: refs/branch-heads/2743@{#591}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

The beforeinstallprompt event signals an imminent app install banner for
a page. This CL adds UMA stats for preventDefault() being called on the
event (stopping the banner from appearing), and for prompt() being
called on the event (making the banner appear subsequent to
a preventDefault()).

BUG=625716

Review-Url: https://codereview.chromium.org/2122783002
Cr-Commit-Position: refs/heads/master@{#404039}
(cherry picked from commit 4f6382c)

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

Cr-Commit-Position: refs/branch-heads/2743@{#592}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

Added logs are printed out only during enrollment process.

BUG=586961

Review-Url: https://codereview.chromium.org/2112553008
Cr-Commit-Position: refs/heads/master@{#403769}
(cherry picked from commit 59d7359)

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

Cr-Commit-Position: refs/branch-heads/2743@{#593}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

BUG=598702

Review-Url: https://codereview.chromium.org/2065243002
Cr-Commit-Position: refs/heads/master@{#402311}
(cherry picked from commit 3e84f9c)

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

Cr-Commit-Position: refs/branch-heads/2743@{#594}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

Cr-Commit-Position: refs/branch-heads/2743@{#595}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

…l CL crrev.com/1988113004).

The original CL was later reverted (CL crrev.com/2068953003) due to
frequent failures of the SAMLPolicyTest.SAMLInterstitialNext test.

This follow-up CL should resolve the tests flakiness.

The problem with the original CL was that it could introduce raising the
"ready" event too early, so that the test code could start working when
the webview was still pointing to the blank page.

BUG=613245,620353
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2082533002
Cr-Commit-Position: refs/heads/master@{#400703}
(cherry picked from commit 93dc10b)

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

Cr-Commit-Position: refs/branch-heads/2743@{#596}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

This updates from revision
2226f9cc92213d0d68a74ecb535b15b3af00388a (2016-05-09)

to revision
28e17a0f8f26f1bddfbd62d9861b223efa7792bc (2016-07-06)

[email protected]
BUG=610498

Review-Url: https://codereview.chromium.org/2127883004
Cr-Commit-Position: refs/heads/master@{#404050}
(cherry picked from commit 7eb9569)

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

Cr-Commit-Position: refs/branch-heads/2743@{#597}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

…quently

When JS iteratively constructs a DOM tree containing form controls, didAssociateFormControlsTimer was fireing for every iteration, causing a massive slow down.

BUG=614856

Review-Url: https://codereview.chromium.org/2055693002
Cr-Commit-Position: refs/heads/master@{#404083}
(cherry picked from commit 6e1c00f)

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

Cr-Commit-Position: refs/branch-heads/2743@{#598}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

dirtyForLayoutFromPercentageHeightDescendants invalidates too much. We already
have code to handle this case, so remove this call. We did have a bug in
that code though -- we do need to force layout on flex items even if did not
lay them out already: such percentages are only resolvable if the flexbox has
a definite height. However, whether the flexbox height is definite may have
changed since the last layout. So, we need to relayout in either case.

The similar code in applyStretchAlignment does not have this issue because
percentages in the cross axis can be resolved independent of whether the
flexbox height itself is definite.

This is covered by an existing test; the call to
dirtyForLayoutFromPercentageHeightDescendants was previously covering this case
but is slower.

This caused a massive performance regression (many minutes to lay out a
flexbox-based website instead of a few seconds).

TEST=css3/flexbox/definite-cross-sizes.html
BUG=595361,617792
[email protected],[email protected]

Review-Url: https://codereview.chromium.org/2128093003
Cr-Commit-Position: refs/heads/master@{#404056}
(cherry picked from commit e31affc)

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

Cr-Commit-Position: refs/branch-heads/2743@{#599}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

The background color of the toolbar is proceduraly generated. When
navigating from a native page, the theme color for the toolbar is
overridden to use the default. This change accounts for incognito
native pages.

BUG=624684

Review-Url: https://codereview.chromium.org/2113553003
Cr-Commit-Position: refs/heads/master@{#403469}
(cherry picked from commit dfbb886)

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

Cr-Commit-Position: refs/branch-heads/2743@{#600}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

…d to default Always Translate checked

BUG=622854

Review-Url: https://codereview.chromium.org/2090283002
Cr-Commit-Position: refs/heads/master@{#403232}
(cherry picked from commit 2364a39)

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

Cr-Commit-Position: refs/branch-heads/2743@{#601}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

Cr-Commit-Position: refs/branch-heads/2743@{#602}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

Cr-Commit-Position: refs/branch-heads/2743@{#603}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

Cr-Commit-Position: refs/branch-heads/2743@{#604}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

When running video_encode_accelerator_unittest :

../../media/gpu/video_encode_accelerator_unittest.cc:301: Failure
Value of: 0
Expected: reinterpret_cast<off_t>(&test_stream->aligned_in_file_data[0]) & 63
Which is: 32
File should be mapped at a 64 byte boundary

Also reuse base::bits::Align.

BUG=624254
TEST=video_encode_accelerator_unittest

Review-Url: https://codereview.chromium.org/2110063002
Cr-Commit-Position: refs/heads/master@{#403435}
(cherry picked from commit b79f630)

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

Cr-Commit-Position: refs/branch-heads/2743@{#605}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

New devices would not be detected on Linux. Worse,
things would get very confused if you disconnected
one device and connected another.

This has been broken for four months, with
crrev.com/17cd1b10ded3a5e730bbcb39c57a6d2f8e16a51e

BUG=625123

Review-Url: https://codereview.chromium.org/2126023004
Cr-Commit-Position: refs/heads/master@{#404092}
(cherry picked from commit e74c2a9)

[email protected]

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

Cr-Commit-Position: refs/branch-heads/2743@{#606}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

This patch applies the same heuristic fix as break-word to break-all.

Since the switch to the complex path, r385693 fixed the performance and
correctness issue of break-word and break-all in common cases. However,
it also introduced a performance regression when a word is really long,
such as minimized JS.

This can be fixed by taking over the ShapeResult to the next lines as
Gecko does, but it will require larger overhaul of the line breaker and
need more time to bake.

As an interim fix, r387974 introduced a heuristic fix for break-word.
This patch applies the same heuristic to break-all.

This patch also revealed that the fix for crbug.com/603679 was not
correct. MidWordBreak must be recomputed when floats pushed the line
down and available width changed. This patch includes the fix.

BUG=622810, 603679

Review-Url: https://codereview.chromium.org/2077313002
Cr-Commit-Position: refs/heads/master@{#403830}
(cherry picked from commit d24d249)

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

Cr-Commit-Position: refs/branch-heads/2743@{#607}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

…tep.

This eliminates redundant testing of vertices for orientation with
respect to the splitting polygon. Previously, up to 3 sets of tests
were made (once to determine whether the polygon was split, then once
during the split, and then finally to determine the orientation of the
split polygons.

Merging these steps in order to reuse calculated values also eliminates
the possibility that different calculations in testing and splitting
could be inconsistent.

BUG=606984
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
NOTRY=true
NOPRESUBMIT=true

Committed: https://crrev.com/89c62c8f69d76471e866f21ee4f1ae5e0c5bca48
Review-Url: https://codereview.chromium.org/2043283002
Cr-Original-Commit-Position: refs/heads/master@{#399459}
Cr-Commit-Position: refs/heads/master@{#403559}
(cherry picked from commit 3e9082b)

Review-Url: https://codereview.chromium.org/2136493002
Cr-Commit-Position: refs/branch-heads/2743@{#608}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

This CL lands AVDA fixes that were originally landed individually
but were reverted due to crbug.com/624482 .  Together, these allow
AVDA to handle cases where Android's mediaserver hangs when trying
to allocate a hardware codec.

The individual commit messages follow.

[M52] Make AVDA fall back to software decoding if needed.

Merge of https://codereview.chromium.org/2084143002

Android MediaCodec creation will sometimes never come back.  On a
N7 (2013) with Lollipop, this can happens when an attempt to allocate
a hardware codec fails, and falls back to a software codec.  Once
mediaserver gets into a bad state, future attempts to create a
hardware codec will hang.  As a result, no additional AVDA instances
will get codecs.  Further, destroying any of them will hang the gpu
process when it tries to join the thread that handles construction.

This CL does several things:
    - Don't join the construction thread if there are outstanding
      MediaCodec creations on it.  While this may sometimes not
      shut down the thread if the AVDA is destroyed while the
      creation is pending (and would return if we just waited a bit
      longer), the thread will be shut down the next time an AVDA
      instance is destroyed.  It isn't leaked permanently.

    - Fall back to requesting a software codec if we believe that
      construction of a hardware codec is hung.  We don't attempt
      to salvage the AVDA instance(s) that have pending HW codecs,
      but future AVDA instances will fall back to software.  If
      those HW codecs are eventually allocated, then we will start
      requesting HW codecs again.  For example, if we simply time
      out too quickly, or if mediaserver is restarted, then we can
      try for hardware codecs for future AVDA instances.

    - Release hardware codecs on a separate thread, since that can
      hang too if mediaserver is in a bad state.

[M52] Fix Log formatting in MediaCodecUtils.

Merge of: https://codereview.chromium.org/2091253003

[M52] Remove usage of MediaCodec.getName(), use proxy instead.

Merge of: https://codereview.chromium.org/2114473002

This method does not exist API < 18 and it is simpler to just
trust the |require_software_codec| value which is the inverse
of |allow_autodetection_|.

[M52] Release MediaCodec on another thread more often.

Merge of: https://codereview.chromium.org/2116573002

Since MediaCodec::release() can hang, this CL moves more cases of
it to a separate thread when needed.  Previously, we did this only
during AVDA destruction.  This CL adds support for other cases in
which we replace or clear |media_codec_|.

BUG=613238,624482
[email protected]
NOPRESUBMIT=true
NOTRY=true

Review-Url: https://codereview.chromium.org/2143433002
Cr-Commit-Position: refs/branch-heads/2743@{#609}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

The blocking bugs are fixed so we can turn it back on.

BUG=597467

Review-Url: https://codereview.chromium.org/1997483002
Cr-Commit-Position: refs/heads/master@{#395385}
(cherry picked from commit 1580687)

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

Cr-Commit-Position: refs/branch-heads/2743@{#610}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

Another speculative fix to ensure that the provider is not
deleted before the compositor is finished with it.

BUG=595980, 623217

NOTRY=TRUE
NOPRESUBMIT=TRUE
[email protected]

Review-Url: https://codereview.chromium.org/2053133003
Cr-Commit-Position: refs/heads/master@{#399209}
(cherry picked from commit 3ac77d9)

Review-Url: https://codereview.chromium.org/2139903002
Cr-Commit-Position: refs/branch-heads/2743@{#611}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}

Cr-Commit-Position: refs/branch-heads/2743@{#612}
Cr-Branched-From: 2b3ae3b-refs/heads/master@{#394939}