| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Trace events collected from suid sandbox'd threads need to report
their real pid and not the sandbox'd pid so data can be correlated
with system event data.
BUG=chromium-os:27809
TEST=check sandbox'd trace data against the output of ps
Change-Id: Ia8c7725ac6e4f18a2114de027a5d19ba15f49e60
Review URL: http://codereview.chromium.org/10165015
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133619 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
1) Don't pass the path as the site. We don't support site-specific clearing,
so just pass an empty string.
2) Append the plugin's name to the profile-specific Pepper data directory.
Review URL: http://codereview.chromium.org/10202002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133616 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
messages aren't called yet by the renderer-side.
Review URL: https://chromiumcodereview.appspot.com/10160003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133576 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
the TabContentsViewAura renaming.
BUG=118024
TEST=none
Review URL: http://codereview.chromium.org/10174009
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133559 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=none
TEST=none
Review URL: http://codereview.chromium.org/10115017
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133520 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is purely removing code that is no longer called, since
https://bugs.webkit.org/show_bug.cgi?id=83638 has been fixed.
BUG=124650
Review URL: http://codereview.chromium.org/10179003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133517 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
To introduce a real KeyPath type, the return type of keyPath accessors
needs to change from a String to an IDBKeyPath. To do this requires
temporarily moving the methods aside. The WebKit API change (which must
land first) is at: https://bugs.webkit.org/show_bug.cgi?id=84208
R=darin@chromium.org,dgrogan@chromium.org
BUG=112308
Review URL: http://codereview.chromium.org/10041014
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133500 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
BUG=NONE
TEST=NONE
Review URL: https://chromiumcodereview.appspot.com/10166001
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133465 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
disabled tests and got rid of flaky patterns. Hopefully they don't fail again.
BUG=121574
Review URL: https://chromiumcodereview.appspot.com/10144015
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133458 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
be handled by web intents.
BUG=105732
TEST=None
Review URL: http://codereview.chromium.org/10079012
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133456 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
TEST=none
BUG=none
Review URL: http://codereview.chromium.org/10155002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133364 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
sometimes we missed the notification that an alert was shown because it came before we started watching for it. The fix is to navigate asynchronously.
BUG=46257
Review URL: https://chromiumcodereview.appspot.com/10162024
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133360 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ASSERT_EQ(false, ...) -> ASSERT_FALSE(...)
BUG=none
TEST=it compiles
TBR=jam@chromium.org
R=thestig@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10144014
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133324 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
Includes unit test for timer functionality.
BUG=123998
Review URL: http://codereview.chromium.org/10119027
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133317 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
| |
BUG=121574, 56264, 62776, 80596, 100823
Review URL: https://chromiumcodereview.appspot.com/10144012
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133307 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=
TEST=
Review URL: https://chromiumcodereview.appspot.com/10170010
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133279 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
until it's more baked.
BUG=122884
TEST=none
Review URL: https://chromiumcodereview.appspot.com/10165008
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133273 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
TEST=none
BUG=none
Review URL: https://chromiumcodereview.appspot.com/10130001
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133236 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
| |
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133217 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
| |
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133216 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
transferring an HTTP body.
This should not change behavior at all, but will let us see how commonly these situations happen in the wild.
BUG=52847
TEST=Existing tests.
Review URL: http://codereview.chromium.org/9950023
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133208 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
ui_test to browser_tests. I renabled the tests, hopefully they're not flaky anymore with the rewrite.
NPObjectReleasedOnDestruction and SelfDeletePluginInvokeAlert weren't testing anything because they broke after the WebKit test plugin changed, so I fixed them.
BUG=121574, 30702, 60071, 46257
Review URL: https://chromiumcodereview.appspot.com/10145001
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133204 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This CL removes requesting_frame parameters from the Geolocation
stack because the URL passed around in these is no longer used for
anything.
BUG=123815
TEST=unit_tests, browser_tests *Geolocation*
Review URL: http://codereview.chromium.org/10107017
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133183 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: https://chromiumcodereview.appspot.com/9950040
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133107 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
into WebContentsObserver, and implement them in PluginObserver and HungPluginTabHelper.
This removes some code from Browser that only forwarded to other helpers.
BUG=none
TEST=none
Review URL: http://codereview.chromium.org/10117025
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133099 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These limits are probably still a useful sanity check for integer overflows,
but 4Kx4K is hitting people with large monitor setups. Also, shmmax is
typically 256MB these days.
BUG=70692
TEST=I don't have that kind of monitor setup I'm afraid.
Review URL: http://codereview.chromium.org/9958075
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133086 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
When the page navigates (or reloads) and a RenderView is reused, in-flight WebUISend messages may still be handled rather than being cancelled. This results in a WebUI receiving unexpected messages (e.g. before initialization has had a chance to take place). This patch makes sure in-flight messages are ignored (in-flight messages will come in before the new document element is ready, thus they will be ignored). I've verified that chrome.send executed before load events are dispatched still works (adding a browsertest for that is a TODO).
BUG=121741
TEST=mashing reload and clicking on an entry in the search engine manager does not cause a crash
Review URL: https://chromiumcodereview.appspot.com/9968123
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133077 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- make OpenStorageArea async
- use GURL to represent origins instead of strings
- consistently use 'connection_id'
- send DomStorage event messages to the originating renderer too
(these are dropped on the floor on that side pending additional
webkit/webcore changes)
- include the src connection_id for DomStorage event message that
originated in the destination renderer
Review URL: https://chromiumcodereview.appspot.com/10116007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133051 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
R=apatrick@chromium.org
CC=davemoore@chromium.org
Review URL: http://codereview.chromium.org/10116036
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133035 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Resource deletion doesn't force a flush, so for textures that are deleted on a
little-used shared context, the delete command may sit in the command buffer for
arbitrary long.
This fixes it.
BUG=123933
TEST=chrome/aura, open many tabs, close all of them, check that GPU memory is reclaimed.
Review URL: http://codereview.chromium.org/10078002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133017 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
so that we don't need to worry about it in unittests.
BUG=110886
TEST=Run DownloadFileTest.* over an NX connection.
R=benjhayden@chromium.org
Review URL: http://codereview.chromium.org/10116027
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132998 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
Renamed caller_id -> session_id in speech recognition classes. This is a partial refactoring in preparation for next CLs.
BUG=116954
TEST=none.
Review URL: http://codereview.chromium.org/9972008
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132979 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If we are using blocking write, when the renderer stop getting the data without notifying the browser, it will hang the browser. This happens with some plugins which use the sync sockets provided by the Pepper.
This patch change CancellableSyncSocket to be non-blocking on sending, so that we don't need to worry the whole browser hangs by one plugin application.
Also, we remove the lock in audio_sync_reader.cc since it is not really needed if we don't set the socket_ to NULL when calling Close(). By doing this we allow the user to close the socket while another thread is writing to the socket.
BUG=121152
TEST=ipc_tests
TBR=tommi@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10124004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132975 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=123418
TEST=
Review URL: http://codereview.chromium.org/10116014
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132940 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=none
TEST=manually on Mac.
TBR=tony@chromium.org, avi@chromium.org
Review URL: http://codereview.chromium.org/10069003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132928 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is the Chromium IPC plumbing to talk to the WebKit API.
This won't be used until https://bugs.webkit.org/show_bug.cgi?id=83638
is fixed.
BUG=92047
Review URL: http://codereview.chromium.org/10083053
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132918 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: https://chromiumcodereview.appspot.com/10115048
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132907 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=118410
TEST=no change
Review URL: http://codereview.chromium.org/10035040
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132898 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=none
TEST=tested with flag enabled and disabled
Review URL: http://codereview.chromium.org/9433046
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132896 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
getting the data without notifying the browser, it will hang the browser. This happens with some plugins which use the sync sockets provided by the Pepper.
This patch change CancellableSyncSocket to be non-blocking on sending, so that we don't need to worry the whole browser hangs by one plugin application.
Also, we remove the lock in audio_sync_reader.cc since it is not really needed if we don't set the socket_ to NULL when calling Close(). By doing this we allow the user to close the socket while another thread is writing to the socket.
BUG=121152
TEST=ipc_tests
Review URL: http://codereview.chromium.org/10000004
TBR=xians@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10083064
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132888 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=104346
TEST=None
Review URL: https://chromiumcodereview.appspot.com/10021058
Patch from Nasko Oskov <nasko@chromium.org>.
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132852 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
without notifying the browser, it will hang the browser. This happens with some plugins which use the sync sockets provided by the Pepper.
This patch change CancellableSyncSocket to be non-blocking on sending, so that we don't need to worry the whole browser hangs by one plugin application.
Also, we remove the lock in audio_sync_reader.cc since it is not really needed if we don't set the socket_ to NULL when calling Close(). By doing this we allow the user to close the socket while another thread is writing to the socket.
BUG=121152
TEST=ipc_tests
Review URL: http://codereview.chromium.org/10000004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132842 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
move it to chrome\renderer and all of its associated switches to chrome. GC extension is only used by webkit\support, so move it there. The other two profiler extensions aren't used, so remove them.
Review URL: https://chromiumcodereview.appspot.com/10117022
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132841 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=114677
TEST=Run with --enable-viewport --aura-host-window-size=XxY*2 and verify that a scale factor of 2 is used.
Review URL: http://codereview.chromium.org/10091016
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132834 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: https://chromiumcodereview.appspot.com/10075001
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132808 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
This is a follow up to r128782.
R=jam@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9956177
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132790 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=123682
TEST=see bug report for manual test
R=kbr
Review URL: http://codereview.chromium.org/10117009
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132714 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
I spent a lot of time trying to find a way to make the assertion and crash dump locator tests non-flaky and shardable. But it's not really possible, because the log file is per binary, and the dumps all get put into the same directory. That means that running with sharding will give erronous results. Also even if we weren't sharding, there's still race conditions looking at the disk for a crash dump. I kept a test which looks for a notification that we crashed (instead of looking on disk). If this breaks in the field, I believe we'll notice very quickly from the canary builds (do we also have breakpad tests for this?). For the assert/check tests, I think if something breaks there developers will very quickly find it.
BUG=121574
Review URL: https://chromiumcodereview.appspot.com/10082001
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132684 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We unconditionally granted the read access to the renderer when dragging in
files. Unfortunately, this breaks things like the File Manager which actually
have write access to certain parts of the filesystem. In order to prevent file
dragging from downgrading child permissions, we first check if the renderer
can already read the file before setting read permissions for it.
BUG=chromium-os:28809
TEST=manual
Review URL: http://codereview.chromium.org/10086020
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132672 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=none
TEST=none
Review URL: http://codereview.chromium.org/10091045
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132667 0039d316-1c4b-4281-b951-d872f2087c98
|