| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the attempt
to create a memory mapped section with the size of the file fails with the section too large
error. As per msdn documentation we can safely pass in 0 for the file size for CreateFileMapping
and MapViewOfFile which indicates that the whole file is being mapped.
This caused some plugin dlls like acrobat reader 9 to not load in chrome.
Fixes bug http://code.google.com/p/chromium/issues/detail?id=75351
BUG=75351
TEST=manually as described in the bug.
Review URL: http://codereview.chromium.org/6661010
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@77575 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
I introduced this in 2008, thinking it'd be a temporary thing.
It has taken a very long time to undo the damage, but it's done
now.
BUG=69467
Review URL: http://codereview.chromium.org/6659018
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@77565 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=none
TEST=On xubuntu lucid, actually detect that we're running xfce.
Review URL: http://codereview.chromium.org/6612056
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@77561 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
| |
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@77531 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
BUG=none
TEST=none
Review URL: http://codereview.chromium.org/6656007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@77530 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
BUG=56596
TEST=none
Review URL: http://codereview.chromium.org/6611007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@77387 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
Also remove mention of about:tasks in release build,
where we don't generate any data for that about page.
R=eroman
Review URL: http://codereview.chromium.org/6626064
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@77323 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[This is a re-landing of CL 6623059, which broke the
shared library build on windows in revision 77207.
An ifdef has been added to avoid the unresolved variable
when allocator_shim.cc is never even compiled]
Continue to support selection of a browser allocator
selection via the environment variable CHROME_ALLOCATOR,
and also add CHROME_ALLOCATOR_2 that can select the
allocator to use in subprocesses, such as a renderer.
Temporarilly set the browser default to the
default windows heap allocator, and the subprocess
allocator to TCMalloc to help detect memory corruption
in a cannary for a few days.
This may illuminate some flakiness in the tree, as
double frees (hidden by races) may cause crashes.
Add minor cleanup (removing reserved word "override"
etc.).
BUG=74901
TBR=mbelshe
Review URL: http://codereview.chromium.org/6623072
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@77245 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Chrome sync is dependent on other areas of chrome, and patches committed to
these areas could potentially break sync. In the past, we have seen
sync integration test failures caused by patches to net, jingle and base.
This patch adds a PRESUBMIT.py file to each of these directories, that
will result the sync integration tests being run on any code that
touches these directories as part of their try runs.
BUG=70311
TEST=modify something under base, net or jingle and do a "git try" or "gcl try"
Review URL: http://codereview.chromium.org/6624086
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@77242 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
During a code review I noticed that RenderViewHost::FromID was being called from the IO thread, but there were no automated assertions that fired.
BUG=None
TEST=DCHECK fires when I add bad code. Otherwise Chrome works without crashing in Debug build.
Review URL: http://codereview.chromium.org/6591108
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@77232 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Continue to support selection of a browser allocator
selection via the environment variable CHROME_ALLOCATOR,
and also add CHROME_ALLOCATOR_2 that can select the
allocator to use in subprocesses, such as a renderer.
Temporarilly set the browser default to the
default windows heap allocator, and the subprocess
allocator to TCMalloc to help detect memory corruption
in a cannary for a few days.
Add minor cleanup (removing reserved word "override"
etc.).
r=mbelshe
bug=74901
Review URL: http://codereview.chromium.org/6623059
TBR=jar@chromium.org
Review URL: http://codereview.chromium.org/6623069
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@77208 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Continue to support selection of a browser allocator
selection via the environment variable CHROME_ALLOCATOR,
and also add CHROME_ALLOCATOR_2 that can select the
allocator to use in subprocesses, such as a renderer.
Temporarilly set the browser default to the
default windows heap allocator, and the subprocess
allocator to TCMalloc to help detect memory corruption
in a cannary for a few days.
Add minor cleanup (removing reserved word "override"
etc.).
r=mbelshe
bug=74901
Review URL: http://codereview.chromium.org/6623059
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@77207 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a test, and will be reverted as soon as the
build starts. We just want to see what the perf
bots have to say.
This CL changes the default allocator to be the
Windows Allocator (rather than TCMalloc), but then
overrides that default via the environment variable
control *during* the running of the browser_main.
The result is that the browser process will use the Windows
Allocator, but all sub-processes, such as renderers,
will use TCMalloc.
TBR=cpu
BUG=74901
Review URL: http://codereview.chromium.org/6624050
TBR=jar@chromium.org
Review URL: http://codereview.chromium.org/6627045
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@77116 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a test, and will be reverted as soon as the
build starts. We just want to see what the perf
bots have to say.
This CL changes the default allocator to be the
Windows Allocator (rather than TCMalloc), but then
overrides that default via the environment variable
control *during* the running of the browser_main.
The result is that the browser process will use the Windows
Allocator, but all sub-processes, such as renderers,
will use TCMalloc.
TBR=cpu
BUG=74901
Review URL: http://codereview.chromium.org/6624050
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@77111 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
BUG=None
TEST=None
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@77082 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I'll revert this as soon as the builds kick off.
I just want to look at perf impact.
I'll ceate a fancier CL that uses different allocators
for render vs browser, but I wanted an overall baseline
for transitioning completely from TCMalloc to
the default allocator on Windows.
TBR=cpu
Review URL: http://codereview.chromium.org/6635004
TBR=jar@chromium.org
Review URL: http://codereview.chromium.org/6623041
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@77067 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I'll revert this as soon as the builds kick off.
I just want to look at perf impact.
I'll ceate a fancier CL that uses different allocators
for render vs browser, but I wanted an overall baseline
for transitioning completely from TCMalloc to
the default allocator on Windows.
TBR=cpu
Review URL: http://codereview.chromium.org/6635004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@77066 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This code was reverted because it caused, or exposed
flakiness in sync unit test code (mostly on the Mac).
We need to monitor that closely as we re-land.
See the reviews and history in CLs:
http://codereview.chromium.org/6577013
and
http://codereview.chromium.org/6591052
This code generates CRC checksums for the histogram
bucket-range vectors, and guarantees they remain
intact when the histogram data is about to be
uploaded to UMA. If the data is corrupted, then
we will fail on a CHECK().
r=mbelshe,rvargas
bug=73939
Review URL: http://codereview.chromium.org/6627011
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@77033 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=carnitas
TEST=compiles
Review URL: http://codereview.chromium.org/6609008
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76962 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=none
TEST=none
TBR=brettw
Review URL: http://codereview.chromium.org/6624025
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76947 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
the user agent construction code.
Also cleans up a few nearby things.
BUG=none
TEST=none
Review URL: http://codereview.chromium.org/6632002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76945 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ignore 64 bit
plugins. We validate whether a plugin is a 32 bit dll by reading its PE image.
This fixes bug http://code.google.com/p/chromium/issues/detail?id=73032
Added support for the win32 version of the MemoryMappedFile helper class in base to map
a file as an image section.
BUG=73032
TEST=As described in the bug at this point.
Review URL: http://codereview.chromium.org/6611028
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76934 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
codebase call it.
BUG=none
TEST=none
Review URL: http://codereview.chromium.org/6610029
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76854 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
functionality is available in release builds if explicitly
requested by using their Impl types. The default usage remains
that they do nothing in release mode.
Also, update unit tests to run in release mode, verifying that the release versions of NonThreadSafe and ThreadChecker do nothing in release builds.
BUG=none
TEST=base unit tests
Review URL: http://codereview.chromium.org/6599004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76833 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=none
TEST=none
Review URL: http://codereview.chromium.org/6602047
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76800 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
Many of our tests want to use Unicode literal strings with the
L"foobar" syntax. Allow us to test FilePaths against these
strings.
BUG=69467
Review URL: http://codereview.chromium.org/6606025
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76763 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also adds streaming for CFStringRefs and CFErrorRefs making it
easier to add them to LOG() type statements.
BUG=NONE
TEST=BUILD
Review URL: http://codereview.chromium.org/6594096
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76714 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Reason for revert: This patch might have resulted in some
flakiness in the sync bots on the chromium waterfall.
The range vector is calculated once when a histogram is
constructed, and should never change over the lifetime of the
histogram. When it does change, it means that memory is being
overwritten. We now crash (via CHECK) when there is any
detected corruption of the range vector.
This CL uses a more robust check-sum algorithm to detect corruption
of the vector. The previous algorithm just did a sum, and was
too easilly tricked by small (offsetting) changes in several
ranges. Hopefully, this CRC-32 implementation will not be
so easilly fooled.
I had to refactor the class to ensure that each histogram was completely
constructed before I registered it. The old code could sometimes
register a base class (tradtional Histogram, with exponential
bucket spread) and then run the derived constructor (such as
when creating a LinearHistogram, with a second construction
of the ranges and checksum). I now carefully avoid
generating the checksum until fully constructing the instance,
and then I run InitializeBuckets only once on
the instance before registering it.
bug=73939,74467
r=mbelshe
Review URL: http://codereview.chromium.org/6577013
TBR=jar@chromium.org
Review URL: http://codereview.chromium.org/6611001
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76667 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Reason for revert: This patch might have resulted in some
flakiness in the sync bots on the chromium waterfall.
CL http://codereview.chromium.org/6577013/ had
a few changes suggested that were not incorporated.
This CL has those name changes etc.
r=rvargas
Review URL: http://codereview.chromium.org/6591052
BUG=74467
TBR=jar@chromium.org
Review URL: http://codereview.chromium.org/6591129
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76662 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove the signal handler when the message-pump terminates. This wouldn't
normally be necessary, but it can happen that the message-pump is terminated,
and then additional GTK+ operations happen (e.g. in unit_tests).
Also check for non-null dispatcher before dispatching events. This can happen
for the first-run dialog, and also in the unit_tests.
BUG=none
TEST=unit_tests
Review URL: http://codereview.chromium.org/6596094
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76643 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remoting's test client and simple host weren't initializing the NSApplication correctly which is required for MessageLoops to work on the Mac. These are just test apps that we use, so I felt it was ok to bring in code from base/test.
Also added a check to message_pump_mac.mm to verify that NSApp is initialized before we attempt to use it.
BUG=NONE
TEST=BUILD
Review URL: http://codereview.chromium.org/6461023
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76624 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
UMA_HISTOGRAM_ENUMERATION and specify 16000 as the bucket size. Bumped
up kBucketCount_MAX to 2**16.
BUG=74618
TEST=We need to test MemoryMappedFile on windows in the browser to send
histogram data for MemoryMappedFile.CreateFileMapping.
R=jar
Review URL: http://codereview.chromium.org/6592087
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76514 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=carnitas
TEST=compiles; existing unit tests.
Review URL: http://codereview.chromium.org/6602049
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76467 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
Setup XInput2 events only for the regular windows (and not for temporary ones). This was causing unit_tests to crash.
BUG=unit_tests crashes for touch
TEST=unit_tests
Review URL: http://codereview.chromium.org/6602050
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76461 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
suppress the TSan complaints. Enabled NonSearchToSearchDoesntSupportInstant
in intractive_ui_tests for Linux.
BUG=70810,61179
TEST=please test interactive_ui_tests.
Review URL: http://codereview.chromium.org/6546020
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76430 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
This is needed for cases where we need to work with known-ASCII filenames,
like locale paths.
Review URL: http://codereview.chromium.org/6597075
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76426 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=73195
TEST=none
Review URL: http://codereview.chromium.org/6588087
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76419 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
CL http://codereview.chromium.org/6577013/ had
a few changes suggested that were not incorporated.
This CL has those name changes etc.
r=rvargas
Review URL: http://codereview.chromium.org/6591052
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76345 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
Bug=58409
Review URL: http://codereview.chromium.org/6469070
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76343 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
The majority of these changes are purely moving code.
Conducted some minor (and hopefully straightforward) refactoring.
BUG=73195
TEST=none
Review URL: http://codereview.chromium.org/6596020
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76339 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
Avoid re-use of method name with different signature
when creating custom histograms
TBR=mbelshe
Review URL: http://codereview.chromium.org/6592043
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76244 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The range vector is calculated once when a histogram is
constructed, and should never change over the lifetime of the
histogram. When it does change, it means that memory is being
overwritten. We now crash (via CHECK) when there is any
detected corruption of the range vector.
This CL uses a more robust check-sum algorithm to detect corruption
of the vector. The previous algorithm just did a sum, and was
too easilly tricked by small (offsetting) changes in several
ranges. Hopefully, this CRC-32 implementation will not be
so easilly fooled.
I had to refactor the class to ensure that each histogram was completely
constructed before I registered it. The old code could sometimes
register a base class (tradtional Histogram, with exponential
bucket spread) and then run the derived constructor (such as
when creating a LinearHistogram, with a second construction
of the ranges and checksum). I now carefully avoid
generating the checksum until fully constructing the instance,
and then I run InitializeBuckets only once on
the instance before registering it.
bug=73939
r=mbelshe
Review URL: http://codereview.chromium.org/6577013
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76239 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Create FunctionTraits specializations that can unwrap function pointers that
are delcared with __fastcall and __stdcall on windows.
Only include these in the Windows build.
BUG=35223
TEST=new unittests
Review URL: http://codereview.chromium.org/6561004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76174 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
the class calculate its own command line. Wired up Linux autorun code and added unit tests.
BUG=None
TEST=Test service process autorun when enabling the cloud print proxy, unit-tests.
Review URL: http://codereview.chromium.org/6591002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76077 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
Associated review at: http://codereview.chromium.org/6489031/
BUG=none
TEST=none
Review URL: http://codereview.chromium.org/6532102
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76074 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Add a DCHECK
- Comment what the return value is on AddGroup
- const a member
- Typo fix
BUG=None
TEST=None
Review URL: http://codereview.chromium.org/6577038
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76061 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to adhere to the C++ Style Guide.
Landing for roubert@google.com, original review
http://codereview.chromium.org/6485028/
BUG=none
TEST=none
Review URL: http://codereview.chromium.org/6580049
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76017 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Skimming their changelogs, it looks like this range contains only minor tweaks for the most part.
gtest r500 is interesting:
http://code.google.com/p/googletest/source/detail?spec=svn500&r=500
"Modifies handling of C++ exceptions in death tests to treat exceptions escaping them as failures."
This confuses to death tests in message_loop_unittest on Windows, MessageLoopTest::Crasher and MessageLoopTest::CrasherNasty. These two tests set the global SEH handler. gtest now uses a frame-level exception handler, which overrides this global handler. Hence, disable gtest's new death test behavior for base_unittests on windows.
This is to prepare a gmock roll to 359, which should improve
build speed on mac.
BUG=none
TEST=none
Review URL: http://codereview.chromium.org/6580010
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@75972 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=carnitas
TEST=compiles
Review URL: http://codereview.chromium.org/6575020
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@75939 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=NONE
TEST=BUILD
Review URL: http://codereview.chromium.org/6482016
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@75893 0039d316-1c4b-4281-b951-d872f2087c98
|