| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
| |
BUG=none
TEST=none
Review URL: http://codereview.chromium.org/5626002
TBR=jhawkins@chromium.org
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@68531 0039d316-1c4b-4281-b951-d872f2087c98
|
| |
|
|
|
|
|
|
|
| |
BUG=none
TEST=none
Review URL: http://codereview.chromium.org/5626002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@68506 0039d316-1c4b-4281-b951-d872f2087c98
|
| |
|
|
|
|
|
|
|
| |
Hopefully this will help to address some valgrind issues.
BUG=none
TEST=none
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@26596 0039d316-1c4b-4281-b951-d872f2087c98
|
| |
|
|
|
|
| |
Review URL: http://codereview.chromium.org/8768
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@4283 0039d316-1c4b-4281-b951-d872f2087c98
|
| |
|
|
|
|
|
|
| |
through the pager, then deallocates the memory. It was previous just using malloc() and free(). This means it goes through heap allocate, which decides that large allocations (larger than ~500k) should get their own memory, and it calls VirtualAlloc(). However, it does this while holding the heap lock, meaning all other threads block their heap operations until the memory is allocated. Instead, since we know these allocations are likely to be large, just get raw pages from the OS directly.
Review URL: http://codereview.chromium.org/8935
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@4282 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
since it will be shared with WebCore and Gears in the
future.
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@1586 0039d316-1c4b-4281-b951-d872f2087c98
|
