summaryrefslogtreecommitdiffstats
path: root/content/browser/browser_child_process_host_impl.cc
Commit message (Collapse)AuthorAgeFilesLines
* Remove kChildCleanExit since it's not used anymore.jam@chromium.org2014-03-281-3/+0
| | | | | | | | R=pkasting@chromium.org Review URL: https://codereview.chromium.org/217403002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@260304 0039d316-1c4b-4281-b951-d872f2087c98
* Refactor configuration of sandboxes - first stepsaberent@chromium.org2014-03-131-13/+0
| | | | | | | | | | | | | | | | | | See https://docs.google.com/document/d/1H-hCsIcMsAEP0fWHimbuiNA-Hc9eXEmR94eb-2RQAhA/edit?usp=sharing for background. This moves all process type dependent decisions on how to create Linux processes (not how to sandbox them once created, not Android) into the launch delegates and makes the arguments to the ChildProcessLauncher constructor and BrowserChildProcessHostImpl::Launch OS independent. BUG=none Review URL: https://codereview.chromium.org/177863002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@256802 0039d316-1c4b-4281-b951-d872f2087c98
* Let DCHECK in non-official-release build be opt-in with dcheck_always_on=1 onlywangxianzhu@chromium.org2014-03-101-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | - Remove DCHECK in non-official-release build by default - Gyp variable dcheck_always_on=1 (existing) forces to enable DCHECK in release build - Remove flag --enable-dcheck Other effects/notes: - Now allow "buildtype=Official dcheck_always_on=1" (which will enable DCHECK in official build) combination. - Gyp variable logging_like_official_build no longer has an effect - Leave DCHECK_IS_ON() unchanged. May deal with it in a later change if needed. This won't affect bots which use dcheck_always_on=1. BUG=350462 TEST=LoggingTest.Dcheck R=thakis@chromium.org TBR=darin,sehr (command line changes in components/nacl and mojo) Review URL: https://codereview.chromium.org/189603007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255987 0039d316-1c4b-4281-b951-d872f2087c98
* Creates a way to launch the utility process with elevated privileges on ↵haven@chromium.org2014-02-111-0/+7
| | | | | | | | | | | | Windows systems for the rare operations that require administrator access. IPCs to the utility process will be filtered when it is running elevated. BUG=331881 Review URL: https://codereview.chromium.org/98603007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@250409 0039d316-1c4b-4281-b951-d872f2087c98
* Allow multiple NaCl modules to be debugged.bradnelson@google.com2014-01-101-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | Assigning the first NaCl module to load to port 4014, allowing other to be dynamic, using a code path currently used for testing. Expose the port used by each module in the Task Manager UI to make it available to users debugging NaCl modules. Follow on changes will add extension api fields to make debuggable modules discoverable to a web based debugger. NOTE: The debug stub port on windows is opened at a different layer (inside nacl, only availabled with --disable-sandbox). This will be exposed in a follow on change. Reviewers: yoshiki@chromium.org (for task_manager) pkasting@chromium.org (for browser/ui) brettw@chromium.org (for content) noelallen@chromium.org (for nacl) BUG=328714 TEST=trybots R=yoshiki@chromium.org,pkasting@chromium.org,brettw@chromium.org,noelallen@chromium.org Review URL: https://codereview.chromium.org/102073008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@244041 0039d316-1c4b-4281-b951-d872f2087c98
* Convert string16 to base::string16 in content.brettw@chromium.org2013-12-031-1/+1
| | | | | | | | BUG= Review URL: https://codereview.chromium.org/102593002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@238447 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 230968 "Use HighResNow whenever possible on Windows."scottmg@chromium.org2013-10-251-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | Speculative revert. Appears to be causing problems on webgl gpu bots (unsure of root cause), and possible some XP test bots (TimeTicks::Now non-monotonic). TBR=awong@chromium.org, kbr@chromium.org, simonjam@chromium.org BUG=311646 > Use HighResNow whenever possible on Windows. > > This has been enabled on Canary channel for sometime now and seems to be > safe there. We also now have data from stable channel showing there are > no unexpectedly buggy CPUs out there. This should be safe to turn on for > all users with adequate CPUs, which is the majority of them. > > BUG=158234 > > Review URL: https://codereview.chromium.org/41953002 TBR=simonjam@chromium.org Review URL: https://codereview.chromium.org/45783003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@231152 0039d316-1c4b-4281-b951-d872f2087c98
* Use HighResNow whenever possible on Windows.simonjam@chromium.org2013-10-251-3/+0
| | | | | | | | | | | | | This has been enabled on Canary channel for sometime now and seems to be safe there. We also now have data from stable channel showing there are no unexpectedly buggy CPUs out there. This should be safe to turn on for all users with adequate CPUs, which is the majority of them. BUG=158234 Review URL: https://codereview.chromium.org/41953002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@230968 0039d316-1c4b-4281-b951-d872f2087c98
* Make BrowserMessageFilter not derive from IPC::ChannelProxy::MessageFilter. ↵jam@chromium.org2013-10-011-3/+7
| | | | | | | | | | This allows us to hide the OnMessageReceived which shouldn't be overridden from child classes, and also avoid the pattern of requiring an overridden method to have to call to the base class. R=scherkus@chromium.org, scherkus Review URL: https://codereview.chromium.org/24514003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@226251 0039d316-1c4b-4281-b951-d872f2087c98
* Enable high resolution time for TimeTicks::Now on Windows Canarysimonjam@chromium.org2013-09-101-0/+3
| | | | | | | | | | | | | | This should be unnoticeable, except for improved resolution in places such as window.performance.now(). The feature is enabled if the user is running Canary channel or has manually specified the --enable-high-resolution-time flag. This will only work if the CPU has a non-stop TSC and isn't a broken Athlon processor. UMA data show this is a safe combination. The flag is propagated to renderer processes so that they know to enable it too. BUG=158234 Review URL: https://chromiumcodereview.appspot.com/23147002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@222396 0039d316-1c4b-4281-b951-d872f2087c98
* Move AlterEnvironment to base/environment.h, implement on Windows. This ↵brettw@chromium.org2013-08-301-1/+1
| | | | | | | | | | | | | re-implements the Posix version to be more like the Windows version and to share some parsing code. The new version will be somewhat slower due to some extra mallocs, but is shorter and more clear. I didn't want to implement a super optimized version on Windows, and the alternative would be to keep the new Windows version and the old Posix version in parallel which seemed less desirable. This changes the input from a vector to a map and just adds the map on the LaunchOptions rather than requiring the caller to set a pointer. This cleans up the callsites somewhat. BUG= R=viettrungluu@chromium.org Review URL: https://codereview.chromium.org/22750002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@220608 0039d316-1c4b-4281-b951-d872f2087c98
* Fix getting exit status for browser child process.jln@chromium.org2013-08-271-3/+4
| | | | | | | | | | | | | | | | | | | | | | | | | This makes BrowserChildProcessHost::GetTerminationStatus() similar to RenderProcessHostImpl::GetChildTerminationStatus(). Linux requires waitpid() to block to get an exit status reliably. Otherwise the kernel is at liberty to not reap the process, even if it's already currently exiting or dead. If we know that a process is dead, we should make use of the known_dead argument to ChildProcessLauncher::GetChildTerminationStatus(), as does RenderProcessHostImpl::GetChildTerminationStatus(). A discussion of this tricky issue is available in crbug.com/157458 and the related CL. This will, among other things, fix NaCl's crash throttling security measure. BUG=274827,nativeclient:359 R=mseaborn@chromium.org, piman@chromium.org Review URL: https://codereview.chromium.org/23019012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@219814 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 217172 "Enable high resolution time for TimeTicks::Now on..."nhiroki@chromium.org2013-08-131-3/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | There is a suspicion that this might break some tests: MessageLoopTest.PostDelayedTask_InPostOrder_2, StatsTableTest.StatsCounterTimer TimeTicks.Deltas http://build.chromium.org/p/chromium.win/builders/XP%20Tests%20%282%29/builds/30128 http://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%281%29/builds/21737 > Enable high resolution time for TimeTicks::Now on Windows Canary > > This should be unnoticeable, except for improved resolution in places such as window.performance.now(). > > The feature is enabled if the user is running Canary channel or has manually specified the --enable-high-resolution-time flag. This will only work if the CPU has a non-stop TSC and isn't a broken Athlon processor. UMA data show this is a safe combination. > > The flag is propagated to renderer processes so that they know to enable it too. > > BUG=158234 > > Review URL: https://chromiumcodereview.appspot.com/16896018 TBR=simonjam@chromium.org Review URL: https://codereview.chromium.org/22984005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@217226 0039d316-1c4b-4281-b951-d872f2087c98
* Enable high resolution time for TimeTicks::Now on Windows Canarysimonjam@chromium.org2013-08-131-0/+3
| | | | | | | | | | | | | | This should be unnoticeable, except for improved resolution in places such as window.performance.now(). The feature is enabled if the user is running Canary channel or has manually specified the --enable-high-resolution-time flag. This will only work if the CPU has a non-stop TSC and isn't a broken Athlon processor. UMA data show this is a safe combination. The flag is propagated to renderer processes so that they know to enable it too. BUG=158234 Review URL: https://chromiumcodereview.appspot.com/16896018 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@217172 0039d316-1c4b-4281-b951-d872f2087c98
* Created multi-process-friendly PowerMonitor interface.bajones@chromium.org2013-08-021-1/+2
| | | | | | | | | | | | | 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
* Update include paths in content/browser for base/process changes.rsesek@chromium.org2013-07-231-1/+0
| | | | | | | | | 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
* Allow tracing to console everywhere.vollick@chromium.org2013-07-111-0/+1
| | | | | | | | | | | | This patch gets rid of the cc-only trace-to-vlog stuff and replaces it with a general trace-to-console approach that can be used everywhere, even the browser. BUG=None Review URL: https://chromiumcodereview.appspot.com/18174006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@211245 0039d316-1c4b-4281-b951-d872f2087c98
* Make utility process run in-process when running in single-process mode.jam@chromium.org2013-07-091-31/+33
| | | | | | | | | | | Remove the unit test/single process code path for SandboxedUnpacker as a first step. BUG=19192 R=asargent@chromium.org, scottmg@chromium.org Review URL: https://codereview.chromium.org/18119009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@210620 0039d316-1c4b-4281-b951-d872f2087c98
* Use a direct include of strings headers in content/browser/, part 1.avi@chromium.org2013-06-111-1/+1
| | | | | | | | | | BUG=247723 TEST=none TBR=ben@chromium.org Review URL: https://chromiumcodereview.appspot.com/16755004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@205449 0039d316-1c4b-4281-b951-d872f2087c98
* Lower the priority of shared workers that aren't associated with the ↵simonhatch@chromium.org2013-05-311-0/+4
| | | | | | | | | | | | | | | | | foreground tab. This should help out less powerful devices in the case where there's a shared worker in another tab and a cpu intensive page in the foreground. BUG= TEST=Open a doc, see webworker running, switch tabs and check webworker's priority by outputting contents of /sys/fs/cgroup/cpu/chrome_renderers/background/cgroup.proc on ChromeOS. With an open doc in a background tab, run 720p video (ie. youtube) at fullscreen, should stay fairly smooth. Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=199840 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=200932 Review URL: https://chromiumcodereview.appspot.com/14137016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@203272 0039d316-1c4b-4281-b951-d872f2087c98
* Move child-common classes to content/common_childjamesr@chromium.org2013-05-211-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | We need a place to put code that is shared between child processes of different types but not used in the browser process. For instance, the NPObject bindings code is used in the plugin and renderer processes but depends on WebBindings which the browser shouldn't depend on. Some web platform features require shared code between renderer and worker processe. The WebKit image decoders are used by worker, renderer and utility processes. This creates a content/common_child directory for code shared by more than one child process type. content/common_child can depend on content/common and all content/ subdirs except for content/browser and content/common can depend on it. The java bridge code is (more than a) bit busted since it pulls the NPObject bindings in to the browser, but since this code is only intended for use on android single-process configurations I've just created DEPS exceptions for this bit of code. BUG=241606 Review URL: https://chromiumcodereview.appspot.com/15047014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@201252 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 200932 "Lower the priority of shared workers that aren't ..."simonhatch@chromium.org2013-05-201-4/+0
| | | | | | | | | | | | | | | | | | | > Lower the priority of shared workers that aren't associated with the foreground tab. > > This should help out less powerful devices in the case where there's a shared worker in another tab and a cpu intensive page in the foreground. > > BUG= > TEST=Open a doc, see webworker running, switch tabs and check webworker's priority by outputting contents of /sys/fs/cgroup/cpu/chrome_renderers/background/cgroup.proc on ChromeOS. With an open doc in a background tab, run 720p video (ie. youtube) at fullscreen, should stay fairly smooth. > > Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=199840 > > Review URL: https://chromiumcodereview.appspot.com/14137016 TBR=simonhatch@chromium.org Review URL: https://codereview.chromium.org/15465006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@201090 0039d316-1c4b-4281-b951-d872f2087c98
* Lower the priority of shared workers that aren't associated with the ↵simonhatch@chromium.org2013-05-181-0/+4
| | | | | | | | | | | | | | | foreground tab. This should help out less powerful devices in the case where there's a shared worker in another tab and a cpu intensive page in the foreground. BUG= TEST=Open a doc, see webworker running, switch tabs and check webworker's priority by outputting contents of /sys/fs/cgroup/cpu/chrome_renderers/background/cgroup.proc on ChromeOS. With an open doc in a background tab, run 720p video (ie. youtube) at fullscreen, should stay fairly smooth. Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=199840 Review URL: https://chromiumcodereview.appspot.com/14137016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@200932 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 199840 "Lower the priority of shared workers that aren't ..."simonhatch@chromium.org2013-05-131-4/+0
| | | | | | | | | | | | | | | | | > Lower the priority of shared workers that aren't associated with the foreground tab. > > This should help out less powerful devices in the case where there's a shared worker in another tab and a cpu intensive page in the foreground. > > BUG= > TEST=Open a doc, see webworker running, switch tabs and check webworker's priority by outputting contents of /sys/fs/cgroup/cpu/chrome_renderers/background/cgroup.proc on ChromeOS. With an open doc in a background tab, run 720p video (ie. youtube) at fullscreen, should stay fairly smooth. > > Review URL: https://chromiumcodereview.appspot.com/14137016 TBR=simonhatch@chromium.org Review URL: https://codereview.chromium.org/15012025 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@199847 0039d316-1c4b-4281-b951-d872f2087c98
* Lower the priority of shared workers that aren't associated with the ↵simonhatch@chromium.org2013-05-131-0/+4
| | | | | | | | | | | | | foreground tab. This should help out less powerful devices in the case where there's a shared worker in another tab and a cpu intensive page in the foreground. BUG= TEST=Open a doc, see webworker running, switch tabs and check webworker's priority by outputting contents of /sys/fs/cgroup/cpu/chrome_renderers/background/cgroup.proc on ChromeOS. With an open doc in a background tab, run 720p video (ie. youtube) at fullscreen, should stay fairly smooth. Review URL: https://chromiumcodereview.appspot.com/14137016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@199840 0039d316-1c4b-4281-b951-d872f2087c98
* Cleanup various bits of BrowserThreadImpl and PluginServiceImpl.thestig@chromium.org2013-04-241-3/+4
| | | | | | Review URL: https://chromiumcodereview.appspot.com/13896004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@195957 0039d316-1c4b-4281-b951-d872f2087c98
* Cleanup: Remove unnecessary ".get()" from scoped_ptrs<>.erg@chromium.org2013-04-171-1/+1
| | | | | | | | | | | In r174057, ajwong@ added support for implicit testing to scoped_ptr<>. Removes these in content/. BUG=232084 Review URL: https://codereview.chromium.org/14081010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@194608 0039d316-1c4b-4281-b951-d872f2087c98
* Split the ProcessType enum into process types that content knows about ↵jam@chromium.org2013-03-221-13/+14
| | | | | | | | | | | (which will remain in src\content) and those that are for chrome (which moved to src\chrome). This way we won't get any more layering violations where nacl code is in content. Also move the NaCl command line switches to chrome. BUG=191682 Review URL: https://codereview.chromium.org/12662019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@189763 0039d316-1c4b-4281-b951-d872f2087c98
* Refactor sandbox_policy.cc so that it doesn't contain the sandbox policies ↵jam@chromium.org2013-03-201-5/+5
| | | | | | | | | | | | | | | | | | | | for all processes. Instead have whoever creates a sandboxed process set this data. This allows us to clean a few NaCl related changes in content: -remove NaCl sandbox rules from content -remove the hack for ifdef'ing out the GPU policy since it didn't link for nacl64.exe -remove the 1GB memory reservation for the NaCl loader process out of content Other cleanup: -renamed sandbox_policy.* to sandbox_win.* to match the other platform-specific sandbox files -moved BrokerGetFileHandleForProcess to internal content files since it's not called from outside -remove AddGpuDllEvictionPolicy since it was redundant (the one dll it removed was already listed in the generic list) There's still more cleanup to be done in the sandbox code (i.e. remove chrome frame switch, nacl process type switch etc). I will do that in future changes. BUG=191682 Review URL: https://codereview.chromium.org/12805004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@189175 0039d316-1c4b-4281-b951-d872f2087c98
* Windows: BrowserChildProcessHostImpl reports OnProcessCrashed if the child ↵apatrick@chromium.org2013-03-061-0/+48
| | | | | | | | | | | | | | | | process crashes before connecting the IPC channel. When a child process crashes, this is generally detected by an error on the IPC channel, i.e. OnChannelError being called. However, if the child process exits or crashes before this IPC channel has been established, the crash is lost. The browser process sees the child process being launched but never learns of its termination. This patch uses a WaitableEventWatcher to track the lifetime of the child process up to the point the IPC channel is connected. If the child process crashes in the interim, the usual OnProcessCrashed handler is invoked. This is important for the GPU child process because it is prone to crashing before the IPC channel is established; it has to initialize Direct3D before the sandbox is turned on. This would lead to a browser hang if Direct3D or the driver crashed during initialization. BUG=177611 Review URL: https://chromiumcodereview.appspot.com/12374061 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186498 0039d316-1c4b-4281-b951-d872f2087c98
* content: convert child process notifications to observer usagephajdan.jr@chromium.org2013-02-281-19/+45
| | | | | | | | BUG=170921 Review URL: https://codereview.chromium.org/12212089 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@185337 0039d316-1c4b-4281-b951-d872f2087c98
* Move file_path.h to base/files.brettw@chromium.org2013-02-241-2/+2
| | | | | | TBR=sky git-svn-id: svn://svn.chromium.org/chrome/trunk/src@184344 0039d316-1c4b-4281-b951-d872f2087c98
* Use base namespace for FilePath in content/browserbrettw@chromium.org2013-02-071-1/+1
| | | | | | Review URL: https://codereview.chromium.org/12213066 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@181349 0039d316-1c4b-4281-b951-d872f2087c98
* Move tracing code in content\browser to content\browser\tracing now that ↵jam@chromium.org2013-02-011-1/+1
| | | | | | | | | there's a separate directory. BUG=169170 Review URL: https://codereview.chromium.org/12149003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@180071 0039d316-1c4b-4281-b951-d872f2087c98
* Linux: inform the Zygote when it's waiting on a dead processjln@chromium.org2012-12-061-1/+2
| | | | | | | | | | | | | | | | | If the browser calls ProcessDied() and asks the Zygote to wait (without blocking) on a dead process, the kernel might not be done destroying it and the Zygote may mistakenly claim that the process is alive. We now inform the Zygote over the IPC that the process is already dead so that it can wait synchroneously. BUG=157458 NOTRY=true Review URL: https://chromiumcodereview.appspot.com/11316261 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@171450 0039d316-1c4b-4281-b951-d872f2087c98
* Add content/browser/loader/ for resource loading related classes.darin@chromium.org2012-12-051-1/+1
| | | | | | | | | | | This infrastructure is shared by both renderer and worker processes, so having it live in renderer_host/ was not quite right. This change also nicely reduces the number of files in renderer_host/. R=jam@chromium.org Review URL: https://codereview.chromium.org/11414299 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@171194 0039d316-1c4b-4281-b951-d872f2087c98
* Because of UID isolation on Android, crash dump generation has to happenjcivelli@chromium.org2012-10-241-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | in-process for renderers as well (as the browser cannot access all the necessary states of the renderer process). Breakpad has support for generating minidumps to a passed FD (as the renderer process on Android does not have permission to create file), so the flow on Android is: - when a render process is created the browser creates a file and passes its FD to the process - the renderer process initializes Breakpad with that FD - if there is a crash, Breakpad generates the minidump to that FD. - when the browser process detects a renderer stopped it checks the minidump file. If it's empty it deletes the file. If it's not empty, it means there was a crasher in which case it moves it to the crash dump folder for it to be picked up and uploaded by the Java side. BUG=None TEST=Test that minidumps are generated and uploaded when visiting about:crash and about:crashbrowserforrealz on Android and desktop Chrome. Review URL: https://chromiumcodereview.appspot.com/11189068 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@163917 0039d316-1c4b-4281-b951-d872f2087c98
* Move the remaning files in content\common to the content namespace.jam@chromium.org2012-10-241-25/+18
| | | | | | Review URL: https://codereview.chromium.org/11235068 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@163732 0039d316-1c4b-4281-b951-d872f2087c98
* Logging: pass logging related cmd line options to utility processqiankun.miao@intel.com2012-10-181-2/+13
| | | | | | | | | | | | | | | Logging doesn't work in utility process due to the related command line options are not passed to utility process. For example, run " ./chrome --vmodule=unpacker=1 --enable-logging=stderr", DVLOG(1) message in unpacker.cc can not be output correctly. This patch passes the related command line options to utility process. BUG= TEST=--enable-logging=stderr --vmodule=unpacker=1, then open chrome://extensions, drag a foo.crx in the page, you can see the DVLOG message " Installing extension ". Review URL: https://chromiumcodereview.appspot.com/11103028 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@162665 0039d316-1c4b-4281-b951-d872f2087c98
* On Posix, make all child processes quit when the browser dies, not just the ↵jam@chromium.org2012-07-301-0/+5
| | | | | | | | | | | renderers. On bots, seeing that sometimes child processes are hanging around after the browser process is gone. This confuses the sharding scripts. BUG=90448 Review URL: https://chromiumcodereview.appspot.com/10834068 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@149023 0039d316-1c4b-4281-b951-d872f2087c98
* Histograms - Support histograms for Plugins, GPUrtenneti@google.com2012-07-121-0/+2
| | | | | | | | | | | | | | and all child processes. Renderer processes also use this new method to send histograms to browser. This code is similar to the code that gets profiler data from all processes. R=jar@chromium.org,jam@chromium.org TEST=browser unit tests, interactive UI tests BUG=114013 Review URL: https://chromiumcodereview.appspot.com/10454086 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@146394 0039d316-1c4b-4281-b951-d872f2087c98
* Remove the code to wait on disconnected child processes to get the exit ↵jam@chromium.org2012-07-091-70/+5
| | | | | | | | code. This was done in r101435 to fix a problem where we were seeing processes "quit" but the result code wasn't ready. It looks like r68831 caused this, since it made the channel be disconnected before the process exits. Review URL: https://chromiumcodereview.appspot.com/10702048 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@145676 0039d316-1c4b-4281-b951-d872f2087c98
* Small cleanup in BrowserChildProcessHost. ↵jam@chromium.org2012-06-191-7/+0
| | | | | | | | ChildProcessHostDelegate::ShutdownStarted isn't called. Review URL: https://chromiumcodereview.appspot.com/10559047 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@142989 0039d316-1c4b-4281-b951-d872f2087c98
* [UMA] Use proper C++ objects to serialize tracked_objects across process ↵isherman@chromium.org2012-04-131-1/+1
| | | | | | | | | | | | | | | boundaries. See https://chromiumcodereview.appspot.com/9702014/ for the original code review. Uploading to a new issue due to an AppEngine error... BUG=103480 TEST=none (refactoring, no functional change expected) TBR=jam@chromium.org,jar@chromium.org,eroman@chromium.org,jhawkins@chromium.org,ajwong@chromium.org Review URL: http://codereview.chromium.org/10077001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@132109 0039d316-1c4b-4281-b951-d872f2087c98
* Aura: Show dialog box asking user's permisssion for screen sharing for gtalkvarunjain@chromium.org2012-03-201-0/+1
| | | | | | | | | | | | video plugin. BUG=111282 TEST=manual Review URL: http://codereview.chromium.org/9683003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@127638 0039d316-1c4b-4281-b951-d872f2087c98
* Delete HostDelegate objects instead of HostImpl objects to avoid leaking the ↵fischman@chromium.org2012-03-061-1/+4
| | | | | | | | | | | former. BUG=116744 Review URL: http://codereview.chromium.org/9553003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@125105 0039d316-1c4b-4281-b951-d872f2087c98
* Remove mach_broker_mac.h dependency from chrome.jam@chromium.org2012-02-291-0/+8
| | | | | | | BUG=98716 Review URL: https://chromiumcodereview.appspot.com/9557002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@124290 0039d316-1c4b-4281-b951-d872f2087c98
* Cleanup: Remove base::environment_vector and ↵thestig@chromium.org2012-02-241-3/+1
| | | | | | | | | | | base::file_handle_mapping_vector to StudlyCaps. BUG=none TEST=none Review URL: http://codereview.chromium.org/9429039 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@123438 0039d316-1c4b-4281-b951-d872f2087c98
* A few clients of the utility process had a race condition that could lead to ↵dgrogan@chromium.org2012-01-271-0/+1
| | | | | | | | | | | | | | a browser crash if the utility process crashed. IndexedDB was the worst offender. WebstoreInstallHelper, the profile importer, and posix plugin loader were also affected. As a side effect, NaClProcessHost and GpuProcessHost are now notified when their respective processes are killed and treat such an occurrence as a crash. BUG=108871 TEST= Review URL: http://codereview.chromium.org/9235052 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@119340 0039d316-1c4b-4281-b951-d872f2087c98
* Convert use of int ms to TimeDelta in files owned by brettw.tedvessenes@gmail.com2012-01-271-3/+4
| | | | | | | | | | BUG=108171 TEST= Review URL: http://codereview.chromium.org/9233018 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@119321 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-03-21 18:43:06 +0000