GitLab

BUG=122670,139470
TEST=none
TBR=timurrrr
Review URL: https://chromiumcodereview.appspot.com/10831066

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

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

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

CryptohomeClient::IsMounted is converted to asynchronous and used instead.
Mock's default action for IsMounted is set in the ctor of MockCryptohomeClient.

BUG=126674
TEST=git try -b linux_chromeos


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

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

BUG=118571


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

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

BUG=123162
TBR=flackr

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

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

Add global tracking of GPU memory allocations.  Have each ContextGroup push memory tracking information to the GpuMemoryManager.  With this we can determine if we transiently oversubscribe.

BUG=135525
TEST=

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

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

BUG=130206
TEST=manual


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

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

Also re-factored the recently landed Debugger api (I believe it's the only API to have compiled events, so far)

BUG=138767


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

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

BUG=139467
TEST=none
TBR=dmazzoni
Review URL: https://chromiumcodereview.appspot.com/10823068

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

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

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

TBR=reed@google.com
Review URL: https://chromiumcodereview.appspot.com/10835026

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

BUG=
TEST=Manual, in browser


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

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

net log event.

https://src.chromium.org/viewvc/chrome?view=rev&revision=148115 is 
the original CL that had the logging.


BUG=133995
R=willchan
TEST=network unit tests

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

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

Continuation of http://codereview.chromium.org/10692178/

If a browser is running, and the service process is running the connector, the
connector will occasionally start up a chromium process to check the connector
enablement policy. The flag to do so would get passed to a running browser, if
present, and there is a path through the policy check code that could cause the
browser to quit.

This patch prevents the policy check flag from being passed on; the started
process will be very short lived and does a silent launch.

Original Review URL: https://chromiumcodereview.appspot.com/10666010
Second Review URL: http://codereview.chromium.org/10692178/

BUG=134252
TEST=None


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

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

Follow-up CLs will make the host respect this policy, and will let Windows
and Mac builds read this string-valued policy.

BUG=132684


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

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

2732 tests pass with these suppressions.

BUG=138115

TEST=


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

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

BUG=123851
TEST=none
TBR=bauerb
Review URL: https://chromiumcodereview.appspot.com/10831065

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

This was formerly a hand-rolled C++ class, but Satoru
pointed out that using protocol buffers would make
serialization to disk much simpler.

BUG=128805
TEST=compiles
TBR=ben@chromium.org

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

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

BUG=126514


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

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

If there is an error bubble on the login screen, and the user clicks
on the status-tray, then the bubble should close. Instead of sending
complicated messages from the UI to the login webui code, it is much
simpler to just close the bubbles when the login window loses focus.

BUG=127092
TEST=manually

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

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

Fix a SPDY crash bug where a CHECK() is hit because a cancelled stream is considered active by the spdy session.

BUG=139375
TEST=SpdySessionSpdy2Test.CancelStream


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

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

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

When the token service is initialized, tokens are read from disk via LoadTokensFromDB. The callback for this function after the DB read completes is LoadTokensIntoMemory.

When LoadTokensIntoMemory is run, it calls UpdateCredentials, which implicitly rewrites the just-read credentials back to the DB. This DB write is unnecessary. An unintended side effect is that the credential caching service does an unnecessary file-write to "Sync Credentials" every single time Chrome is restarted, even though the sync credentials haven't changed in any way.

This patch modifies LoadTokensIntoMemory to merely update |credentials_|, the in-memory credentials object, without updating the DB too.

BUG=139263
TEST=unit_tests; Sign in to sync, restart chrome, and make sure TokenService credentials are not re-written to DB during initialization.


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

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

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

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

This add gesture related functionality to the java side to ContentViewCore and also
adds some missing calls on the routing path of the gesture events to webkit. The WebKit side
for related parts of the WebCompositorInputHandler has already been upstreamed.

BUG=136680
TEST=

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

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

BUG=134372,123162
TEST=none
TBR=flackr

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

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

cc1plus: warnings being treated as errors
./chrome/browser/extensions/api/api_resource_manager.h: In member function 'void extensions::TestExtensionSystem::CreateSocketManager()':
./chrome/browser/extensions/api/api_resource_manager.h:28:error: 'id' is used uninitialized in this function
chrome/browser/extensions/test_extension_system.cc:55: note: 'id' was declared here



/b/build/slave/cr-mac-rel/build/src/chrome/browser/extensions/test_extension_system.cc:56:3:error: variable 'id' is used uninitialized whenever '&&' condition is false [-Werror,-Wsometimes-uninitialized]
  DCHECK(BrowserThread::GetCurrentThreadIdentifier(&id));
  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../base/logging.h:706:35: note: expanded from macro 'DCHECK'
  LAZY_STREAM(LOG_STREAM(DCHECK), DCHECK_IS_ON() && !(condition))   \
                                  ^
../base/logging.h:670:3: note: expanded from macro 'DCHECK_IS_ON'
  ((::logging::g_dcheck_state ==                                        \
  ^
../base/logging.h:362:5: note: expanded from macro 'LAZY_STREAM'
  !(condition) ? (void) 0 : ::logging::LogMessageVoidify() & (stream)
    ^~~~~~~~~
/b/build/slave/cr-mac-rel/build/src/chrome/browser/extensions/test_extension_system.cc:57:56: note: uninitialized use occurs here
  socket_manager_.reset(new ApiResourceManager<Socket>(id));
                                                       ^~
/b/build/slave/cr-mac-rel/build/src/chrome/browser/extensions/test_extension_system.cc:56:3: note: remove the '&&' if its condition is always true
  DCHECK(BrowserThread::GetCurrentThreadIdentifier(&id));
  ^
../base/logging.h:706:35: note: expanded from macro 'DCHECK'
  LAZY_STREAM(LOG_STREAM(DCHECK), DCHECK_IS_ON() && !(condition))   \
                                  ^
../base/logging.h:670:3: note: expanded from macro 'DCHECK_IS_ON'
  ((::logging::g_dcheck_state ==                                        \
  ^
../base/logging.h:362:5: note: expanded from macro 'LAZY_STREAM'
  !(condition) ? (void) 0 : ::logging::LogMessageVoidify() & (stream)
    ^
/b/build/slave/cr-mac-rel/build/src/chrome/browser/extensions/test_extension_system.cc:55:3: note: variable 'id' is declared here
  BrowserThread::ID id;
  ^
1 error generated.


- Improve unit testing of socket API.

Add socket_api_unittest.cc, which calls Socket API functions directly.
This skips the whole browser_tests setup that is relatively slow and
expensive. The current test merely validates the socket-type argument
handling, but the next phase will simulate blocking socket operations.

BUG=112902
TEST=see above


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

TBR=miket@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10830061

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

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

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

Add socket_api_unittest.cc, which calls Socket API functions directly.
This skips the whole browser_tests setup that is relatively slow and
expensive. The current test merely validates the socket-type argument
handling, but the next phase will simulate blocking socket operations.

BUG=112902
TEST=see above


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

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

BUG=139088
TEST=Linux CrOS build.

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

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

This is the default value. It can be overridden with GYP_DEFINES. It is with
the swarm master.
Also remove the corresponding XXX_run targets. These can be problematic when
developers are moving files around, especially with DEPS rolls.
This simplifies build slave management during the deployment as the .isolate
files are being rolled out.

TBR=cmp@chromium.org
NOTRY=true
BUG=139426

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

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

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

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

Move the render process host tests in content to chrome. These test chrome specific behavior with things like extensions/webui/singleton tabs.

BUG=90448
Review URL: https://chromiumcodereview.appspot.com/10820056

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

Also removes a no-longer necessary -respondsToSelect: check since we no longer support 10.5.

BUG=20053
TEST=Right click on a BMB folder and click edit. Buttons should be "Cancel" and "Save".
Right click on BMB and select "Add Folder...". Buttons should be "Cancel" and "Add".

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

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

Do not individual files that are needed since the list of needed files for
new-run-webkit-websocketserver is too often changing.

Contrary to the previous .isolate CLs, this one was done manually. A rule in isolate_common.py will be added in a follow up change.

TBR=dpranke@chromium.org
NOTRY=true
BUG=139426


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

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

own pp_file_handle{.h,idl}.

BUG= none
TEST= trybots

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

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

-Put nodoc on experimental.apps.{notify,clearAllNotifications} since those
aren't available in new packaged apps and we'll probably be doing some changes
to them before we'd move them to supported anyway.

-Remove nodoc from experimental.apps.onLaunched

BUG=138754
TEST=none

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

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

BUG=138115

TEST=


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

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