GitLab

Added flushing to python server to fix issue in Visual Studio output window.


BUG=136414
TEST=


Review URL: https://chromiumcodereview.appspot.com/10821046

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

With this change, target 'chrome' builds with the 10.7 SDK.

BUG=136844
TEST=none

Review URL: https://chromiumcodereview.appspot.com/10823049

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

This seems to have outlived its usefulness.

NOTRY=true
BUG=none
TEST=lol


Review URL: https://chromiumcodereview.appspot.com/10826040

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

Add matching OS_ANDROID guard in tests missing from
http://codereview.chromium.org/10806077/


Review URL: https://chromiumcodereview.appspot.com/10827051

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

This can decrease NaCl's total warm load time by ~15% for larger files.
The algorithm for resizing the buffer matches the one used by
AsyncResourceHandler.

BUG= none
TEST= none


Review URL: https://chromiumcodereview.appspot.com/10828024

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

BUG=138643
TEST=none

Review URL: https://chromiumcodereview.appspot.com/10823047

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

There is already an ash::GetRootWindowController, and it does the same thing.

BUG=none
TEST=none

Review URL: https://chromiumcodereview.appspot.com/10828037

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

- Moved CSS into shared/css similar to other about pages.
  (cleaned up style warnings during move).
- Added android specific CSS overrides where necessary.
- Removed flash section as it is not supported on Android.

BUG=
TEST=


Review URL: https://chromiumcodereview.appspot.com/10821026

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

Instead of enqueueing SPDY frames, enqueue SPDY streams that are ready to produce data. This allows us to lazily allocate a stream id.

The second CL was reverted because of use-after-free problems.  Producers were deleted before they were pop()'d from the WriteQueue, which turns out to be a no-no.  This version fixes this defect.

The initial CL was reverted because of memory leaks.  Both SpdyIOBufferProducers leaked the SpdyFrame they owned.  The second version of the CL fixes this defect.

Attempting to re-land 144649

Revert 147692 - Revert 144655 - Revert 144649

BUG=111708
TEST=net_unittests


Review URL: https://chromiumcodereview.appspot.com/10815074

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

BUG=137247

Review URL: https://chromiumcodereview.appspot.com/10821049

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

BUG=112525
TEST=unittests, manual

Review URL: https://chromiumcodereview.appspot.com/10827045

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

Drop frontbuffers with ui-use-gpu-process, synchronized with browser, decoupled from backbuffer drop.

On Aura, every time a tab is backgrounded, RenderWidgetHostViewAura will reset its handle to the front surface.  If that tab is foregrounded again, that front surface will not be used until synchronizing with the gpu process to make sure that surface is still available.  By doing this, the gpu process knows when it is safe to discard the front surface.

RWHVA sends a FrontSurfaceIsProtected(bool, int) message to the gpu process to keep it informed about front surface protection.  The int is a state-of-the-world identifier to protect from ABA issues.  RWHVA delays sending FrontSurfaceIsProtected(false) until after the current surface is certain to not be in use, namely after the compositor finishes the current frame and the browser thumbnailer is complete.


BUG=112842
TEST=Manual


Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=142408

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=142541

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=143590

Review URL: https://chromiumcodereview.appspot.com/10052018

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

BUG=108171


Review URL: https://chromiumcodereview.appspot.com/10808069

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

Iceberg builds .mpkgs, but Packages builds flat .pkgs. We switch to using
Packages because it can create "flag packages" that we can sign and 
signing is required for Mac OS X 10.8.

When we switched from .mpkg to .pkg, the keystone installer script was
not updated. So keystone installs are not happening.
Review URL: https://chromiumcodereview.appspot.com/10831041

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

BUG=134744, 117261


Review URL: https://chromiumcodereview.appspot.com/10682007

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

BUG=129471
TEST=


Review URL: https://chromiumcodereview.appspot.com/10834039

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

BUG=101244
TEST=N/A, only moving code, no change in functionality


Review URL: https://chromiumcodereview.appspot.com/10796062

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

BUG=133827


Review URL: https://chromiumcodereview.appspot.com/10827032

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

BUG=127664
TEST=Accelerated .mp4 video works on Chrome OS.

Review URL: https://chromiumcodereview.appspot.com/10824019

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

QuickDraw.h is gone, but the frameworks still exports the symbols
on 10.8. So just declare the functions for now, so that we can
build with the 10.7 SDK.

We can remove Carbon plugin support later.

BUG=136844
TEST=none
TBR=stuartmorgan,tony

Review URL: https://chromiumcodereview.appspot.com/10826036

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

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

TBR=tomhudson@chromium.org
BUG=none
TEST=none

Review URL: https://chromiumcodereview.appspot.com/10831038

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

Remove the second comparison group from the prerender field trials, and reorganize the code so that we can compile assert on the summation. The second group has already shown us our numbers are good. The compile time assertion should avoid fat finger errors that we've caught in other reviews (which would otherwise have been a _beta crasher_!).

I think we should also give consideration to renaming these histograms for ease of understanding. I know that makes a historic comparison cost, but it makes arriving new in this area so much easier.

I'll rebase the multiple prerender CL on top of this.

R=dominich@chromium.org
BUG=None

TEST=


Review URL: https://chromiumcodereview.appspot.com/10802062

TBR=gavinp@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10828041

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

BUG=
TEST=


Review URL: https://chromiumcodereview.appspot.com/10835006

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

1. base64, rand_util, threading, time and threads were previosly disabled in
base_untrusted. Remoting code depends on these parts of base, so they
need to be enabled.
2. Implemented NaCl version of rand_util.
3. Enabled glibc version of base_untrusted

BUG=134216

Review URL: https://chromiumcodereview.appspot.com/10795083

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

This is implemented by passing -MMD to gcc and then including the
generated .d files in the Makefile.

BUG=139161
TEST=
NOTRY=true

Review URL: https://chromiumcodereview.appspot.com/10821050

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

Remove the second comparison group from the prerender field trials, and reorganize the code so that we can compile assert on the summation. The second group has already shown us our numbers are good. The compile time assertion should avoid fat finger errors that we've caught in other reviews (which would otherwise have been a _beta crasher_!).

I think we should also give consideration to renaming these histograms for ease of understanding. I know that makes a historic comparison cost, but it makes arriving new in this area so much easier.

I'll rebase the multiple prerender CL on top of this.

R=dominich@chromium.org
BUG=None

TEST=


Review URL: https://chromiumcodereview.appspot.com/10802062

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

CID=104268,104216,104131,104058


Review URL: https://chromiumcodereview.appspot.com/10830022

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

Updates kSyncAutoStarts in defaults.cc to match the android version as well.

BUG=138245
TEST=

Review URL: https://chromiumcodereview.appspot.com/10796054

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

Include the LongPressDetectorTest as part of the
ContentShellTests.apk.

Produce a jar (ContentShellTests-debug.jar) so that
run_instrumentation_tests.py can use Proguard to enumerate the tests
by annotation.

BUG=136687
TEST=LongPressDetectorTest


Review URL: https://chromiumcodereview.appspot.com/10818039

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

This is based on https://chromiumcodereview.appspot.com/10790041/, not yet submitted.

BUG=137764
TEST=self

Review URL: https://chromiumcodereview.appspot.com/10803029

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

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

This is to pick up recent fixes to license metadata.

third_party/aosp: r122156 to r148330
- r122930 - Add svn:ignore to aosp
- r148330 - Fix licensing metadata for third_party/aosp

third_party/webgl_conformance: r138171 to r148561
- r148561 - Fix license metadata for ffmpeg and WebGL conformance tests

BUG=138921

Review URL: https://chromiumcodereview.appspot.com/10827044

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

r=scottmg
BUG=139084
Review URL: https://chromiumcodereview.appspot.com/10833030

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

BUG=137764
TEST=self

Review URL: https://chromiumcodereview.appspot.com/10790041

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

Some long lived browsers (and more likely, run-away and hyperactive
tasks) can run more times than can be tallied in a mere int (2^31
times). We use the count as a modulus to take a uniform sample of
other profiled activities.  If the task runs enough times, this value
turns negative, and eventually becomes zero, which would cause an
arithmetic exception (divide by zero when doing modulo operation).  We
now clamp the value at 2^31 - 1, which will make clear what has
happened when users visit about:profiler (a task has run a LOT), and
we then use this clamped value (instead of the real count) to be very
infrequent about taking a replacement sample.  This sampling should be
"good enough for government work," and should not impact enough folks
to have any effect on our profiling stats.

r=isherman
BUG=138961
Review URL: https://chromiumcodereview.appspot.com/10826018

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

The default LibjingleTransportFactory is used for tests only. We didn't
disable TCP ports even though we do disable them in host and client.


Review URL: https://chromiumcodereview.appspot.com/10824049

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

Fixing some more instances where I put in HistoryServiceFactory::GetForProfile which will force creation of the history. Replacing those instantces where we should not force creation and should instead just check if the history has already been created.

BUG=97804
TEST=unittests

Review URL: https://chromiumcodereview.appspot.com/10605003

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

Disable GPU process prelaunching in content_browsertests on Linux. This is causing lots of crashes inside base::LaunchProcess.

BUG=139209,90448
TBR=zmo
Review URL: https://chromiumcodereview.appspot.com/10827053

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

Windows 8 has both a classic "Desktop" mode and a new "Metro" mode, that
must use different browser processes because Chrome profile data stores
can only be accessed from one profile at a time, and it is not
technically feasible to allow multi process access today.

The short term solution to making the experience less jarring on Windows
8 is to cache the sync credentials in a separate file when the user
signs in on either Metro or Desktop, so that they can be used to
auto-start sync on the alternate profile (Desktop or Metro) when it is
opened.

This patch contains the following changes:

- A new class CredentialCacheService, that contains code capable of
  encrypting and persisting the google username, the lsid and sid,
  the encryption bootstrap token, and a list of enabled / disabled sync
  datatypes to a json encoded "Sync Credentials" file in the profile
  directory.
- Methods that listen to the PrefService and TokenService for changes
  to the above credentials and persist them when the user successfully
  signs in manually.
- Code in ProfileSyncService that detects that we are running on Windows
  8, and if sync has never been set up, tries to load cached credentials
  from the alternate Metro / Desktop profile, and if they were found,
  bootstrap sync using the credentials.
- Mechanisms to detect that we are using the "Default" profile on Metro
  or Desktop. As of today, Metro Chrome on Windows 8 does not support
  multiple profiles, and there is no good way to pair up a non-default
  profile directory ("Profile 1", "Profile 2", etc.) on Desktop to its
  corresponding directory on Metro and vice versa.
- Unit tests for functionality in credential_cache_service_win.{h|cc}.

BUG=139199,139200
TEST=Sign in to sync on Desktop, launch Metro, and watch sync automatically start up

Review URL: https://chromiumcodereview.appspot.com/10656033

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