GitLab

version_extension_ in MetricsLogBase was only used in the MetricsLog
subclass, so move it to there.

BUG=101600,94925
TEST=none


Review URL: http://codereview.chromium.org/8468018

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

BUG=104314
TEST=no change

Review URL: http://codereview.chromium.org/8520018

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

than needed.

BUG=none
TEST=none
Review URL: http://codereview.chromium.org/8540027

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

This will mean that when things like cancel are done on downloads resulting
from a Save Page As ..., chrome will not crash.  They also won't do anything,
but that's the previous (broken :-{) behavior.

BUG=103590
R=cbentzel@chromium.org


Review URL: http://codereview.chromium.org/8519008

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

Null time values can appear if the profiler is
not ACTIVE, and the Now() function returns a Null
value (to avoid wasting time and calling the OS Time).

r=rtenneti
Review URL: http://codereview.chromium.org/8573017

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

BUG=None
TEST=Manual

Review URL: http://codereview.chromium.org/8568023

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

BUG=104031


Review URL: http://codereview.chromium.org/8533015

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

Fix a breakage to about:profiler from r110207. This change was actually part of my original codereview that was approved, but I lost it while synching my svn client :(

TBR=jar@chromium.org
Review URL: http://codereview.chromium.org/8520029

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

Don't pollute the namespace with defines from C header files and forward
declare WaylandEvent.

BUG=102903
TEST=compiles

Change-Id: I5cd50c04361d4d053bdf8c193071a4c7808c51d7

R=oshima@chromium.org,dnicoara@chromium.org,mark@chromium.org


Review URL: http://codereview.chromium.org/8572030

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

BUG=104314
TEST=


Review URL: http://codereview.chromium.org/8468021

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

Also get rid of flushed_metahandles since it serves exactly zero purpose :)

BUG=87122
TEST=none

Review URL: http://codereview.chromium.org/8565035

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

Complete the rename from about:tracking2 --> about:profiler by changing the implementation code to always reference "profiler" rather than "tracking".

BUG=100992
Review URL: http://codereview.chromium.org/8520016

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

Also removes copy/pasted instances of this class.

BUG=none
TEST=none

R=willchan@chromium.org

Review URL: http://codereview.chromium.org/8565024

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

BUG=101996
TEST=NA
TBR=dimich@chromium.org


Review URL: http://codereview.chromium.org/8568018

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

BUG=none
TEST=PPAPI tests still pass (perhaps even less flakily)


Review URL: http://codereview.chromium.org/8468017

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

BUG=101774
TEST=NONE


Review URL: http://codereview.chromium.org/8527015

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

Added Media.URLScheme histogram.

BUG=none
TEST=manual observation of chrome://histograms/Media


Review URL: http://codereview.chromium.org/8468011

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

BUG=none
TEST=FindInPageControllerTest.FindMovesWhenObscuring on windows, linux_chromeos and aura bots.

Review URL: http://codereview.chromium.org/8573012

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

The window gets removed in RemovedFromWidget, so it is not necessary to do
this again in NativeViewDetaching. This fixes a couple of failing DOMViewTest
tests.

BUG=103487
TEST=DOMViewTest.TestRemoveAndDelete, TestReparent (browser_tests)

Review URL: http://codereview.chromium.org/8574016

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

After improving v8 API to allow us to pass in an extension source string
length field, use that to refer directly to the in-image source rather
than copying it and holding it in memory, thus saving memory.

It bums me out that I have to call GetRawDataResource() twice, but I don't s
a way around that without abandoning inheritance from v8::Extension and
switching to composition/delegation.

Moved DEPS for v8 to r9534, the newest to include r9365. I don't know whethe
this matches our convention; perhaps we always move DEPS to the latest.

BUG=95147
TEST=relying on existing extensions unit tests, which all still pass.


Review URL: http://codereview.chromium.org/8277020

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

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

Fix to v8-i18n was submitted in http://codereview.chromium.org/8570009

BUG=104011
TEST=Load crash1.html from bug report and check it doesn't crash browser. 
Review URL: http://codereview.chromium.org/8573014

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

Review URL: http://codereview.chromium.org/8520021

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

TEST=unit_tests --gtest_filter=BookmarkBarGtkUnittest*
R=sky@chromium.org


Review URL: http://codereview.chromium.org/8568011

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

BUG=none
TEST=none
Review URL: http://codereview.chromium.org/8463031

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

BUG=none
TEST=none

Original review: http://codereview.chromium.org/8136027/
Review URL: http://codereview.chromium.org/8520011

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

BUG=none
TEST=none

R=csilv@chromium.org

Review URL: http://codereview.chromium.org/8554001

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

No longer using libcros to call the method.  Part of libcros removal.
Instead chrome will call the method directly.

BUG=chromium-os:16558
TEST=none
Signed-off-by: Simon Que <sque@chromium.org>

R=satorux@chromium.org,stevenjb@chromium.org,tbarzic@chromium.org


Review URL: http://codereview.chromium.org/8566024

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

BUG=103999
TEST=see bug
Review URL: http://codereview.chromium.org/8570015

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

BUG=
TEST=

Review URL: http://codereview.chromium.org/8510074

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

BUG=100276
R=thestig@chromium.org

Review URL: http://codereview.chromium.org/8551002

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

Linux directory detection is now done in the driver instead of in the frontend, so let the plugin test script invoke the driver instead of clang -cc1 (else it won't find <string> etc on linux).

Previous attempt at http://codereview.chromium.org/8538027/

BUG=104323
TEST=none
TBR=hans


Review URL: http://codereview.chromium.org/8572021

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

   
This failure path has not received a lot of testing until now.  Here are
the issues addressed by this patch:
    
- We usually check the return value of step() calls.  However, we do not
check the return value of prepare() calls, which are more likely to fail.
If they do fail, we will DCHECK() or go on to dereference an invalid
pointer in step().  This patch checks the return value of one particular
prepare statement, the one in CheckIntegrity().
    
- Disable DCHECKs on sqlite errors, DirectoryManager open failure,
and SyncManager initialization failure.  This will allow us to test these
error paths.
    
- Be careful in ShutdownOnSyncThread().  The directory will not be fully
intialized during shutdown if the database load failed.

- Add a ProfileSyncService unit test that simulates a load from an
unreadable database.  The harness had to be modified slightly to make
this possible.

- Remove a setup_for_test_mode_ flag in SyncManager::SyncInternal::Init.
I don't know what the original intent of this flag was.  However, I do
know that it prevents me from properly simulating a database load failure
and removing it seems to have no ill effects.

- Do not delete the database from DirectoryBackingStore.  If this code
were to get executed it would put us into an inconsistent state.  See
issue 103824.  However, it's unlikely this code would get executed.  If
the database were actually corrupt, we would DCHECK or de-reference an
invalid pointer on our way to this code because we don't check the
return value of the attempt to prepare an SQL statement in
DirectoryBackingStore::CheckIntegrity().
    
- Modify the DirectoryBackingStoreTest.Corruption unit test to expect the
new behaviour.

- Disable sync when backend initialize fails.  Such a failure could
be due to bad local state.  We don't know the actual cause because the
information is not available from the ProfileSyncService callback.  The
safe course of action is to clear our local sync state and try again
later.  It's the easiest way to get back to the most well travelled sync
initialization path.

BUG=103307, 103824
TEST=DirectoryBackingStoreTest.Corruption, ProfileSyncServiceTest.CorruptDatabase

Review URL: http://codereview.chromium.org/8496002

TBR=rlarocque@chromium.org
Review URL: http://codereview.chromium.org/8570016

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

r=rvargas
bug=102940
Review URL: http://codereview.chromium.org/8487004

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

Initialization of the profiler is supposed to happen while
single threaded.  The tests however often skip affirmative
initialization, and rely on lazy initialization.  This
CL tightens up that process, to reduce changes of races
(even benign races) during testing.

I also added a suppression for examination of the state,
which is always a benign race.  At initialization time
we rely on a lock (now) to ensure race freedom (if we
get a racy value of state).

r=rtenneti
Review URL: http://codereview.chromium.org/8570007

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

This solves the problem when chrome.windows.create() is used to create a panel with a tabid. Panel was watching for NOTIFICATION_TAB_ADDED, which is only sent upon browser navigation. As there is no navigation when existing tab contents are used, the Panel does not set up auto-resize in this scenario.

BUG=None
TEST=PanelBrowserTest.CreateWithExistingContents

Review URL: http://codereview.chromium.org/8539025

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

BUG=none
TEST=compiles

Review URL: http://codereview.chromium.org/8571015

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

   
This failure path has not received a lot of testing until now.  Here are
the issues addressed by this patch:
    
- We usually check the return value of step() calls.  However, we do not
check the return value of prepare() calls, which are more likely to fail.
If they do fail, we will DCHECK() or go on to dereference an invalid
pointer in step().  This patch checks the return value of one particular
prepare statement, the one in CheckIntegrity().
    
- Disable DCHECKs on sqlite errors, DirectoryManager open failure,
and SyncManager initialization failure.  This will allow us to test these
error paths.
    
- Be careful in ShutdownOnSyncThread().  The directory will not be fully
intialized during shutdown if the database load failed.

- Add a ProfileSyncService unit test that simulates a load from an
unreadable database.  The harness had to be modified slightly to make
this possible.

- Remove a setup_for_test_mode_ flag in SyncManager::SyncInternal::Init.
I don't know what the original intent of this flag was.  However, I do
know that it prevents me from properly simulating a database load failure
and removing it seems to have no ill effects.

- Do not delete the database from DirectoryBackingStore.  If this code
were to get executed it would put us into an inconsistent state.  See
issue 103824.  However, it's unlikely this code would get executed.  If
the database were actually corrupt, we would DCHECK or de-reference an
invalid pointer on our way to this code because we don't check the
return value of the attempt to prepare an SQL statement in
DirectoryBackingStore::CheckIntegrity().
    
- Modify the DirectoryBackingStoreTest.Corruption unit test to expect the
new behaviour.

- Disable sync when backend initialize fails.  Such a failure could
be due to bad local state.  We don't know the actual cause because the
information is not available from the ProfileSyncService callback.  The
safe course of action is to clear our local sync state and try again
later.  It's the easiest way to get back to the most well travelled sync
initialization path.

BUG=103307, 103824
TEST=DirectoryBackingStoreTest.Corruption, ProfileSyncServiceTest.CorruptDatabase

Review URL: http://codereview.chromium.org/8496002

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

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

Review URL: http://codereview.chromium.org/8570013

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

BUG=none
TEST=none


Review URL: http://codereview.chromium.org/8523008

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