summaryrefslogtreecommitdiffstats
path: root/chrome/browser/process_info_snapshot_mac_unittest.cc
Commit message (Collapse)AuthorAgeFilesLines
* Cleanup: Remove base::environment_vector and ↵thestig@chromium.org2012-02-241-2/+2
| | | | | | | | | | | 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
* Change base::LaunchProcess API slightlyevan@chromium.org2011-07-151-2/+1
| | | | | | | | | | | Rather than passing the out param process handle via the options, take it as a function argument. This simplifies many callers. BUG=88990 Review URL: http://codereview.chromium.org/7377012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@92701 0039d316-1c4b-4281-b951-d872f2087c98
* Clean up users of a deprecated base::LaunchApp API.evan@chromium.org2011-07-131-2/+5
| | | | | | | | BUG=88990 Review URL: http://codereview.chromium.org/7346017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@92393 0039d316-1c4b-4281-b951-d872f2087c98
* Revert "Clean up users of a deprecated base::LaunchApp API."evan@chromium.org2011-07-121-5/+2
| | | | | | This reverts commit r92240, ChromeOS failures. git-svn-id: svn://svn.chromium.org/chrome/trunk/src@92244 0039d316-1c4b-4281-b951-d872f2087c98
* Clean up users of a deprecated base::LaunchApp API.evan@chromium.org2011-07-121-2/+5
| | | | | | | | BUG=88990 Review URL: http://codereview.chromium.org/7346017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@92240 0039d316-1c4b-4281-b951-d872f2087c98
* Use /usr/bin/top in about:memorysail@chromium.org2011-01-121-3/+29
| | | | | | | | | | | | | | | | | Currently we get memory information for about:memory using /bin/ps. Unfortuantely ps doesn't give us information about shared and private memory. Also, it's total virtual memory value doesn't match Activity Monitor's. This change adds code to get memory information using /usr/bin/top. The new code falls back to ps if there's a parsing error. Once about:memory displays all the information we need there are still a couple of things left to do: - refactor ProcessInfoSnapshot to use ProcessMetrics where possible - do a better job of detecting shared objects between our child processes and show it some how BUG=25454 TEST=Opened about:memory and verified that the values matched those in Activity Monitor. Tested on both 10.6 and 10.5. Review URL: http://codereview.chromium.org/6052005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@71114 0039d316-1c4b-4281-b951-d872f2087c98
* Mac: Add unit test for effective vs real user IDsail@chromium.org2010-12-231-0/+25
| | | | | | | | | | | This adds a test to make sure that we're getting the real effective and real user IDs in ProcessInfoSnapshot. BUG=None TEST=Ran the unit test and verified that it passed. Review URL: http://codereview.chromium.org/5999007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@70073 0039d316-1c4b-4281-b951-d872f2087c98
* Mac: Implement about:memory.viettrungluu@chromium.org2009-11-051-0/+85
This implements about:memory on Mac. It calls /bin/ps to obtain information about processes (this is Apple's officially supported "API"). Unfortunately, ps provides fairly minimal information (rss and vsize); top is better, but not a stable API -- it has changed greatly between Mac OS 10.5 and 10.6, and moreover the 10.6 version is more limited in its output formatting. BUG=9653 TEST=Go to about:memory under a variety of conditions (with a variety of browsers loaded). Review URL: http://codereview.chromium.org/333008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@31168 0039d316-1c4b-4281-b951-d872f2087c98