GitLab

BUG: 16870075
Change-Id: I7d1971f2862fa27ae4469519a81029f85eab38bb

> Rename the "linker_script_copy" target to "android_exports" and move the
> link_settings clause to that target. This avoids the linker flag being
> duplicated once for every target which includes jni_generator.gypi,
> which causes problems on some linker versions.
>
> BUG=402003
>
> Review URL: https://codereview.chromium.org/473173004
>
> Cr-Commit-Position: refs/heads/master@{#289941}
> git-svn-id: svn://svn.chromium.org/chrome/trunk/src@289941 0039d316-1c4b-4281-b951-d872f2087c98

BUG: 16870075
Change-Id: Ic8a0906563edc777c3fc9a831643b8b535ede184

> This removes the eager class registration from RegisterNatives when possible.
>
> BUG=402003
> TBR=sievers@chromium.org, brettw@chromium.org, torne@chromium.org
>
> Review URL: https://codereview.chromium.org/491043002

BUG: 16870075
Change-Id: Ia2cdbddad9a12f9101290af4c06684706eac63c6

> Rather than registering all jni bindings at startup, only get references
> to the class object for those files which require bindings. All others
> are satisfied by exporting symbols which can be found automatically by
> the VM.
>
> BUG=402003
>
> Review URL: https://codereview.chromium.org/454923002

BUG: 16870075
Change-Id: I8d7617c87ac10cb9833cdb370bc6718bd58fd587

Re-generate .mk files after "Cherry-pick: Revert "Merge 281715 "[Android WebView] Terminate execution of stuck JS ..."""

As the patch was changing android_webview.gyp file, we have to update .mk files

Bug: 13509205, 17175122, 17173843
Change-Id: I0b736bb8ced4e63040b6c203cc29dbebb78aaaa0

Merge "Cherry pick   Android WebView: clean up the AwContentsClientBridge webcontents userdata." into lmp-dev

Bug: 17396873

Original description:

When we destroy the AwContentsClientBridge, clear the pointer to it
held by webcontents user data.

Also ensure that if we don't post the callback to the java side
to run the js dialog callback in the embedding app that we run
the callback.

BUG=411399
Committed: https://chromium.googlesource.com/chromium/src/+/bafb7ef3239ed1db29393ca1d528af08a2f19dfb

Change-Id: Ib9fbb4fc6b4e4dc45688db814e3ec886d469e222

The approach implemented in the patch is prone to crashing Blink bindings code.
See more comments in the bugs.

Bug: 13509205, 17175122, 17173843

Original description:

    Revert "Merge 281715 "[Android WebView] Terminate execution of stuck JS ...""

    This reverts commit 8508a2f18909b0768d273bb9161aee749f47beca.

    As described in the bug, the proposed approach is invalid, as Blink's bindings
    code isn't ready to deal with terminated scripts properly, resulting in random
    crashes. Hence reverting the patch.

    BUG=390906

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

    Cr-Commit-Position: refs/branch-heads/2062@{#587}
    Cr-Branched-From: 2e531f7c26d0d9e2aa0cced17a35eea6687dc58c-refs/heads/master@{#278856}

Change-Id: I6805a85cefef55492d5b3934b4fbd9263c1d004e

This should not happen and BrowserViewRenderer/GlobalTileManager would
be in an invalid state when it happens.
Remove this CHECK before we ship L.

BUG: 17369933

Change-Id: I288b67ac9a8bd018aed207decabb37de41889a73

BUG: 17403571
Change-Id: Ia2fab595694aa62578f3f771a322c2938662ba94

> Move the include of the Mac TargetConditionals.h file to after we've
> checked if we're building for Android. Apparently this file doesn't
> exist on all macs used to build android and the rest of android builds
> fine without it, so including it there causes the build to fail. It
> appears to only be used to test TARGET_OS_IPHONE which will never be
> true on android.
>
> BUG=
>
> Review URL: https://codereview.chromium.org/538563002
>
> Cr-Commit-Position: refs/heads/master@{#293495}

Bug: 17401514

> Android's bionic C library is intending to adopt the same semantics as
> glibc for strerror_r: define the version that returns char* if the
> source is compiled with _GNU_SOURCE instead of the POSIX version which
> returns int. Add __BIONIC__ to the condition for
> USE_HISTORICAL_STRERRO_R so that Chromium will still work.
>
> BUG=
>
> Review URL: https://codereview.chromium.org/491893002
>
> Cr-Commit-Position: refs/heads/master@{#291050}
> git-svn-id: svn://svn.chromium.org/chrome/trunk/src@291050 0039d316-1c4b-4281-b951-d872f2087c98

Bug: 17384482
Change-Id: Ie80073df1327c8e415d83c1c9321cc3ca1beaf01

When using a prebuilt libwebviewchromium, instead of skipping the entire
directory just include the makefiles needed to build V8 for
external/chromium-libpac to use.

Bug: 17228462
Change-Id: I0f543120265707d47674a85e059787a2c77611bd

Merge "Cherry pick "Cache pending JS bridge sync IPC replies, and send in case of RenderFrame deletion."" into lmp-dev

conflicts in:
  content/common/android/gin_java_bridge_errors.cc
  content/common/android/gin_java_bridge_errors.h

Bug: 16840290

Original description:
Cache pending JS bridge sync IPC replies, and send in case of
RenderFrame deletion.

When the WebView app makes a call to java over the JavaScriptBridge,
we leave the renderer hanging on a synchronous IPC. Once control
is passed into Java, it's possible that the WebView may get destroyed
(and thus the IPC channel back to the renderer closed) which means we
can't unblock the renderer waiting on the IPC response.

Instead we cache the IPC reply message and while waiting on Java to come
back to us, if we detect that the RenderFrame has been deleted, send a
reponse back before the IPC channel is closed.

BUG=408188
Committed:
https://chromium.googlesource.com/chromium/src/+/5d3e001f79c137b2ba0f5b0e9489abea616f3431

Change-Id: I7f1b28e297059eb69c5686316b47d926ea8a3d4f

These changes have landed to the system copy of libwebP in
Idf2756b8881d10001c0663bca454aac86ab30a39

and this brings the WebView version in line with it.

Bug: 17028120
Change-Id: I9e150225d7fb8e280cb1e632dc184191ed94fae8

Clean cherry-pick of chromium
crrev.com/d3ba7205b5a0c9154b91357c8795e772833fa798

BUG: 17111986

Original description:

Currently, if |compositor_needs_continuous_invalidate_| is unset before
PostFallbackTick or FallbackTickFired, then the fallback ticks are
cancelled, but we never unset |block_invalidates_|, which will block
invalidates indefinitely.

Fix is simply always unset |block_invalidates_| even if we skip
the fallback tick.

Change-Id: I8bf65ae614a5ac697d5bc1b62c7cd11fbbd16cad

Cherry-pick with conflict of chromium
crrev.com/d7de03c45e06e104e3ba022e240f7bc88315e753

Conflicts:
	cc/layers/layer_impl.cc
	cc/layers/layer_impl.h
	cc/layers/picture_layer_impl.cc
	cc/layers/picture_layer_impl.h
	cc/resources/picture_layer_tiling.cc
	cc/resources/picture_layer_tiling.h
	cc/resources/tile_manager.cc
	cc/resources/tile_manager.h
	cc/trees/layer_tree_host_impl.cc
	cc/trees/layer_tree_impl.cc
	cc/trees/layer_tree_impl.h

BUG: 17315710

Original description:

This patch changes which tiles we report on. Previously, we logged
all of the available tiles. Now, we only log tiles that are active.
That is, only tiles that are on either active or pending trees are
logged.

The way this is done is as follows:
- Walk the tree, layers, tilings
- Insert all tiles from a tiling into a set
- Stuff those into a trace.

Change-Id: Ied16f30ee7e69873e12a2754054a39ecb7acc385

Fix strict mode violations in Android.

BUG=408525
Committed:
https://chromium.googlesource.com/chromium/src/+/6c4efa4876f1397b51d4e067d73ecb202b860147

Bug: 17313418
Change-Id: I1417d0cff8e6de00ef5dde601d1d5c404423d887

BUG:17316153

-----------------------------------------------------------

Fix a crash reported by monkey tests.

BUG=405504

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

Change-Id: I749a1740cd602f586895906977e1eaa006590f17
Cr-Commit-Position: refs/heads/master@{#292359}

BUG:17295749

---------------------------------------------------------------------

[aw] Fix crash when "misbehave" app exits fullscreen.

exitFullScreen() might be call without a prior call to
enterFullScreen() if a "misbehave" app overrides onShowCustomView
but does not add the custom view to the window. This fixes a
crash by returning early from exitFullScreen in that case.

BUG=408133

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

Change-Id: I297f84c42b4cb27d703c43b0e459003ea3425fc2
Cr-Commit-Position: refs/heads/master@{#292165}

Include tile manager state in lthi state dump

R=vmpstr,enne
BUG=401209

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

Cr-Commit-Position: refs/heads/master@{#289451}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@289451
0039d316-1c4b-4281-b951-d872f2087c98

Chromium revision: 0eded9ea3c713e1ce61b4f26c7a202c55f0302fe
Bug: 17315710

Change-Id: I5d47079abb36678a16d1fb245e4caa25c20c9067

Add source frame number to LayerTreeImpl::AsValueInto

Will help work around
https://code.google.com/p/trace-viewer/issues/detail?id=587

R=enne

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

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

Chromium change: 929378a002b5756a9f8501e292c157ecedfa36bb
Bug: 17315710

Change-Id: Ia409efc82e1d5d011906846c0c3304e0f36c4987

Will let us show gpu memory usage in a more-intuitive way in frame
viewer.

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@287998
0039d316-1c4b-4281-b951-d872f2087c98

Chromium revision: d1cb7ee309cc97dc8ccbb95da4e57a44af5bc924
Bug: 17315710

Change-Id: I2dfe624bbd030e78a314290d2d1b0b84cbfb8167

Cherry-pick with conflict of chromium crrev.com/290074

Conflicts:
	cc/resources/picture_layer_tiling.cc

BUG: 17303244
Change-Id: Ibbef79ee10c3a7b9abfec80b476092b7465e6417

Clean cherry-pick of chromium crrev.com/286085

BUG: 16133204

Original description:

One previous approach was to try and balance memory usage vs amount
of time we spend analyzing tiles. This patch switches it so that we
always analyze tiles in order to try and save as much memory as
possible.

This is due to the fact that there are some cases out there that
break the heuristic and use too much memory, when otherwise they
would be detected as solid.

As well, it enables analysis for gpu rasterization since it also
needs to start benefitting from these memory savings.

Change-Id: I909295b1ef94ea45b122d1758185f3f768a747b1

Merge "Cherry-pick: Only set accessibility focus on page load for browser tabs, not web views." into lmp-dev

Clean cherry-pick of chromium
https://crrev.com/61c6121a6cb9dc16f9786830655049d68dcde67c

BUG: 17000817

Original description:

Only set accessibility focus on page load for browser tabs, not web views.

BUG=406053

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

Change-Id: I09130c2598e71c878f85a7d8bf08f2519c337639
Cr-Commit-Position: refs/heads/master@{#291713}

Cherry-pick with conflict of
crrev.com/7fceb77977afd9af22215eb9cd28ab667567668e

Conflicts:
	cc/debug/rasterize_and_record_benchmark_impl.cc
	cc/layers/picture_layer_impl_unittest.cc
	cc/resources/picture_layer_tiling.cc
	cc/resources/picture_layer_tiling_unittest.cc
	cc/test/fake_picture_layer_tiling_client.cc
	cc/test/fake_picture_layer_tiling_client.h

BUG: 16548433

Original description:

This patch removes tiles from the recycle tree that were deleted from
the active tree as a result of a shifting live tiles rect. It is
important to do this, since if the active tree then would recreate
the deleted tile (ie, live tiles rect shift back), we have to ensure
that this tile will be shared when the next pending tree is created.
If we don't do it, we can run into a situation in which we will
continuously raster the same tile.

The patch does the following:
- Adds a way to get a recycled tree twin tiling.
- During LiveTilesRect tile deletion, deletes tiles from the same
  location from the recycle twin (if one exists).

Change-Id: I295cec01b476a97f68b0678d9d4322568662040f