summaryrefslogtreecommitdiffstats
path: root/chrome/browser/browser_main.cc
Commit message (Collapse)AuthorAgeFilesLines
* Change UI font at startup time if necessary, based on the UI locale.satorux@chromium.org2010-09-091-0/+18
| | | | | | | | | | | | | | | | | | | | | | As of writing, ChromeDroidSans is used as the UI font (see /etc/gtk-2.0/gtkrc). This setting does not work well for Japanese users as Chinese glyphs are used for Kanji characters. For Japanese UI, we should use a Japanese font. Introduce IDS_UI_FONT_FAMILY_CROS to control the UI font based on the UI locale. For now, app_locale_settings_ja.xtb only contains a non-default value: IPAPGothic. Just for the record, I originally tried to use "DroidSans Japanese" but for some reason, this caused space characters (0x20) to be garbled in the wrench menu. Hence, IPAPGotchic is chosen for now. TEST=manually on the netbook, and ubuntu BUG=chromium-os:4038 Review URL: http://codereview.chromium.org/3275008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@58913 0039d316-1c4b-4281-b951-d872f2087c98
* Cleanup some duplicated includes.tfarina@chromium.org2010-09-041-1/+0
| | | | | | | | | BUG=None TEST=trybots Review URL: http://codereview.chromium.org/3358014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@58582 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 58493 - Call InitEventRouters after a successful chromeos login. This ↵stoyan@chromium.org2010-09-031-4/+0
| | | | | | | | | | | | | | | | | | | | | successfully solves a problem where extension event listeners were never getting called on Chrome OS because InitEventRouters wasn't getting called from browser_main.cc if the profile was in the temporary OTR state while the login was in progress. Does this need a check to make sure it doesn't happen twice? BUG=51724 TEST=Log in, test simple extension that notifies when a tab is created. Review URL: http://codereview.chromium.org/3177006 TBR=dmazzoni@chromium.org Review URL: http://codereview.chromium.org/3306008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@58502 0039d316-1c4b-4281-b951-d872f2087c98
* Call InitEventRouters after a successful chromeos login. This successfullydmazzoni@chromium.org2010-09-031-0/+4
| | | | | | | | | | | | | | | | solves a problem where extension event listeners were never getting called on Chrome OS because InitEventRouters wasn't getting called from browser_main.cc if the profile was in the temporary OTR state while the login was in progress. Does this need a check to make sure it doesn't happen twice? BUG=51724 TEST=Log in, test simple extension that notifies when a tab is created. Review URL: http://codereview.chromium.org/3177006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@58493 0039d316-1c4b-4281-b951-d872f2087c98
* Update the Preconnect logic to use the new HttpStreamFactory formbelshe@chromium.org2010-09-031-2/+1
| | | | | | | | | | | | | | | | creating connections rather than doing it manually. With this update, I believe we no longer need to avoid preconnects through proxies. The new logic can handle that case. Also updated the predictor_api slightly for the next wave of work. BUG=none TEST=existing Review URL: http://codereview.chromium.org/3226011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@58464 0039d316-1c4b-4281-b951-d872f2087c98
* Set default browser AFTER import.mirandac@chromium.org2010-09-011-0/+1
| | | | | | | | | BUG=53655 TEST=set Firefox as default browser on Windows. Run Chrome with a fresh profile. Import from FF should occur. Review URL: http://codereview.chromium.org/3298004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@58176 0039d316-1c4b-4281-b951-d872f2087c98
* Reduce the number of files that recompile when changing template_url.h or ↵levin@chromium.org2010-08-311-1/+2
| | | | | | | | | | | | | | | | | | template_url_model.h. Separated out the TemplateURL::IDType which is now TemplateURLId into its own file, since this was a primary reason for including template_url.h in another header. Similarly separate out the TemplateURLModelObserver from template_url_model.h to reduce how often that file is included. BUG=None TEST=Compiling. Review URL: http://codereview.chromium.org/3270011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@58080 0039d316-1c4b-4281-b951-d872f2087c98
* Support handling blob URL and resolve blob references in upload data.jianli@chromium.org2010-08-311-1/+3
| | | | | | | | | BUG=none TEST=unittest Review URL: http://codereview.chromium.org/3282003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@57938 0039d316-1c4b-4281-b951-d872f2087c98
* Create an instance of AtExitManager before relaunching the browser on ↵prasadt@chromium.org2010-08-281-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | Windows. This is needed for two reasons: 1) The RelaunchChromeBrowserWithNewCommandLineIfNeeded() code path on Windows invokes Singleton<PathData>::get() to get the module. This in turn requires an instance of AtExitManager to be present, as it manages the lifetime of singletons. 2) The point at which the RelaunchChromeBrowserWithNewCommandLineIfNeeded() is invoked we return from ChromeMain and thus the instance of AtExitManager that belongs to chrome.dll is already deleted. 3) Note that there is another instance of AtExitManager that's instantiated in wWinMain() that's still alive. But the scope of that is in chrome.exe and not chrome.dll, and hence is not visible to the code in RelaunchChromeBrowserWithNewCommandLineIfNeeded(). BUG=none TEST=On Windows - Change BrowserProcessImpl::StartAutoupdateTimer() function to change the timer from 6hrs to 30 seconds. Build and run chrome with --no-startup-window and --keep-alive-for-test flags. Copy chrome.exe to new_chrome.exe to fake an update. Wait for 30 seconds and verify that the browser shuts down and restarts. Also verify that new_chrome.exe is deleted and there is an old_chrome.exe. Review URL: http://codereview.chromium.org/3104037 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@57756 0039d316-1c4b-4281-b951-d872f2087c98
* Implement about:labsthakis@chromium.org2010-08-271-0/+4
| | | | | | | | | | | | | Tabpose is currently the only lab on mac, tabs-on-left the only lab on windows. Nothing for linux yet. BUG=53399 TEST=Go to about:labs. Should have one feature on windows and osx each, none on linux yet. about:labs should not be visible on the stable channel. Labs that were enabled on the dev channel should not be enabled on the stable channel. about:labs in chromeos should still work (they use a different implementation) Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=57635 Review URL: http://codereview.chromium.org/3152055 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@57670 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 57635: Implement about:labsdpolukhin@chromium.org2010-08-271-4/+0
| | | | | | | | | | | | | | | | Original CL: http://codereview.chromium.org/3152055 Implement about:labs Tabpose is currently the only lab on mac, tabs-on-left the only lab on windows. Nothing for linux yet. BUG=53399 TEST=Go to about:labs. Should have one feature on windows and osx each, none on linux yet. about:labs should not be visible on the stable channel. Labs that were enabled on the dev channel should not be enabled on the stable channel. about:labs in chromeos should still work (they use a different implementation) TBR=thakis@chromium.org Review URL: http://codereview.chromium.org/3256001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@57664 0039d316-1c4b-4281-b951-d872f2087c98
* Implement about:labsthakis@chromium.org2010-08-271-0/+4
| | | | | | | | | | | Tabpose is currently the only lab on mac, tabs-on-left the only lab on windows. Nothing for linux yet. BUG=53399 TEST=Go to about:labs. Should have one feature on windows and osx each, none on linux yet. about:labs should not be visible on the stable channel. Labs that were enabled on the dev channel should not be enabled on the stable channel. about:labs in chromeos should still work (they use a different implementation) Review URL: http://codereview.chromium.org/3152055 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@57635 0039d316-1c4b-4281-b951-d872f2087c98
* Move prefs-related files under chrome/browser/ into a prefs/ subdir.evan@chromium.org2010-08-261-3/+3
| | | | | | | | | | | | Rename includes, resort header include order in places where the rename changed the order. BUG=50548 TEST=compiles Review URL: http://codereview.chromium.org/3203008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@57434 0039d316-1c4b-4281-b951-d872f2087c98
* Refactor new first run control flow.estade@chromium.org2010-08-251-1/+1
| | | | | | | | | | | | | Factor out the common code so that Mac and Linux may share the new flow with Windows (e.g., import is done before the first run dialog appears). Windows *should* be unaffected by this change. Linux has some non-user-visible changes. The user visible changes (showing the default search engine in the ballot, for example) are TODO. BUG=49705,47651 TEST=launching chromium with --first-run works as expected, i.e. it imports stuff from your default browser (such as history); if that browser is firefox and firefox is open, the failure is silent. Review URL: http://codereview.chromium.org/3171029 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@57421 0039d316-1c4b-4281-b951-d872f2087c98
* A/B experiment for re-establishing TCP connections.ziadh@chromium.org2010-08-251-0/+29
| | | | | | | | | | | | | We would like to test the impact of automatic retries when a TCP connection exceeds a certain threshold before it gets back an ACK. We are observing a fair number of sockets where the connection had been established, but the sockets were not used thereafter. r=mbelche Review URL: http://codereview.chromium.org/3191019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@57276 0039d316-1c4b-4281-b951-d872f2087c98
* Resubmit r56600 - Start/stop service process when browser starts and stophclam@chromium.org2010-08-231-0/+16
| | | | | | | | | | | | | | | | | Save the information that the setup of remoting has completed. After setup has been completed we start and stop service process when --enable-remoting presents when browser starts. Also save the information in the service process that host is registered and ready to be used. Again start chromoting host automatically once the host registration is done. BUG=50244, 50242, 50243, 50249 Review URL: http://codereview.chromium.org/3153029 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@57120 0039d316-1c4b-4281-b951-d872f2087c98
* Enable spdy to 95%, npn only to 5%.lzheng@chromium.org2010-08-201-9/+2
| | | | | | | | BUG=48964 TEST=none Review URL: http://codereview.chromium.org/3115023 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@56915 0039d316-1c4b-4281-b951-d872f2087c98
* net: expect MITM attacks with HTTP proxies and command line flag.agl@chromium.org2010-08-191-0/+2
| | | | | | | | | | | | | | | | | With r51258 we started requiring the TLS renegotiation extension from a whitelist of servers that we knew supported it. When Chrome is getting MITM attacked, this extension can be removed and this broke some debugging tools (which intercept SSL connections) and some proxies which do the same. This patch causes us to expect to be MITM attacked when tunneling via an HTTP proxy and when the --allow-ssl-mitm-proxies command line flag is given. BUG=48485 TEST=Can't really test without one of these MITM proxy machines. http://codereview.chromium.org/3111019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@56727 0039d316-1c4b-4281-b951-d872f2087c98
* Switch to GoogleServiceAuthError struct instead of GaiaAuthError.chron@chromium.org2010-08-191-2/+2
| | | | | | | | | | | | Remove CAPTCHA code from existing user controller and plumb into google authenticator2. TEST=Install ChromeOS build. Hit Captcha. Enter captcha. BUG=50408 Review URL: http://codereview.chromium.org/3134009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@56724 0039d316-1c4b-4281-b951-d872f2087c98
* Extract connection logic from HttpNetworkTransaction into a newmbelshe@chromium.org2010-08-191-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | HttpStreamFactory. The HttpNetworkTransaction now deals exclusively with streams rather than connections directly. This cut the size of HTN roughly in in half. The HttpNetworkTransaction is still responsible for all proxy and server authentication functions. This is because the streams may come and go - we could create a stream, have the server declare auth is needed, and then the next attempt would be on a different stream. So Auth belongs on the HNT. The HNT no longer has direct access to the connection itself; instead, it only knows of an HttpStream. The StreamRequest, however, is responsible for determining whether the connection needs to use a proxy, whether AlternateProtocols are available, and whether the connection should be SPDY or HTTP. Other changes: - moved some static configuration methods from HNT to HttpStreamFactory. - added some methods to the HttpStream. BUG=none TEST=all Review URL: http://codereview.chromium.org/3171002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@56646 0039d316-1c4b-4281-b951-d872f2087c98
* Add a command-line flag to disable SSL/TLS False Startdavidben@chromium.org2010-08-181-0/+2
| | | | | | | | | | | | | | Some servers are not compatible with False Start. Adding a command-line flag will make it easier to test and verify such cases. Also, blacklist www.picnik.com as incompatible with False Start. BUG=50650 TEST=see bug Review URL: http://codereview.chromium.org/3167015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@56622 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 56600 - ServiceProcessControlBrowserTest.LaunchAndIPC crashes.rvargas@google.com2010-08-181-16/+0
| | | | | | | | | | | | | | | | | | | | Start/stop service process when browser starts and stop Save the information that the setup of remoting has completed. After setup has been completed we start and stop service process when --enable-remoting presents when browser starts. Also save the information in the service process that host is registered and ready to be used. Again start chromoting host automatically once the host registration is done. Review URL: http://codereview.chromium.org/3185015 TBR=hclam@chromium.org Review URL: http://codereview.chromium.org/3107024 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@56610 0039d316-1c4b-4281-b951-d872f2087c98
* Start/stop service process when browser starts and stophclam@chromium.org2010-08-181-0/+16
| | | | | | | | | | | | | | | Save the information that the setup of remoting has completed. After setup has been completed we start and stop service process when --enable-remoting presents when browser starts. Also save the information in the service process that host is registered and ready to be used. Again start chromoting host automatically once the host registration is done. Review URL: http://codereview.chromium.org/3185015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@56600 0039d316-1c4b-4281-b951-d872f2087c98
* Rework gfx::Font by moving platform-specific code into inner classes.ben@chromium.org2010-08-131-2/+3
| | | | | | | | | | | | | gfx::Font is a platform-neutral API shim that exists as a wrapper object to allow for the creation and lifetime of gfx::Font objects to remain consistent with past usage. gfx::PlatformFont is an interface implemented by the platform-specific inner classes (gfx::PlatformFontWin,Mac,Gtk). BUG=none TEST=existing unittests Review URL: http://codereview.chromium.org/3083022 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@56040 0039d316-1c4b-4281-b951-d872f2087c98
* Fix for issue 51693, which was a regression from integrating the open sourcerogerta@google.com2010-08-131-0/+2
| | | | | | | | | | | | | | | | version of RLZ into Chromium. Chromium should never send RLZ pings to Google, only Google Chrome should do so. Removing dependency from rlz chrome extenion api to RLZTracker since it is not required. BUG=51693 TEST=Install Chromium on a clean machine and make sure no pings are sent to http://client1.google.com/tools/pso/ping?... Review URL: http://codereview.chromium.org/3146007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@56032 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 55797 - Disable support of --enable-preconnect flagziadh@chromium.org2010-08-111-1/+6
| | | | | | | | | | | | | | | The preconenct feature is still not fully implemented yet. We would like to disable it for M6 as it is causing crashes. This is a temporary 'fix'. BUG=48549 r=jar Review URL: http://codereview.chromium.org/3140007 TBR=ziadh@chromium.org Review URL: http://codereview.chromium.org/3161007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@55806 0039d316-1c4b-4281-b951-d872f2087c98
* Disable support of --enable-preconnect flagziadh@chromium.org2010-08-111-6/+1
| | | | | | | | | | | | The preconenct feature is still not fully implemented yet. We would like to disable it for M6 as it is causing crashes. This is a temporary 'fix'. BUG=48549 r=jar Review URL: http://codereview.chromium.org/3140007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@55797 0039d316-1c4b-4281-b951-d872f2087c98
* net: add embedded DNSSEC chain support.agl@chromium.org2010-08-111-0/+3
| | | | | | | | | | | | | | | | | Now that the DNS root is signed we have a good trust path in several TLDs (including .org). This patch enables self-signed certificates to include a DNSSEC chain as an extension which proves a CERT record, containing the fingerprint of the public key. The format of the chain is still undecided, so this is only enabled with --enable-dnssec-certs. BUG=none TEST=net_unittests http://codereview.chromium.org/2806076 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@55771 0039d316-1c4b-4281-b951-d872f2087c98
* Added event traces at various points during Chrome and ChromeFrame startup ↵ananta@chromium.org2010-08-111-0/+7
| | | | | | | | | | to help measure and track performance. Bug=51638 Review URL: http://codereview.chromium.org/3152001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@55671 0039d316-1c4b-4281-b951-d872f2087c98
* Histograms & Field Trails about prefetchinggavinp@google.com2010-08-091-0/+23
| | | | | | | | | | | | This CL lands some histograms to track prefetching, and a 10% field trial enabling the feature to track performance. BUG=none TEST=none Review URL: http://codereview.chromium.org/3036050 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@55431 0039d316-1c4b-4281-b951-d872f2087c98
* More metrics for proxy connections impact A/B test.ziadh@chromium.org2010-08-091-4/+4
| | | | | | | | | | | | | I added socket request times (for new/unused sockets). The hypothesis is that if proxy servers get overloaded, we will see an increase in request times for new sockets. Hence, we know that we should tone back a little. BUG=44501 r=jar Review URL: http://codereview.chromium.org/3040049 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@55377 0039d316-1c4b-4281-b951-d872f2087c98
* Bad interaction between 2 A/B experimentsziadh@chromium.org2010-08-061-3/+14
| | | | | | | | | | | | | | There is a 1/20 chance that the max number of sockets per group be greater than the max number of sockets per proxy server. This would result in hitting a DCHECK in client_socket_pool_base.cc:145. This CL attempts to circumvent that event. r=jar Review URL: http://codereview.chromium.org/3044051 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@55303 0039d316-1c4b-4281-b951-d872f2087c98
* Reland 54771 (and 54795) To enable TCP Preconnection by defaultjar@chromium.org2010-08-061-1/+6
| | | | | | | | | | | | | | | | | | | | | | | I pulled out the code to update the socket connectivity stats. I added defensive code which should preclude the crash that was reported on the stability bot. I added a second call to update the stats from ~ClientSocketHandle to ensure that we updated the related ClientSocket when we are torn down. As noted in the original checkin: Enable speculative preconnection by default Added histogram to track preconnection utilization (vs waste). BUG=42694 r=mbelshe Review URL: http://codereview.chromium.org/3050040 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@55197 0039d316-1c4b-4281-b951-d872f2087c98
* Have MakeName prepend the underscore to the field trial group name,mlloyd@chromium.org2010-08-051-13/+13
| | | | | | | | | | | | | | | | | | | | rather than having the field trial group name itself include the underscore. This will change the histogram names for only one field trial, the CacheSizeGroup field trial, and I have got in touch with Mike and Ricardo (who wrote that code); they confirmed that they don't mind the name change. Also updates the field trial unit tests to reflect the change, and to make the use of the expected/actual arguments to the unit test macros consistent TEST=Unit tests pass. BUG=None. Review URL: http://codereview.chromium.org/3066036 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@55146 0039d316-1c4b-4281-b951-d872f2087c98
* [ChromeOS] When doing a stub-login for chromeos, avoid the ↵cmasone@google.com2010-08-051-1/+7
| | | | | | | | | | | | | | | | | | | | already-logged-in-user path Before r54950, we used the kLoginUser switch to indicate that chrome had crashed, and we were relaunching it for the indicated user. http://src.chromium.org/viewvc/chrome?view=rev&revision=54950 introduced a new semantic: if passed along with kLoginPassword, this flag now indicated that a mocked-out login should be attempted with the given credentials. Doing this as well as starting up like we were relaunching the browser for the indicated user caused some DCHECKs to fire. BUG=None TEST=do a stub login, watch it succeed Review URL: http://codereview.chromium.org/3026053 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@55127 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 55071 - Reland 54771 (and 54795) To enable TCP Preconnection by defaultdhollowa@chromium.org2010-08-051-6/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Leaks reported with this CL. http://build.chromium.org/buildbot/memory/builders/Linux%20Heapcheck/builds/6130/steps/heapcheck%20test:%20net/logs/stdio Eg. Leak of 24 bytes in 1 objects allocated from: @ 84aece net::SSLClientSocketNSS::BufferRecv @ 84b161 net::SSLClientSocketNSS::DoTransportIO @ 84ca1f net::SSLClientSocketNSS::DoHandshakeLoop @ 84ca6b net::SSLClientSocketNSS::OnHandshakeIOComplete @ 84cadc net::SSLClientSocketNSS::OnRecvComplete @ 84cbb0 net::SSLClientSocketNSS::BufferRecvComplete @ 84ea4b void DispatchToMethod @ 84ea7b CallbackImpl::RunWithParams @ 4b3a10 CallbackRunner::Run @ 853e7e net::TCPClientSocketLibevent::DoReadCallback @ 85426f net::TCPClientSocketLibevent::DidCompleteRead @ 856a5c net::TCPClientSocketLibevent::ReadWatcher::OnFileCanReadWithoutBlocking @ 93d8fd base::MessagePumpLibevent::FileDescriptorWatcher::OnFileCanReadWithoutBlocking @ 93d966 base::MessagePumpLibevent::OnLibeventNotification @ 9da639 event_process_active @ 9da923 event_base_loop @ 93dfd0 base::MessagePumpLibevent::Run @ 8f2873 MessageLoop::RunInternal @ 8f2893 MessageLoop::RunHandler @ 8f2938 MessageLoop::Run @ 44b7f9 TestCompletionCallback::WaitForResult @ 6a1ee6 SSLClientSocketTest_ConnectMismatched_Test::TestBody @ 961831 testing::Test::Run @ 965026 testing::internal::TestInfoImpl::Run @ 96515c testing::TestCase::Run @ 965bbe testing::internal::UnitTestImpl::RunAllTests @ 965d35 testing::UnitTest::Run @ 4a4bf7 TestSuite::Run @ 4a3b6d main @ 2adff5bb11c4 __libc_start_main Suppression: { <insert_a_suppression_name_here> Heapcheck:Leak fun:net::SSLClientSocketNSS::BufferRecv fun:net::SSLClientSocketNSS::DoTransportIO fun:net::SSLClientSocketNSS::DoHandshakeLoop fun:net::SSLClientSocketNSS::OnHandshakeIOComplete fun:net::SSLClientSocketNSS::OnRecvComplete fun:net::SSLClientSocketNSS::BufferRecvComplete fun:void DispatchToMethod fun:CallbackImpl::RunWithParams fun:CallbackRunner::Run fun:net::TCPClientSocketLibevent::DoReadCallback fun:net::TCPClientSocketLibevent::DidCompleteRead fun:net::TCPClientSocketLibevent::ReadWatcher::OnFileCanReadWithoutBlocking fun:base::MessagePumpLibevent::FileDescriptorWatcher::OnFileCanReadWithoutBlocking fun:base::MessagePumpLibevent::OnLibeventNotification fun:event_process_active fun:event_base_loop fun:base::MessagePumpLibevent::Run fun:MessageLoop::RunInternal fun:MessageLoop::RunHandler fun:MessageLoop::Run fun:TestCompletionCallback::WaitForResult fun:SSLClientSocketTest_ConnectMismatched_Test::TestBody fun:testing::Test::Run fun:testing::internal::TestInfoImpl::Run fun:testing::TestCase::Run fun:testing::internal::UnitTestImpl::RunAllTests fun:testing::UnitTest::Run fun:TestSuite::Run fun:main fun:__libc_start_main } I added defensive code in ClientSocketHandle::ReleaseSocket(), which should preclude the crash that was reported on the stability bot. I added a second call to ReleaseSocket() from ~ClientSocketHandle to ensure that we updated the related ClientSocket when we are torn down. r=mbelshe Review URL: http://codereview.chromium.org/3071022 TBR=jar@chromium.org git-svn-id: svn://svn.chromium.org/chrome/trunk/src@55090 0039d316-1c4b-4281-b951-d872f2087c98
* Reland 54771 (and 54795) To enable TCP Preconnection by defaultjar@chromium.org2010-08-051-1/+6
| | | | | | | | | | | | | | | I added defensive code in ClientSocketHandle::ReleaseSocket(), which should preclude the crash that was reported on the stability bot. I added a second call to ReleaseSocket() from ~ClientSocketHandle to ensure that we updated the related ClientSocket when we are torn down. r=mbelshe Review URL: http://codereview.chromium.org/3071022 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@55071 0039d316-1c4b-4281-b951-d872f2087c98
* FBTF: Remove unneeded headers from base/ (part 1)thestig@chromium.org2010-08-051-2/+0
| | | | | | | | BUG=none TEST=none Review URL: http://codereview.chromium.org/3071012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@55034 0039d316-1c4b-4281-b951-d872f2087c98
* To effectively test some parts of chrome for cros on the linux desktop, we ↵davemoore@chromium.org2010-08-041-0/+45
| | | | | | | | need a way to start chrome logged in. The login UI requires the WM to display, so I added command line options to do this. But we needed the full functionality of login, which doesn't work when libcros can't be loaded. I created stubs for all the cros api. I then took both stubs and the real implementations and put them entirely inside the .cc files (no separate declaration of the implementations in the .h files). Review URL: http://codereview.chromium.org/3076029 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@54950 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 54771 - Enable speculative preconnection by defaultjar@chromium.org2010-08-041-6/+1
| | | | | | | | | | | | | | Added histogram to track utilization (vs waste). [The stability bot was reporting problems, so I'm reverting] r=mbelshe Review URL: http://codereview.chromium.org/3026038 TBR=jar@chromium.org Review URL: http://codereview.chromium.org/3090011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@54930 0039d316-1c4b-4281-b951-d872f2087c98
* Remove wstrings from l10n_util/ResourceBundle locale functions.evan@chromium.org2010-08-041-1/+1
| | | | | | Review URL: http://codereview.chromium.org/3069026 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@54917 0039d316-1c4b-4281-b951-d872f2087c98
* First stage of proxy extension API.pam@chromium.org2010-08-041-1/+1
| | | | | | | | | | | | | Adds a basic API that will cover the features available with the --proxy-server command-line switch, once the underlying proxy config is rewritten to actually access the pref dynamically rather than only ever loading a proxy config on startup. BUG=48930 TEST=covered by browser_tests (ExtensionApiTest.Proxy*) Review URL: http://codereview.chromium.org/3074013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@54882 0039d316-1c4b-4281-b951-d872f2087c98
* De-wstringify some browser startup code and net utility.evan@chromium.org2010-08-041-2/+3
| | | | | | Review URL: http://codereview.chromium.org/3054042 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@54860 0039d316-1c4b-4281-b951-d872f2087c98
* [ChromeOS] Keep logging inside the user's home dir, even after a browser crashcmasone@google.com2010-08-041-0/+13
| | | | | | | | | BUG=50866 TEST=Boot, log in, check that logging goes to /home/chronos/user/chrome_log. Crash the browser. After it comes back, verify that the browser process has created a new log file in /home/chronos/user and is writing to it. Review URL: http://codereview.chromium.org/3063014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@54854 0039d316-1c4b-4281-b951-d872f2087c98
* Make BrowserInit use FilePath instead of wstring for current directory.viettrungluu@chromium.org2010-08-031-1/+2
| | | | | | | | | | | (A.k.a. shaving a yak to get rid of a FromWStringHack().) BUG=24672 TEST=builds Review URL: http://codereview.chromium.org/3064032 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@54830 0039d316-1c4b-4281-b951-d872f2087c98
* Enable speculative preconnection by defaultjar@chromium.org2010-08-031-1/+6
| | | | | | | | | Added histogram to track utilization (vs waste). r=mbelshe Review URL: http://codereview.chromium.org/3026038 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@54771 0039d316-1c4b-4281-b951-d872f2087c98
* Fix the Windows build again.brettw@chromium.org2010-08-031-3/+7
| | | | | | | TEST=none BUG=none git-svn-id: svn://svn.chromium.org/chrome/trunk/src@54749 0039d316-1c4b-4281-b951-d872f2087c98
* Add #include utf_string_conversions.h to all files that use ASCIIToWide andbrettw@chromium.org2010-08-031-0/+1
| | | | | | | | | | | | | | | ASCIIToUTF16. I removed string_util includes from a few places where it obviously wasn't needed. In a separate pass, I'm going to remove ASCIITo* from string_util, then I'm going to do an even later pass to find the unnecessary string_util.h includes and remove them. TEST=it compiles BUG=none Review URL: http://codereview.chromium.org/3058027 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@54746 0039d316-1c4b-4281-b951-d872f2087c98
* [linux] Hook up crash reporter initialization with configuration management.mnissler@chromium.org2010-08-031-8/+24
| | | | | | | | | BUG=49662 TEST=Enable/Disable metrics reporting through policy and check whether the crash reporter respects that. Review URL: http://codereview.chromium.org/3084008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@54716 0039d316-1c4b-4281-b951-d872f2087c98
* A/B test for measuring effect of number of proxy connections.ziadh@chromium.org2010-08-021-0/+42
| | | | | | | | | | | | | | | | | Currently, we limit the number of connections per proxy server to 32 (raised from 15). Firefox uses 8. A low value keeps from overloading the proxy servers; at the same time, some users may hit the limit (since we use the same number for both HTTP and SOCKS proxies). This experiment selects a different number at browser launch (from the set [8, 16, 32, 64]), and attempts to look at certain stats to get a clearer picture of how this affects the user. BUG=44501 r=jar Review URL: http://codereview.chromium.org/3033045 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@54541 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-11-28 13:10:25 +0000