summaryrefslogtreecommitdiffstats
path: root/chrome/browser/browser_process.h
Commit message (Collapse)AuthorAgeFilesLines
* Hide MHTMLGenerationManager from chrome.jam@chromium.org2012-03-011-3/+0
| | | | | | | BUG=98716 Review URL: https://chromiumcodereview.appspot.com/9566001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@124430 0039d316-1c4b-4281-b951-d872f2087c98
* Remove GetAudioManager and GetMediaStreamManager from ResourceContext. The ↵jam@chromium.org2012-02-231-3/+0
| | | | | | | | | | | reason is the content module should create all the concrete objects that it knows about, instead of depending on every embedder to do so. ResourceContext is then just the interfaces that it implements and which it provides on the IO thread. The AudioManager getter was a global, so I added a getter to the AudioManager class. MediaStreamManager now has its own static getter like other internal content classes on ResourceContext or BrowserContext. BUG=98716 Review URL: https://chromiumcodereview.appspot.com/9433006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@123264 0039d316-1c4b-4281-b951-d872f2087c98
* Introduced the PolicyService.joaodasilva@chromium.org2012-02-091-0/+6
| | | | | | | | | | | | | | | | The PolicyService is owned by the BrowserPolicyConnector, and isn't yet used anywhere. The next step is to make the ConfigurationPolicyPrefStores get their policies from the PolicyService instead of the providers directly. The providers then can also be modified to provide both mandatory and recommended policies, and 3rd party policies. BUG=108999 TEST=All works as before; unit_tests green Review URL: http://codereview.chromium.org/9325066 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@121249 0039d316-1c4b-4281-b951-d872f2087c98
* Move creation and ownership of ResourceDispatcherHost and PluginService to ↵jam@chromium.org2012-01-111-2/+3
| | | | | | | | | | | | | | | | content. This gives a few benefits: -avoid having each embedder know when to create/destruct these objects, as well as contained objects (i.e. those related to downloads) -avoid having to tell embedders about specifics of BrowserThread startup/shutdown -move ResourceDispatcherHost's getter to content where it belongs I've taken out the DnsParallelism field trial (not used anymore, confirmed with jar) as it was the only thing that caused MetricsService to depend on IOThread initialization, which also depended on MetricsService (through FieldTrials). This two-sided dependency always annoyed me and made the code hard to restructure. BUG=98716 Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=117078 Review URL: http://codereview.chromium.org/9150016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@117171 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 117078 - Move creation and ownership of ResourceDispatcherHost and ↵jam@chromium.org2012-01-101-3/+2
| | | | | | | | | | | | | | | | | | | PluginService to content. This gives a few benefits: -avoid having each embedder know when to create/destruct these objects, as well as contained objects (i.e. those related to downloads) -avoid having to tell embedders about specifics of BrowserThread startup/shutdown -move ResourceDispatcherHost's getter to content where it belongs Some code (extensions+promos) used the fact that RDH is NULL in unittests as a signal to not use the utility process. I've switches those unittests to set a flag on the objects instead. I've taken out the DnsParallelism field trial (not used anymore, confirmed with jar) as it was the only thing that caused MetricsService to depend on IOThread initialization, which also depended on MetricsService (through FieldTrials). This two-sided dependency always annoyed me and made the code hard to restructure. BUG=98716 Review URL: http://codereview.chromium.org/9150016 TBR=jam@chromium.org git-svn-id: svn://svn.chromium.org/chrome/trunk/src@117096 0039d316-1c4b-4281-b951-d872f2087c98
* Move creation and ownership of ResourceDispatcherHost and PluginService to ↵jam@chromium.org2012-01-101-2/+3
| | | | | | | | | | | | | | | | | content. This gives a few benefits: -avoid having each embedder know when to create/destruct these objects, as well as contained objects (i.e. those related to downloads) -avoid having to tell embedders about specifics of BrowserThread startup/shutdown -move ResourceDispatcherHost's getter to content where it belongs Some code (extensions+promos) used the fact that RDH is NULL in unittests as a signal to not use the utility process. I've switches those unittests to set a flag on the objects instead. I've taken out the DnsParallelism field trial (not used anymore, confirmed with jar) as it was the only thing that caused MetricsService to depend on IOThread initialization, which also depended on MetricsService (through FieldTrials). This two-sided dependency always annoyed me and made the code hard to restructure. BUG=98716 Review URL: http://codereview.chromium.org/9150016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@117078 0039d316-1c4b-4281-b951-d872f2087c98
* Rip Out the Sidebar APIrdevlin.cronin@chromium.org2012-01-091-3/+1
| | | | | | | | | | | This fix removes the sidebar api and all its references from the code (primarily relating to chrome/common/extensions and chrome/browser/ui). BUG=107646 TEST=Covered by existing tests. Review URL: http://codereview.chromium.org/9006027 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@116901 0039d316-1c4b-4281-b951-d872f2087c98
* Remove the AudioManager singleton.tommi@chromium.org2011-12-121-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Unit tests now instantiate their own AudioManager and can choose to use the default one or provide their own mock implementation without having to worry about conflicting with the singleton. The teardown sequence of the AudioManager and its thread has been cleaned up significantly and I don't think it has been completely tested before as the audio thread was terminated before all objects that belonged to the thread had a chance to do cleanup. The AudioManager unit tests do not use the actual audio thread, so this part seems to have been left out. In Chrome, the AudioManager instance is now owned by BrowserProcessImpl and always constructed on the UI thread. This instance is then shared in the same way that several other 'manager' type objects are shared to 'content' code, via content::ResourceContext. Audio specific classes do though receive a direct pointer to the AudioManager and are required to do proper reference counting if they need to hold onto the instance. I chose to use the ResourceContext rather than direct use of g_browser_process to avoid requiring another singleton when writing relatively simple tests that touch the AudioManager. I added a couple of safeguards to guard against future regressions: - Not more than one instance of the AudioManager should be created. - The AudioManager should not be addrefed by its own thread. This can basically become a circular reference and prevent deterministic shutdown. Reviewers: Of course you're free to review everything, but here's the breakdown in terms of the bare minimum from the standpoint of "Owners approval". I'm asking Henrik to be the main reviewer of the entire patch (sorry!). Henrik: Everything minus the below, but it would be great if you could take a look at the whole thing, specifically media/audio. Pawel: I'd like you to take a generic look at this approach. The key areas as far as the singleton itself goes are in media/audio/audio_manager[_base].* and chrome/browser/browser_process*.* Satish: content/browser/speech/* media/audio/audio_manager_base.* (new reference counting code) Andrew: content/browser/renderer_host/media/* content/renderer/media/webrtc_audio_device_unittest.cc (Owner) Avi: content/browser/renderer_host/render_process_host_impl.cc content/browser/resource_context.* William: chrome/browser/profiles/profile_io_data.cc chrome/browser/browser_process*.* Robert: This is basically a heads up. I hope that I didn't break the OpenBSD implementation, but unfortunately I have no way of knowing for sure. Shijing: Please take a look at AudioManagerLinux. I replaced the set of active streams with a simple counter. BUG=105249 TEST=content_unittests, media_unittests, browser_tests. Review URL: http://codereview.chromium.org/8818012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@114084 0039d316-1c4b-4281-b951-d872f2087c98
* Remove BrowserThread::UnsafeGetBrowserThread, add UnsafeGetMessageLoopForThread.joi@chromium.org2011-12-071-28/+8
| | | | | | | | | | | | | | This also removes several accessors on BrowserProcess that are no longer used. I wanted to remove all retrieval of MessageLoop objects via BrowserThread, but this proved harder than it looked, because several net:: classes use MessageLoop and have fairly deep assumptions that it is a real MessageLoop, e.g. they use MessageLoopForIO with its IO observers and so forth. Therefore, we now have UnsafeGetMessageLoopForThread but UnsafeGetBrowserThread is gone. TBR=abodenha@chromium.org BUG=98716 Review URL: http://codereview.chromium.org/8769013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@113377 0039d316-1c4b-4281-b951-d872f2087c98
* Remove dead code for gpu blacklist auto-update.zmo@google.com2011-12-031-3/+0
| | | | | | | | | BUG=103851 TEST=tree R=kbr Review URL: http://codereview.chromium.org/8758003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@112879 0039d316-1c4b-4281-b951-d872f2087c98
* Remove IOThread::message_loop().joi@chromium.org2011-12-021-3/+0
| | | | | | | | | | | | | | | | | Instead introduce BrowserThread::UnsafeGetMessageLoop which is used in a couple of places. This will be removed in a follow-up change. I could have used UnsafeGetBrowserThread(id)->message_loop() but this is even easier to search for. Also, remove a couple of BrowserProcess accessors that aren't used by anybody, and that were using UnsafeGetBrowserThread. TBR=battre@chromium.org BUG=98716 Review URL: http://codereview.chromium.org/8775014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@112697 0039d316-1c4b-4281-b951-d872f2087c98
* DevTools: remove support for legacy remote debugger.yurys@chromium.org2011-11-241-2/+0
| | | | | | | | | | | DevTools remote debugging protocol supersedes the legacy protocol and old implementation should be removed. BUG=104625 TEST=Existing tests Review URL: http://codereview.chromium.org/8635005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@111540 0039d316-1c4b-4281-b951-d872f2087c98
* Make DevToolsManager a singleton, remove it from ContentBrowserClient.yurys@chromium.org2011-11-221-2/+0
| | | | | | | | | | | DevToolsManager should be created and destroyed inside content implementation, not by the embedder. BUG=104625 TEST=Exising tests Review URL: http://codereview.chromium.org/8609010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@111106 0039d316-1c4b-4281-b951-d872f2087c98
* Move enabling IPC logging for all child processes to the Content API.jam@chromium.org2011-11-181-7/+0
| | | | | | | BUG=98716 Review URL: http://codereview.chromium.org/8574070 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@110747 0039d316-1c4b-4281-b951-d872f2087c98
* redesign and reimplement proxy config service and tracker, revise proxy ui ↵kuan@chromium.org2011-11-041-8/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | on cros * original plan was to revise proxy ui on cros for all proxy sources and network types, refer to bug rpt 21219 for ui details * redesign and reimplement PrefProxyConfigTracker and PrefProxyConfigService by switching the inter-dependencies between the two and renaming the latter - PrefProxyConfigService used to observe PrefProxyConfigTracker and retrieve new prefs proxy from the latter whenever the former gets notification of proxy change from prefs or delegate service to determine effective proxy config. Now, PrefProxyConfigTracker pushes new prefs proxy to the renamed ChromeProxyConfigService on the IO thread; the latter then uses it and proxy from delegate service to determine effective proxy config. - remove all thread-switching in PrefProxyConfigTracker which now lives and runs on UI thread, except for when it pushes proxy config to ChromeProxyConfigService on IO thread - enhances and moves ConfigState definition to namespace ProxyPrefs to indicate source of proxy config (policy, extension, other-precede, system, fallback) so that PrefProxyConfigTracker, ChromeProxyConfigService and chromeos::ProxyConfigServiceImpl can acccess it - extract code for deciding effective proxy config from PrefProxyConfigService into static PrefProxyConfigTracker method to be shared by all classes * re-design and re-implement chromeos::ProxyConfigServiceImpl - this now extends PrefProxyConfigTracker to act as a special of "prefs", handles all proxy changes from network and prefs notifications and uses PrefProxyConfigTracker to push effective proxy to ChromeProxyConfigService and hence to network stack - remove wrapper chromeos::ProxyConfigService - this is the authority on cros, and ChromeProxyConfigService does not have a delegat service. - provide proxy config to ui for all proxy sources: policy, extension, network or recommended (in order of precedence), also indicates if proxy is user-modifiable - handle user profile changes to use correct PrefProxyConfigTracker * modify CoreOptionsHandler and CoreChromeosOptionsHandler to implement dynamic monitoring of prefs::kProxy and on-the-fly ui changes of affected use-shared-proxies user pref * modify ui native code, html, css and javascript for internet options and proxy pages to show yellow banner with different messages (same banner as options page when there's policy), en/dis-able ui fields, set current user profile in backend * modify network dropdown menu to always show proxy settings menu item as long as there's a network * modify automation tests, PrefProxyConfigTracker and ProxyConfigSerivceImpl unittests to handle redesign, fix unittests that fail due to redesign BUG=chromium-os:20679,chromium-os:21219 TEST=verify per bugs rpts Review URL: http://codereview.chromium.org/8102019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@108616 0039d316-1c4b-4281-b951-d872f2087c98
* Add CRL set updater.agl@chromium.org2011-09-301-0/+3
| | | | | | | | | | | | | This is just a dormant component updater for CRL sets. Since the call to start the initial load is commented out it's actually inactive, but it helps to split the CRL set change into parts to make it more easily reviewable. BUG=none TEST=none Review URL: http://codereview.chromium.org/8056013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@103466 0039d316-1c4b-4281-b951-d872f2087c98
* CrOS - Change OomPriorityManager from a Singleton to a member of ↵jamescook@chromium.org2011-09-201-0/+7
| | | | | | | | | | | BrowserProcessImpl BUG=none TEST=about:discards still shows a page listing open tabs Review URL: http://codereview.chromium.org/7973001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@101995 0039d316-1c4b-4281-b951-d872f2087c98
* Cleanup AutomationProviderList to fix shutdown crashes on ChromeOS auto testsstevenjb@google.com2011-09-161-1/+1
| | | | | | | | | | | | | | There is a circular relationship between BrowserProcessImpl and AutomationProvider. To clean this up and eliminate a shutdown crash: 1. Eliminate the AutomationProviderList singleton instance; it is already clearly owned by BrowserProcessImpl 2. Eliminate the calls to g_browser_process->Add/ReleaseModule in AutomationProvider since BrowserProcessImpl already owns AutomationProviderList (which owns any AutomationProvider instances). This could possibly have side effects if AutomationProvider attempts to access the message loop after the last call to BrowserProcessImpl::ReleaseModule exits the message loop, but that shouldn't be happening. BUG=96030 TEST=./run_remote_tests.sh --remote=localhost --ssh_port 9222 --use_emerged suite_Smoke and ensure no crashes occur in ~AutomationProvider Review URL: http://codereview.chromium.org/7790031 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@101582 0039d316-1c4b-4281-b951-d872f2087c98
* Remove string from BrowserProcess interface.tony@chromium.org2011-08-171-11/+0
| | | | | | | | | | | | It's an interface and shouldn't have any member variables. Also, it's not used anymore. TEST=PluginDataRemoverTest browser tests Review URL: http://codereview.chromium.org/7664018 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@97110 0039d316-1c4b-4281-b951-d872f2087c98
* Factor out dependncy on download throttling from core download code.jam@chromium.org2011-08-161-0/+1
| | | | | | | BUG=82782 Review URL: http://codereview.chromium.org/7660007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@96991 0039d316-1c4b-4281-b951-d872f2087c98
* Remove wstrings that aren't used from browser.h and browser_process.h.tony@chromium.org2011-08-101-8/+0
| | | | | | | | | | | This is from the old user data dir multi profile thingy that was removed ages ago. BUG=23581 Review URL: http://codereview.chromium.org/7497050 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@96236 0039d316-1c4b-4281-b951-d872f2087c98
* Component update part six, wire sigleton to browsercpu@chromium.org2011-08-031-0/+3
| | | | | | | | | | Also adds a minimalistic configurator TEST=none BUG=61602 Review URL: http://codereview.chromium.org/7545004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@95336 0039d316-1c4b-4281-b951-d872f2087c98
* Move gpu preliminary info collection from IO thread to FILE thread.zmo@google.com2011-07-281-0/+3
| | | | | | | | | | In linux we need certain file IO to collect preliminary gpu info. BUG=84497 TEST=bots green Review URL: http://codereview.chromium.org/7519007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@94592 0039d316-1c4b-4281-b951-d872f2087c98
* DevTools: move devtools_ui into content since it should be able to serve ↵pfeldman@chromium.org2011-07-271-0/+2
| | | | | | | | | | | devtools files. BUG=84078 TEST= Review URL: http://codereview.chromium.org/7453021 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@94290 0039d316-1c4b-4281-b951-d872f2087c98
* Move download stuff from download helper back to TabContents. This is ↵jam@chromium.org2011-07-151-1/+0
| | | | | | | | | basically a revert of r85762, with updating for code changes in the meantime. BUG=82782 Review URL: http://codereview.chromium.org/7374008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@92747 0039d316-1c4b-4281-b951-d872f2087c98
* Hooking MHTML generation to the browser.jcivelli@chromium.org2011-06-141-0/+3
| | | | | | | | | | | | | | This CL adds a class that can be used to generate MHTML for the current page of a tab. It is not yet surfaced in the UI. BUG=None TEST=Run the browser tests. Review URL: http://codereview.chromium.org/7044095 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@89047 0039d316-1c4b-4281-b951-d872f2087c98
* Remove g_browser_process dependency from content. Also make all the ↵jam@chromium.org2011-06-131-4/+0
| | | | | | | | | SyncChannels in the browser process ChannelProxy instead, since no code in the browser should send synchronous IPC messages. The renderer one was done like that a long time ago to send sync IPCs for accessibility, and we learnt that that doesn't work. BUG=76697 Review URL: http://codereview.chromium.org/7046100 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@88806 0039d316-1c4b-4281-b951-d872f2087c98
* Remove last safebrowsing references from content.jam@chromium.org2011-06-021-5/+8
| | | | | | | BUG=77089 Review URL: http://codereview.chromium.org/7108003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@87622 0039d316-1c4b-4281-b951-d872f2087c98
* Remove the background X11 thread.tony@chromium.org2011-06-011-9/+0
| | | | | | | | | | | | After r87381, we no longer have anything that uses the background X11 thread. I think there's still considerable cleanup that can be done to gtk_native_view_id_manager.*, but I'll do that in a follow up. Review URL: http://codereview.chromium.org/7020013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@87548 0039d316-1c4b-4281-b951-d872f2087c98
* Modifying the BackgroundModeManager to handle multiple profiles.rlp@chromium.org2011-05-281-0/+10
| | | | | | | | | | | | | | | The background mode manager is now owned by the broser The status tray is also owned by the browser process since there is only one per browser. Previously it was owned by the profile, but now that there are multiple profiles, it makes sense to have the browser process own it. Note: This CL does not unify the status tray into one icon. TEST=unittests (added BackgroundModeManagerTest::MultiProfile) BUG=80069, 82215 Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=86726 Review URL: http://codereview.chromium.org/6914021 Review URL: http://codereview.chromium.org/7008026 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@87119 0039d316-1c4b-4281-b951-d872f2087c98
* Fix gpu acceleration with --in-process-gpu and --single-process modes.sievers@google.com2011-05-271-3/+0
| | | | | | | | | | | | With recent changes that have moved gpu message handling in the browser to the IO thread (and moved the handling of messages between gpu and renderer, that are mediated by the browser, to GpuProcessHost), the routing for such messages was broken when running the gpu thread (rather than process). The new approach is to always instantiate GpuProcessHost (even when running a gpu thread only) and have a real IPC channel between host and gpu thread. This makes the 'in-process' GPU code work similar to what the renderer does when running --single-process. Note that --single-process mode is potentially still a bit fragile with this, since ChildProcess and ChildThread are currently written to only allow a single static instance in one process (it would be better to instantiate GpuProcess and RenderProcess simultaneously), so ambiguous calls to access e.g. the main thread are possible. Review URL: http://codereview.chromium.org/7054005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@86958 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 86724 - Modifying the BackgroundModeManager to handle multiple profiles.vandebo@chromium.org2011-05-251-10/+0
| | | | | | | | | | | | | | | | The background mode manager is now owned by the broser The status tray is also owned by the browser process since there is only one per browser. Previously it was owned by the profile, but now that there are multiple profiles, it makes sense to have the browser process own it. Note: This CL does not unify the status tray into one icon. TEST=unittests (added BackgroundModeManagerTest::MultiProfile) BUG=80069,82215 Review URL: http://codereview.chromium.org/6914021 TBR=rlp@chromium.org Review URL: http://codereview.chromium.org/7068025 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@86726 0039d316-1c4b-4281-b951-d872f2087c98
* Modifying the BackgroundModeManager to handle multiple profiles.rlp@chromium.org2011-05-251-0/+10
| | | | | | | | | | | | | The background mode manager is now owned by the broser The status tray is also owned by the browser process since there is only one per browser. Previously it was owned by the profile, but now that there are multiple profiles, it makes sense to have the browser process own it. Note: This CL does not unify the status tray into one icon. TEST=unittests (added BackgroundModeManagerTest::MultiProfile) BUG=80069,82215 Review URL: http://codereview.chromium.org/6914021 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@86724 0039d316-1c4b-4281-b951-d872f2087c98
* Remove a chrome dependency by removing Prerender from ResourceDispatcherHost.dominich@chromium.org2011-05-251-0/+6
| | | | | | | | | BUG=82590,77090 TEST=Prerender* Review URL: http://codereview.chromium.org/6966017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@86667 0039d316-1c4b-4281-b951-d872f2087c98
* Websocket to TCP proxy running in a separate thread (only on ChromeOS).dilmah@chromium.org2011-05-101-0/+7
| | | | | | | | | | | | | | | | | | With this webproxy: authorized extensions can connect to ws://127.0.0.1:10101/tcpproxy, pass authorization_token:hostname:port: in first frame, then webproxy establishes TCP connection to hostname:port and forwards any subsequent communication. Subsequent communication between extension and webproxy is base64-encoded. TODO(dilmah): remove this temporary solution, get rid of separate thread and listening socket, instead provide the same functionality via hooks into websocket layer. BUG=chromium-os:9667 TEST=Manual Review URL: http://codereview.chromium.org/6801008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@84795 0039d316-1c4b-4281-b951-d872f2087c98
* Print Preview: Print in the background.thestig@chromium.org2011-05-071-0/+3
| | | | | | | | BUG=79531 TEST=Print preview tab closes print button is pressed. Printing succeeds. Review URL: http://codereview.chromium.org/6930034 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@84539 0039d316-1c4b-4281-b951-d872f2087c98
* Moved URLRequestContextGetter to net/ so it can be used by projects such as ↵sanjeevr@chromium.org2011-03-311-2/+5
| | | | | | | | | | jingle. BUG=None TEST=Build. Review URL: http://codereview.chromium.org/6778025 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@80033 0039d316-1c4b-4281-b951-d872f2087c98
* Move some files from base to base/memory.levin@chromium.org2011-03-281-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | raw_scoped_refptr_mismatch_checker.h ref_counted.cc ref_counted.h ref_counted_memory.cc ref_counted_memory.h ref_counted_unittest.cc scoped_callback_factory.h scoped_comptr_win.h scoped_handle.h scoped_native_library.cc scoped_native_library.h scoped_native_library_unittest.cc scoped_nsobject.h scoped_open_process.h scoped_ptr.h scoped_ptr_unittest.cc scoped_temp_dir.cc scoped_temp_dir.h scoped_temp_dir_unittest.cc scoped_vector.h singleton.h singleton_objc.h singleton_unittest.cc linked_ptr.h linked_ptr_unittest.cc weak_ptr.cc weak_ptr.h weak_ptr_unittest.cc BUG=None TEST=Compile Review URL: http://codereview.chromium.org/6714032 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@79524 0039d316-1c4b-4281-b951-d872f2087c98
* Remove the check for inspector files since they're in resources.pak now.tony@chromium.org2011-03-231-9/+0
| | | | | | | | | | | | | | | | | In r79038, I moved the inspector files into resources.pak so we no longer need to check to see if inspector is available (it should always be there). Also fix chrome --diagnostics to check for resources.pak rather than the resources/Inspector dir. BUG=77167 TEST=Delete resources/inspector from disk, start chrome and right click on a page. Inspect Element should be there and work. Review URL: http://codereview.chromium.org/6726027 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@79170 0039d316-1c4b-4281-b951-d872f2087c98
* This is a thread that runs in the browser process that can issue GL calls ↵apatrick@chromium.org2011-03-211-0/+3
| | | | | | | | | | | | | | | | | | | | | | without going via a command buffer. It is for rendering the browser's chrome, basic compositing, etc. It is not for rendering arbitrary content from, for example, WebGL. It is only enabled with --single-process or --in-process-gpu, the latter only running the GPU "process" as a thread inside the browser process. Eventually, the plan is to add strict validation to ensure it can only run basic white-listed shaders and other restrictions so that the browser's GPU thread can be made available to the renderers' compositors without a command line switch. I split GpuThread into two new classes. GpuChildThread derives from ChildThread and contains stuff that should only happen in a standalone process. I included GPUInfo collection here because if the browser should never need to run that. GpuRenderThread contains stuff that is also needed in the browser process. The GPU thread does not use an IPC channel within the browser process. It still uses IPC messages but posts them directly between message loops. I changed the EstablishGpuChannel messages between the browser and GPU process to not deal with returning the GPUInfo. Now the GPU process just sends it as the first thing it does after handling its Init message. This was to allow the separation of GPUInfo collection (in GpuChildThread) and channel establishment (in GpuRenderThread). TEST=trybots, run webgl with no switches, --single-process and --in-process-gpu, check browser terminates cleanly in all cases. BUG=none Review URL: http://codereview.chromium.org/6677055 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@78945 0039d316-1c4b-4281-b951-d872f2087c98
* This is an extension of http://codereview.chromium.org/6280018 that provides ↵battre@chromium.org2011-03-161-0/+16
| | | | | | | | | | | | | a proxy configuration which respects command line parameters and policies This was committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=78228, iyengar asked to commit again after fixing trunk. BUG=67232,70732 TEST=Start chrome, observe two PROXY_CONFIG_CHANGED events in about:net-internals (if you are on a corporate network with PAC configurations), observe that everything behaves as usual. In particular the https://www.google.com/searchdomaincheck?format=domain&type=chrome request should not fail as it uses the new system URLRequestContext. Review URL: http://codereview.chromium.org/6292017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@78362 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 78228 - Extended: Add "system" URLRequestContext (not ready for use!)jam@chromium.org2011-03-151-16/+0
| | | | | | | | | | | | | | This is an extension of http://codereview.chromium.org/6280018 that provides a proxy configuration which respects command line parameters and policies BUG=67232,70732 TEST=Start chrome, observe two PROXY_CONFIG_CHANGED events in about:net-internals (if you are on a corporate network with PAC configurations), observe that everything behaves as usual. In particular the https://www.google.com/searchdomaincheck?format=domain&type=chrome request should not fail as it uses the new system URLRequestContext. Review URL: http://codereview.chromium.org/6292017 TBR=battre@chromium.org Review URL: http://codereview.chromium.org/6693023 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@78240 0039d316-1c4b-4281-b951-d872f2087c98
* Extended: Add "system" URLRequestContext (not ready for use!)battre@chromium.org2011-03-151-0/+16
| | | | | | | | | | | This is an extension of http://codereview.chromium.org/6280018 that provides a proxy configuration which respects command line parameters and policies BUG=67232,70732 TEST=Start chrome, observe two PROXY_CONFIG_CHANGED events in about:net-internals (if you are on a corporate network with PAC configurations), observe that everything behaves as usual. In particular the https://www.google.com/searchdomaincheck?format=domain&type=chrome request should not fail as it uses the new system URLRequestContext. Review URL: http://codereview.chromium.org/6292017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@78228 0039d316-1c4b-4281-b951-d872f2087c98
* Reverting the revert 76468. Removed include for browser_thread.h.rtenneti@chromium.org2011-03-021-0/+4
| | | | | | | | | | | | | | | | Enable the WATCHDOG thread that monitors browser threads for their responsiveness using ping-pong messaging. WACTHDOG thread also collects statistics for response time for each thread via histograms. This CL was approved http://codereview.chromium.org/6588039 BUG=71378, 73915, 73844, 73975 TEST=performance tests TBR=jar Review URL: http://codereview.chromium.org/6591091 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76561 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 76468 - Added back thread watcher changes.rtenneti@chromium.org2011-03-021-4/+0
| | | | | | | | | | | | BUG=71378,73915,73844,73975 TEST=performance tests Review URL: http://codereview.chromium.org/6588039 TBR=rtenneti@chromium.org Review URL: http://codereview.chromium.org/6597088 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76469 0039d316-1c4b-4281-b951-d872f2087c98
* Added back thread watcher changes.rtenneti@chromium.org2011-03-021-0/+4
| | | | | | | | | BUG=71378,73915,73844,73975 TEST=performance tests Review URL: http://codereview.chromium.org/6588039 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76468 0039d316-1c4b-4281-b951-d872f2087c98
* Make the ChromeNetworkDelegate use the ExtensionEventRouterForwarderjochen@chromium.org2011-03-011-0/+3
| | | | | | | | | BUG=73903 TEST=tests for proxy and webrequest API should still work Review URL: http://codereview.chromium.org/6598002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76372 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 76199 - Trying changes to see the perfomance impact on Mac.rtenneti@chromium.org2011-02-281-4/+0
| | | | | | | | | | | | | This change list is same as CL 6588039. BUG=73915 Review URL: http://codereview.chromium.org/6602004 TBR=rtenneti@chromium.org Review URL: http://codereview.chromium.org/6591035 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76200 0039d316-1c4b-4281-b951-d872f2087c98
* Trying changes to see the perfomance impact on Mac.rtenneti@chromium.org2011-02-281-0/+4
| | | | | | | | | | | This change list is same as CL 6588039. Will back out immediately. BUG=73915 Review URL: http://codereview.chromium.org/6602004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76199 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 76168 - Trying changes to see the perfomance impact on Mac.rtenneti@chromium.org2011-02-261-4/+0
| | | | | | | | | | | | | | This change list is same as CL 6588039. Will back out immediately. http://codereview.chromium.org/6588039/ Review URL: http://codereview.chromium.org/6594032 TBR=rtenneti@chromium.org Review URL: http://codereview.chromium.org/6588041 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76170 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-05-12 11:48:57 +0000