Skip to content

GitLab

Switch branch/tag
  1. 08 Dec, 2014 1 commit
  3. 05 Dec, 2014 1 commit
  5. 13 Nov, 2014 2 commits
    • jdduke's avatar
      Cherry-pick: Reland [Android] Mark posted UI thread tasks as asynchronous · 692aa678
      jdduke authored 
      Clean cherry-pick of chromium
crrev.com/d51117a99a4e023e791134185c6db12b28028a1d

BUG: 18283959

Original description:

Chromium shares a message loop with Android on the browser UI thread.
This can cause problems when the associated Looper has a sync barrier,
preventing posted Chromium tasks from being dispatched until the
barrier is removed. Make this sharing more fair by marking all Chromium
Message tasks as asynchronous, avoiding stalls when there is a sync
barrier.

Note: This change was originally landed in crrev.com/512333002, but was
reverted to gather more data about sync barrier impact and investigate
alternative solutions. The investigation determiend that this approach
is fine for the near future, though it will likely evolve in time.

Change-Id: I9879a9c1bdad0dcec12c2bbee62356a5b12d9596
      692aa678
    • jdduke's avatar
      Cherry-pick: Revert of [Android] Experimental sync barrier detection for... · 7a4903d2
      jdduke authored 
      Cherry-pick: Revert of [Android] Experimental sync barrier detection for tracing (patchset #6 id:100001 of https://codereview.chromium.org/575103002/)

Cherry-pick of chromium
crrev.com/adefc40cb9652a2ea046bbdbef223d881f4a7463

Conflicts:
	base/android/java/src/org/chromium/base/SystemMessageHandler.java

BUG: 18283959

Original description:

Reason for revert:
Barrier detection is no longer necessary, see crrev.com/512333002.

Original issue's description:
> [Android] Experimental sync barrier detection for tracing
>
> When an Android View is invalidated outside of frame dispatch
> (animation/input/draw), a sync barrier may be inserted into the shared
> UI thread message loop. This effectively blocks dispatch of all Chrome
> tasks posted to the browser UI thread for an entire frame (or more if
> the View is continually invalidated).
>
> There are currently no easy or even automated ways to avoid this
> untimely invalidation, and judicious coding can only take us so far. As
> an intermediate assist in debugging the issue, use reflection and a
> crude form of MessageQueue inspection to trace known cases where the
> MessageQueue is blocked by a sync barrier.
>
> Note that this detection is not perfect, neither is it exact, but it's a
> solid proxy for informing traces about such pipeline stalls.
>
> BUG=407133
>
> Committed: https://crrev.com/85bceaa6e05ee1bf42ac220ddcbb50ca268c1ea4
> Cr-Commit-Position: refs/heads/master@{#296249}

Change-Id: Ie92ab895b864bf466ac092a1a1b7fdc80a8fd3ce
      7a4903d2
  7. 12 Nov, 2014 1 commit
  9. 29 Oct, 2014 1 commit
  11. 03 Oct, 2014 1 commit
  13. 01 Oct, 2014 2 commits
  15. 30 Sep, 2014 1 commit
  17. 25 Sep, 2014 1 commit
  19. 19 Sep, 2014 1 commit
  21. 11 Sep, 2014 1 commit
  23. 10 Sep, 2014 1 commit
  25. 09 Sep, 2014 1 commit
    • torne's avatar
      Cherrypick "Handle bionic's strerror_r in an ABI-compatible way." · d74b8cc5
      torne authored 
      > The previous fix in r291050 fixed source compatibility but broke ABI
> compatibility with older versions of bionic instead. Since older
> versions of bionic only provide the POSIX version of strerror_r we
> should instead make sure we always use that version.
>
> BUG=
>
> Review URL: https://codereview.chromium.org/552753002
>
> Cr-Commit-Position: refs/heads/master@{#293894}

Bug: 17384482
Change-Id: I91b55784ec64145882d12119a70acde163ea97e3
      d74b8cc5
  27. 08 Sep, 2014 3 commits
  29. 04 Sep, 2014 1 commit
  31. 28 Aug, 2014 2 commits
  33. 21 Aug, 2014 1 commit
  35. 19 Aug, 2014 2 commits
  37. 12 Aug, 2014 1 commit
  39. 06 Aug, 2014 1 commit
  41. 04 Aug, 2014 1 commit
  43. 01 Aug, 2014 3 commits
  45. 29 Jul, 2014 1 commit
  47. 22 Jul, 2014 1 commit
  49. 21 Jul, 2014 1 commit
  51. 15 Jul, 2014 1 commit
  53. 10 Jul, 2014 1 commit
    • Bo Liu's avatar
      Cherry-pick: base: Default android version to 4.4.99 · 1ec87773
      Bo Liu authored 
      Cherry-pick of https://codereview.chromium.org/381813002/

Original description:

Under-development Android versions do not have a numeric
version, so falls back to a "default version".

Using a real released Android version like 4.3.0 will
incorrectly trigger code paths, such has version-specific
gpu blacklists.

First attempt at fixing this was using 0.0.0, which caused
websites parsing Android version in the user agent to break.

So this is the second attempt, use the latest public major
version and minor version, and use a higher bug release
version to avoid conflicts with the gpu blacklist.

BUG: 16162131
Change-Id: Icbc68fbe118311b806f41a17593e9f3bc2a2f069
      1ec87773
  55. 01 Jul, 2014 1 commit
  57. 25 Jun, 2014 1 commit
  59. 20 Jun, 2014 1 commit
  61. 09 Jun, 2014 1 commit
  63. 03 Jun, 2014 1 commit