summaryrefslogtreecommitdiffstats
path: root/content/browser/browser_main_loop.cc
Commit message (Collapse)AuthorAgeFilesLines
...
* Revert 245131 "Add the UI compositor to the Mac build", which caused Mac ↵glider@chromium.org2014-01-161-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | ASan redness > Add the UI compositor to the Mac build > > Move the bulk of the files in content/browser/aura to > content/browser/compositor, since they're not aura-specific. > > Build all of those files in the Mac build, and add ui/compositor > to the dependencies of the Mac build. These files will soon only > be excluded from the Android build. > > BUG=314190 > > Review URL: https://codereview.chromium.org/137893007 TBR=ccameron@chromium.org BUG=335083 Review URL: https://codereview.chromium.org/137853019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245195 0039d316-1c4b-4281-b951-d872f2087c98
* Add the UI compositor to the Mac buildccameron@chromium.org2014-01-161-1/+1
| | | | | | | | | | | | | | | Move the bulk of the files in content/browser/aura to content/browser/compositor, since they're not aura-specific. Build all of those files in the Mac build, and add ui/compositor to the dependencies of the Mac build. These files will soon only be excluded from the Android build. BUG=314190 Review URL: https://codereview.chromium.org/137893007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245131 0039d316-1c4b-4281-b951-d872f2087c98
* Remove vestigal traces of the TLS Cached Info Extension supportrsleevi@chromium.org2014-01-111-3/+0
| | | | | | | | | | | | | Chrome no longer carries the patch to NSS to enable this support; remove the traces that exist in Chrome to support it. BUG=none R=wtc TBR=brettw Review URL: https://codereview.chromium.org/122573004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@244285 0039d316-1c4b-4281-b951-d872f2087c98
* linux_aura: Work around a bug in the KDE Oxygen theme.erg@chromium.org2014-01-071-0/+2
| | | | | | | | BUG=329991 Review URL: https://codereview.chromium.org/105273014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243253 0039d316-1c4b-4281-b951-d872f2087c98
* MessageLoop(TYPE_UI) -> MessageLoopForUIsky@chromium.org2013-12-191-1/+1
| | | | | | | | | | | | | | | Converts creation of MessageLoopForUI from MessageLoop(TYPE_UI) to MessageLoopForUI. This is a step in the direction of moving type out of MessageLoop. BUG=none TEST=none R=darin@chromium.org Review URL: https://codereview.chromium.org/108713004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@241917 0039d316-1c4b-4281-b951-d872f2087c98
* Plumb AudioLog support into AudioManager.dalecurtis@chromium.org2013-12-041-1/+3
| | | | | | | | | | | | | | | | AudioManager is now also an AudioLogFactory. Changing the constructor of AudioManager isn't viable due to its psuedo-singleton behavior, so MediaInternal's AudioLogFactory must be injected after construction. The next step after this CL is to have AudioOutputDispatcherImpl objects own an AudioLog instance. BUG=260005 TEST=none, just plumbing. Review URL: https://codereview.chromium.org/99733004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@238637 0039d316-1c4b-4281-b951-d872f2087c98
* Relanding 236651: https://codereview.chromium.org/77123002oshima@chromium.org2013-11-221-7/+10
| | | | | | | | | | | | | | Linux: initialize RenderSandboxHostLinux before threads are started. A few tests in browser_tests seems to be relying on TestSuite in base/test/test_suite.cc, which is calling gtk_init. Instead of fixing gtk config, I simply skipped DCHECK on TOOLKIT_GTK as this config will be obsolete soon. BUG=321388 R=creis@chromium.org, jln@chromium.org, kbr@chromium.org TBR=creis@chromium.org, jln@chromium.org, kbr@chromium.org Review URL: https://codereview.chromium.org/83813002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@236805 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 236651 "Linux: initialize RenderSandboxHostLinux before t..."vabr@chromium.org2013-11-221-10/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | This change seems to break some browser_tests on linux debug. Some examples are in the trybot results at the original CL, including some PnaclHeaderTests, locally I saw it break DeclarativeApiTest.DeclarativeApi. Look for "FATAL:render_sandbox_host_linux.cc(712)] Check failed: 1 == base::GetNumberOfThreads(base::GetCurrentProcessHandle()) (1 vs. 2)" in the output. > Linux: initialize RenderSandboxHostLinux before threads are started. > > RenderSandboxHostLinux::Init() uses fork(). Therefore the process needs > to only have one thread when this is called. > > Move RenderSandboxHostLinux early enough that on one thread exists. > > BUG=321388 > R=creis@chromium.org, kbr@chromium.org, oshima@chromium.org > > Review URL: https://codereview.chromium.org/77123002 TBR=jln@chromium.org Review URL: https://codereview.chromium.org/82743002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@236693 0039d316-1c4b-4281-b951-d872f2087c98
* Linux: initialize RenderSandboxHostLinux before threads are started.jln@chromium.org2013-11-221-7/+10
| | | | | | | | | | | | | | RenderSandboxHostLinux::Init() uses fork(). Therefore the process needs to only have one thread when this is called. Move RenderSandboxHostLinux early enough that on one thread exists. BUG=321388 R=creis@chromium.org, kbr@chromium.org, oshima@chromium.org Review URL: https://codereview.chromium.org/77123002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@236651 0039d316-1c4b-4281-b951-d872f2087c98
* Support use_glib==0 in contentspang@chromium.org2013-11-211-3/+3
| | | | | | | | | | There's no need to add a log handler if we're not using glib. BUG=318315, 318413, 170408 Review URL: https://codereview.chromium.org/77673006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@236432 0039d316-1c4b-4281-b951-d872f2087c98
* Use TracingController for startup tracingwangxianzhu@chromium.org2013-11-211-5/+45
| | | | | | | | | | | This CL depends on https://codereview.chromium.org/66893003/ (which allows customized trace data file) and https://codereview.chromium.org/66193005/ (which removes TraceLog enable counting). BUG=none R=cdn@chromium.org, nduca@chromium.org, piman@chromium.org Review URL: https://codereview.chromium.org/65343006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@236362 0039d316-1c4b-4281-b951-d872f2087c98
* Make it possible to disable udev in the content API on linuxmostynb@opera.com2013-11-201-3/+3
| | | | | | | | | | | | This is useful for embedded linux setups, which often don't include udev support. TEST=Build content_shell on linux with use_udev=0 then run ldd on output binaries to verify libudev is not listed (and is listed if built with use_udev=1 or unspecified) BUG=318315,318413 Review URL: https://codereview.chromium.org/12374068 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@236204 0039d316-1c4b-4281-b951-d872f2087c98
* Introduce RenderProcessHostObserver, use it in its first client.avi@chromium.org2013-11-191-4/+3
| | | | | | | | | BUG=170921 TEST=everything still works Review URL: https://codereview.chromium.org/72203003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@235877 0039d316-1c4b-4281-b951-d872f2087c98
* Have Blink be told of scrollbar changes rather than paying attention itself ↵avi@chromium.org2013-11-081-0/+8
| | | | | | | | | | | (Chromium side). BUG=306348 TEST=no visible change; scrollbar changes still work Review URL: https://codereview.chromium.org/63203003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@233826 0039d316-1c4b-4281-b951-d872f2087c98
* Move Gtk initialization earlier in BrowserMain.kbr@chromium.org2013-10-231-19/+24
| | | | | | | | | | | | | In order to work around bugs in glib, it must be initialized before any threads are started in the process. If this is not done then the process will intermittently hang upon exit. BUG=309093 R=erg@chromium.org, jorgelo@chromium.org, sky@chromium.org Review URL: https://codereview.chromium.org/34463007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@230547 0039d316-1c4b-4281-b951-d872f2087c98
* Allow asynchronous GPU context creation for browser clientssievers@chromium.org2013-10-231-11/+21
| | | | | | | | | | | | | | | | | | This moves the call to establish a GPU channel out of WGC3D. It adds an asynchronous method to BrowserGpuChannelHostFactory that registers callbacks that are run on the main thread once the channel is established. This is prerequisite work for asynchronous OutputSurface creation. BUG=270179,125248,235300 R=piman@chromium.org Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=228777 Review URL: https://codereview.chromium.org/26959002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@230261 0039d316-1c4b-4281-b951-d872f2087c98
* Revert r228777: "Allow asynchronous GPU context creation for browser clients"eroman@chromium.org2013-10-151-21/+11
| | | | | | | | | | | | | | | To see if it is responsible for browser_tests failures on Vista: GpuFeatureTest.MultisamplingBlocked GpuFeatureTest.WebGLBlocked GpuFeatureTest.Canvas2DBlocked TBR=sievers BUG=270179,125248,235300 Review URL: https://codereview.chromium.org/26571006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@228806 0039d316-1c4b-4281-b951-d872f2087c98
* Allow asynchronous GPU context creation for browser clientssievers@chromium.org2013-10-151-11/+21
| | | | | | | | | | | | | | | | This moves the call to establish a GPU channel out of WGC3D. It adds an asynchronous method to BrowserGpuChannelHostFactory that registers callbacks that are run on the main thread once the channel is established. This is prerequisite work for asynchronous OutputSurface creation. BUG=270179,125248,235300 R=piman@chromium.org Review URL: https://codereview.chromium.org/26959002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@228777 0039d316-1c4b-4281-b951-d872f2087c98
* When running in single-process mode, delete the one RenderProcessHost at ↵jam@chromium.org2013-10-151-1/+5
| | | | | | | | | | | shutdown. This ensures that we stop the renderer thread which would expose any crashes. BUG=301520 R=glider@chromium.org Review URL: https://codereview.chromium.org/27183007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@228757 0039d316-1c4b-4281-b951-d872f2087c98
* Add more support for FreeBSDGeo.Liaskos@gmail.com2013-09-211-3/+3
| | | | | | | | BUG= Review URL: https://chromiumcodereview.appspot.com/16206002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224546 0039d316-1c4b-4281-b951-d872f2087c98
* Chrome tracing for system-wide performance stats.jwmak@chromium.org2013-09-181-0/+7
| | | | | | | | | | | | Trace memory, swap, ZRAM, and disk activity and place the data in JSON to be displayed by trace-viewer. BUG=236763 TEST=base_unittests TraceSystemStatsMonitorTest.* Review URL: https://chromiumcodereview.appspot.com/22836004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@223806 0039d316-1c4b-4281-b951-d872f2087c98
* Adding shutdown tracing capabilitiesskuhne@chromium.org2013-09-061-29/+75
| | | | | | | | | | | | | | | use "--trace-shutdown" to enable the feature to start profiling when the user has pressed "shutdown" and specify "--trace-shutdown-file=<name>" to specify the file where you want to dump to. Additionally you can specify which modules to trace with e.g. "--trace-shutdown=base,net". That said: NOTE that the dumping will cost time since it has to be done after the shutdown of Chrome is finished. As such it takes time and will make it impossible to get a correct reading of time from shutdown till a new startup is finished. Note: This is similar to the trace-startup - with the exception that upon shutdown it is not possible to rely on threads for IO anymore. BUG=281524 TEST=visual tests Review URL: https://chromiumcodereview.appspot.com/23691025 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@221631 0039d316-1c4b-4281-b951-d872f2087c98
* Revert "Revert "Remove dependencies on /media for iOS.""bdibello@google.com2013-08-281-2/+1
| | | | | | | | | | | | This reverts commit 1f99bc28b47392ed97d03863460bc681d7f39a1a. /media was only needed for the old version of voice search on iOS. BUG=227855 Review URL: https://chromiumcodereview.appspot.com/18873009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@219867 0039d316-1c4b-4281-b951-d872f2087c98
* Allow overlapping sync and async startup requestsaberent@chromium.org2013-08-271-22/+39
| | | | | | | | | | | | | | | On Android we can get a second request to start the browser while the an asynchronous request is in progress. Since the second request may be synchronous, we may have switch to completing initialization synchronously. This patch handles this by tracking which initialization tasks have been run, and running the remaining initialization tasks. BUG=260574 Review URL: https://chromiumcodereview.appspot.com/22691002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@219795 0039d316-1c4b-4281-b951-d872f2087c98
* Implement inertial sensor service and shared memory data fetcher for device ↵timvolodine@chromium.org2013-08-221-2/+2
| | | | | | | | | | | | | | | | | | | | | motion/orientation. This CL modifies the existing structure by introducing a more general approach using enums for representing consumers of motion/orientation data. There is now a singleton service class which owns the shared memory data fetcher. The shared memory data fetcher takes care of updating the shared memory buffer with fresh sensor data. On some platforms like mac this needs a polling thread, on others like Android the data is pushed by the system. This logic is encapsulated inside the data fetcher, so there is now no need for a separate provider class. In particular this CL includes: - generalized inertial_sensor_service class with support for both motion/orientation consumers, - generalized data_fetcher_shared_memory_base class which takes care of initialization and polling if needed, - android data fetcher and default data fetcher (only for motion for now). - enums for orientation/motion, for optimal code reuse, - unittests for data_fetcher_shared_memory_base for both motion and orientation. BUG=261165,269559 Review URL: https://chromiumcodereview.appspot.com/21735007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@219007 0039d316-1c4b-4281-b951-d872f2087c98
* Correctly use IsThreadedCompositingEnabled in content_browsertestspiman@chromium.org2013-08-211-1/+1
| | | | | | | | | | | | | | Content-level defaults should be set direclty inside of content, not in chrome. Also remove redundant setting of WebPreferences::force_compositing_mode in ChromeContentBrowserClient - it's already set in WebContentsImpl::GetWebkitPrefs. This allows us to remove compositor_util.h from the public API. BUG=276561 Review URL: https://chromiumcodereview.appspot.com/22912014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@218619 0039d316-1c4b-4281-b951-d872f2087c98
* Add support for multiple asynchronous browser startups.nyquist@chromium.org2013-08-201-1/+1
| | | | | | | | | | | | | | | | | | | | | | | This CL adds support for easily doing multiple asynchronous startups where every startup request can get their own callback executed. This makes the logic in at the caller very simple by for example extracting away usage of AndroidBrowserProcess and catching ProcessInitException. BrowserStartupConfig is renamed to BrowserStartupController, since it now does more than just keep the configuration. The BrowserStartupController is called from native when the native startup is complete. It keeps an ordered list of caller's callbacks which will all be called when initialization is finished. If initialization has already been completed before the async startup request is called, the callback is called immediately. The first users of this are content shell and chromium testshell. BUG=260574 Review URL: https://chromiumcodereview.appspot.com/22272006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@218562 0039d316-1c4b-4281-b951-d872f2087c98
* Disable GPU process prelaunch if browser uses the software compositorjbauman@chromium.org2013-08-201-1/+6
| | | | | | | | | | If the browser is using the software compositor, then nothing will use the GPU, so it's pointless to prelaunch it. BUG=270172 Review URL: https://chromiumcodereview.appspot.com/22893019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@218456 0039d316-1c4b-4281-b951-d872f2087c98
* Adding key press detection in the browser process.jiayl@chromium.org2013-08-151-0/+9
| | | | | | | | | | | | | | | | | It works like this on the browser side: A new object UserInputMonitor is created on BrowserMainLoop and passed to AudioInputRendererHost to pass to AudioInputController. AudioInputController::DoRecord calls UserInputMonitor::AddKeyStrokeListener --> UserInputMonitor listens to system key events (only implemented on Linux) --> AudioInputController::OnKeyPressed is called and sets key_pressed_ --> When AudioInputController::OnData called, it writes key_pressed_ to shared memory along with the audio data buffer. On the renderer side a new param "key_pressed" is added through the code path of passing the flag to the webrtc voice engine. This CL includes all these changes except the implementation of UserInputMonitor for Windows and Mac. The impl of UserInputMonitor is mostly copied from remoting/host/local_input_monitor_linux.cc BUG= Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=217768 Review URL: https://chromiumcodereview.appspot.com/21183002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@217844 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 217768 "Adding key press detection in the browser process."phoglund@chromium.org2013-08-151-9/+0
| | | | | | | | | | | | | | | | | | | | > Adding key press detection in the browser process. > It works like this on the browser side: > A new object KeyPressMonitor is created on BrowserMainLoop and passed to AudioInputRendererHost to pass to AudioInputController. > AudioInputController::DoRecord calls KeyPressMonitor::AddKeyPressListener --> KeyPressMonitor listens to system key events through UserInputMonitor(only implemented on Linux) --> AudioInputController::OnKeyPressed is called and sets key_pressed_ --> When AudioInputController::OnData called, it writes key_pressed_ to shared memory along with the audio data buffer. > On the renderer side a new param "key_pressed" is added through the code path of passing the flag to the webrtc voice engine. > This CL includes all these changes except the implementation of UserInputMonitor for Windows and Mac. The impl of UserInputMonitor is mostly copied from remoting/host/local_input_monitor_linux.cc > > > BUG= > > Review URL: https://chromiumcodereview.appspot.com/21183002 TBR=jiayl@chromium.org Review URL: https://codereview.chromium.org/22871007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@217774 0039d316-1c4b-4281-b951-d872f2087c98
* Adding key press detection in the browser process.jiayl@chromium.org2013-08-151-0/+9
| | | | | | | | | | | | | | | It works like this on the browser side: A new object KeyPressMonitor is created on BrowserMainLoop and passed to AudioInputRendererHost to pass to AudioInputController. AudioInputController::DoRecord calls KeyPressMonitor::AddKeyPressListener --> KeyPressMonitor listens to system key events through UserInputMonitor(only implemented on Linux) --> AudioInputController::OnKeyPressed is called and sets key_pressed_ --> When AudioInputController::OnData called, it writes key_pressed_ to shared memory along with the audio data buffer. On the renderer side a new param "key_pressed" is added through the code path of passing the flag to the webrtc voice engine. This CL includes all these changes except the implementation of UserInputMonitor for Windows and Mac. The impl of UserInputMonitor is mostly copied from remoting/host/local_input_monitor_linux.cc BUG= Review URL: https://chromiumcodereview.appspot.com/21183002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@217768 0039d316-1c4b-4281-b951-d872f2087c98
* Linux: use sandbox binary alongside chrome.phajdan.jr@chromium.org2013-08-091-28/+36
| | | | | | | | | | | | | | | | | | | This removes linux_sandbox_path and instead expects sandbox binary to be in the same directory as chrome (or CHROME_DEVEL_SANDBOX to be set). This will be helpful for SxS support on Linux, where the sandbox path would be different depending on channel. This is a resubmit of https://codereview.chromium.org/20197003 with a bug fix that makes --no-sandbox work properly. TBR=jln@chromium.org BUG=38598 Review URL: https://codereview.chromium.org/22751007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@216746 0039d316-1c4b-4281-b951-d872f2087c98
* Created multi-process-friendly PowerMonitor interface.bajones@chromium.org2013-08-021-1/+4
| | | | | | | | | | | | | PowerMonitor status is now captured in the browser process, which has the appropriate UI thread, and then sent via IPC to other processes which are interested in the power state. BUG=236031 R=apatrick@chromium.org, jam@chromium.org, jar@chromium.org, jvoung@chromium.org, kbr@chromium.org, mpcomplete@chromium.org, palmer@chromium.org, piman@chromium.org, vandebo@chromium.org Review URL: https://codereview.chromium.org/17074009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@215381 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 215101 "Linux: use sandbox binary alongside chrome."tonyg@chromium.org2013-08-021-34/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | It breaks the page cycler benchmarks. BUG=267640 > Linux: use sandbox binary alongside chrome. > > This removes linux_sandbox_path and instead expects sandbox binary > to be in the same directory as chrome (or CHROME_DEVEL_SANDBOX to be > set). > > This will be helpful for SxS support on Linux, where the sandbox path > would be different depending on channel. > > BUG=38598 > R=avi@chromium.org, jln@chromium.org > > Review URL: https://codereview.chromium.org/20197003 TBR=phajdan.jr@chromium.org Review URL: https://codereview.chromium.org/21910004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@215300 0039d316-1c4b-4281-b951-d872f2087c98
* Linux: use sandbox binary alongside chrome.phajdan.jr@chromium.org2013-08-011-26/+34
| | | | | | | | | | | | | | | | This removes linux_sandbox_path and instead expects sandbox binary to be in the same directory as chrome (or CHROME_DEVEL_SANDBOX to be set). This will be helpful for SxS support on Linux, where the sandbox path would be different depending on channel. BUG=38598 R=avi@chromium.org, jln@chromium.org Review URL: https://codereview.chromium.org/20197003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@215101 0039d316-1c4b-4281-b951-d872f2087c98
* Run the later parts of startup as UI thread tasksaberent@chromium.org2013-08-011-13/+60
| | | | | | | | | | | | | | | This CL splits the later parts of startup, from thread creation onwards, into multiple UI thread tasks. Depending on the StartupTaskRunner passed to CreateThreads the tasks are all run immediately, or are queued one at a time on the UI thread. This, on platforms where the UI is already running, allows the UI to remain interactive while Chrome is initialized. BUG=231856 Review URL: https://chromiumcodereview.appspot.com/19957002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@215042 0039d316-1c4b-4281-b951-d872f2087c98
* Move and split up image_transport_factory files.danakj@chromium.org2013-07-291-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | The image_transport_factory.cc declares and defines 11 classes currently, which makes it incredibly hard to work on, or read and understand. This moves the files out from content/browser/renderer_host/ where they do not belong as they are serving the browser compositor. It moves the files to content/browser/aura/ (beside content/browser/android/) and splits them up into separate files for each class. There's a few classes left in gpu_process_image_factory.cc that can be split out afterward. This also splits the BrowserCompositorOutputSurfaceProxy off from the new RefCountedIDMap so that no class except the GpuProcessTransportFactory needs to know about the proxy, by passing the compositor thread message loop to the proxy directly. TBR=piman@chromium.org NOTRY=true BUG=258625 Review URL: https://codereview.chromium.org/20570003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@214213 0039d316-1c4b-4281-b951-d872f2087c98
* Record Chrome trace events in tcmalloc heap profilesjamescook@chromium.org2013-07-241-0/+14
| | | | | | | | | | | | | | | | | This allows about:tracing to show tcmalloc heap memory allocation over time. The implementation: * Adds a "memory" checkbox to about:tracing * Uses thread-local-storage to store the "stack" of trace events per thread while about:tracing is running. * Introduces a StackGeneratorFunction callback into tcmalloc, allowing it to call back into Chrome to get a "stack" of trace events. * Parses the heap profiler output of tcmalloc and converts it to JSON to be displayed by a visualizer in the about:tracing trace viewer. BUG=243895 TEST=base_unittests TraceMemoryTest.* Review URL: https://chromiumcodereview.appspot.com/15418002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@213473 0039d316-1c4b-4281-b951-d872f2087c98
* Update include paths in content/browser for base/process changes.rsesek@chromium.org2013-07-231-1/+1
| | | | | | | | | BUG=242290 TBR=sky@chromium.org Review URL: https://codereview.chromium.org/19495006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@213225 0039d316-1c4b-4281-b951-d872f2087c98
* Remove unused WEBKIT_DEPRECATED threadjamesr@chromium.org2013-07-191-31/+1
| | | | | | | | | BUG=237267, 234283 R=jam@chromium.org Review URL: https://codereview.chromium.org/18414007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212661 0039d316-1c4b-4281-b951-d872f2087c98
* Move Android data fetcher JNI registration to browser_jni_registrar.cc.timvolodine@chromium.org2013-07-191-5/+0
| | | | | | | | | | | - Renamed DataFetcherImplAndroid::Init() -> Register(). - Moved the Register() method call from browser_main_loop to browser_jni_registrar. BUG= Review URL: https://chromiumcodereview.appspot.com/18941005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212633 0039d316-1c4b-4281-b951-d872f2087c98
* Use a direct include of the message_loop header in content/, part 1.avi@chromium.org2013-07-181-1/+1
| | | | | | | | | | BUG=260807 TEST=none TBR=ben@chromium.org Review URL: https://chromiumcodereview.appspot.com/19532003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212206 0039d316-1c4b-4281-b951-d872f2087c98
* Simply use scoped_ptr::reset() to stop and delete threads.oshima@chromium.org2013-07-171-20/+9
| | | | | | | | | | | | | so that crash stack can tell in which thread the chrome received sigabort during shutdown. It looks to me that this was done for historical reason (r111705), but no longer necessary. BUG=258569 Review URL: https://chromiumcodereview.appspot.com/19379004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212070 0039d316-1c4b-4281-b951-d872f2087c98
* Revert "Remove dependencies on /media for iOS."blundell@chromium.org2013-07-121-1/+2
| | | | | | | | | | | | | This reverts commit 5acb0a7605d1eec9220e0b7b3b663967fcf1e5ce. We need to stop media_unittests running on the iOS simulator bot before we can safely reland this CL. TBR=bdibello Review URL: https://codereview.chromium.org/19002008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@211411 0039d316-1c4b-4281-b951-d872f2087c98
* Implement the content/renderer and content/browser part of the Device Motion ↵timvolodine@chromium.org2013-07-111-0/+2
| | | | | | | | | | | | | | | | | | API. This patch has a partial implementation of provider and does not include any device motion fetchers. The patch features: - chromium-side event pump - shared memory reader and buffer representation - IPC messages and filters for shared memory communication - service class to keep track of listening renderers BUG=135804 Review URL: https://chromiumcodereview.appspot.com/14678012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@211043 0039d316-1c4b-4281-b951-d872f2087c98
* Remove dependencies on /media for iOS.bdibello@google.com2013-07-101-2/+1
| | | | | | | | | | /media was only needed for the old version of voice search on iOS. BUG=227855 Review URL: https://chromiumcodereview.appspot.com/18777006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@210900 0039d316-1c4b-4281-b951-d872f2087c98
* Add additional startup trace events.nkostylev@chromium.org2013-07-041-1/+2
| | | | | | | | | | | | | * LoadAndDecodeWallpaper * ShowLoginWebUI * SetupSandbox BUG=257026 NOTRY=true Review URL: https://chromiumcodereview.appspot.com/18345013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@210156 0039d316-1c4b-4281-b951-d872f2087c98
* Move timing files into base/time and base/timer, install forwarding headers.avi@chromium.org2013-06-271-2/+2
| | | | | | | | | | BUG=254986 TEST=none TBR=brettw@chromium.org Review URL: https://codereview.chromium.org/18063004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@208951 0039d316-1c4b-4281-b951-d872f2087c98
* Move IndexedDB from WEBKIT_DEPRECATED to dedicated threadjsbell@chromium.org2013-06-251-0/+9
| | | | | | | | BUG=234279 Review URL: https://chromiumcodereview.appspot.com/17518004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@208544 0039d316-1c4b-4281-b951-d872f2087c98
* Linux: the lack of setuid sandbox is now fatal.jln@chromium.org2013-06-231-5/+13
| | | | | | | | | | | | | | | | | | --disable-setuid-sandbox needs to be passed on the command line for the setuid sandbox to be disabled. Because migrating existing bots and configurations takes time, there is an escape hatch as well: if the CHROME_DEVEL_SANDBOX environment variable is empty, we only log an error. chromium-dev announcement: http://goo.gl/yWwZn BUG=245376 R=markus@chromium.org, piman@chromium.org Review URL: https://codereview.chromium.org/16925003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@208133 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-03-21 23:18:56 +0000