summaryrefslogtreecommitdiffstats
path: root/chrome/test/memory_test
Commit message (Collapse)AuthorAgeFilesLines
* Move more files from chrome/test to chrome/test/base, part #7phajdan.jr@chromium.org2011-08-041-512/+0
| | | | | | | | | | Move all performance tests under chrome/test/perf. This also gets rid of directories containing only 1-2 files. BUG=90905 Review URL: http://codereview.chromium.org/7578004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@95481 0039d316-1c4b-4281-b951-d872f2087c98
* Move more files from chrome/test to chrome/test/base, part #4phajdan.jr@chromium.org2011-08-011-1/+1
| | | | | | | BUG=90905 Review URL: http://codereview.chromium.org/7544021 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@94963 0039d316-1c4b-4281-b951-d872f2087c98
* Fix TODO(evanm) about only having ui_test.h forward declare AutomationProxy.darin@chromium.org2011-06-271-0/+1
| | | | | | | | R=evan@chromium.org Review URL: http://codereview.chromium.org/7243011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@90666 0039d316-1c4b-4281-b951-d872f2087c98
* Support Chromium-branded builds and cleanup reference build usage.jrt@chromium.org2011-06-231-42/+14
| | | | | | | | | | Implemented cmp's POC (http://codereview.chromium.org/7171005/) and enforced the usage of UIPerfTest::UseReferenceBuild(). Review URL: http://codereview.chromium.org/7185023 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@90141 0039d316-1c4b-4281-b951-d872f2087c98
* Browser::Type cleanup.jianli@chromium.org2011-05-051-2/+2
| | | | | | | | | | BUG=None TEST=Existing tests R=ben@chromium.org,stevenjb@chromium.org,phajdan.jr@chromium.org Review URL: http://codereview.chromium.org/6697032 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@84303 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 83070 - Resubmit GPU memory test after updating DEPS to pull in ↵hnguyen@chromium.org2011-04-261-111/+13
| | | | | | | | | latest test data.Previous review: http://codereview.chromium.org/6676002/Review URL: http://codereview.chromium.org/6854024 TBR=hnguyen@chromium.org Review URL: http://codereview.chromium.org/6902053 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@83101 0039d316-1c4b-4281-b951-d872f2087c98
* Resubmit GPU memory test after updating DEPS to pull in latest test data.hnguyen@chromium.org2011-04-261-13/+111
| | | | | | | Previous review: http://codereview.chromium.org/6676002/ Review URL: http://codereview.chromium.org/6854024 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@83070 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 81353 - Adding memory test for GPU.Review URL: ↵nick@chromium.org2011-04-131-112/+13
| | | | | | | | | | | http://codereview.chromium.org/6676002 [ Reason for revert: these new tests fail on the bots in what looks like a possible state-carryover problem: http://build.chromium.org/p/chromium.perf/builders/Vista%20Perf%20%28jank%29/builds/2020/steps/memory_test/logs/stdio ] TBR=hnguyen@chromium.org Review URL: http://codereview.chromium.org/6834038 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@81452 0039d316-1c4b-4281-b951-d872f2087c98
* Adding memory test for GPU.hnguyen@chromium.org2011-04-131-13/+112
| | | | | | Review URL: http://codereview.chromium.org/6676002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@81353 0039d316-1c4b-4281-b951-d872f2087c98
* Move platform_thread to base/threading and put in the base namespace. I left abrettw@chromium.org2010-12-311-3/+4
| | | | | | | | | | | stub and "using" declarations in the old location to avoid having to change the entire project at once. TEST=it compiles BUG=none Review URL: http://codereview.chromium.org/6001010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@70342 0039d316-1c4b-4281-b951-d872f2087c98
* Remove FLAKY tag from memory tests.vandebo@chromium.org2010-10-201-14/+2
| | | | | | | | | | | These tests are no longer flaky. Likely fixed by http://crrev.com/63104 BUG=59335 TEST=Green bots - no longer repros. Review URL: http://codereview.chromium.org/3968002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@63288 0039d316-1c4b-4281-b951-d872f2087c98
* Convert LOG(INFO) to VLOG(1) - chrome/test/.pkasting@chromium.org2010-10-201-3/+3
| | | | | | | | | | Also fix indentation, remove a few unnecessary endls, collapse some append()s into +s, and remove a few extra {}s. BUG=none TEST=none Review URL: http://codereview.chromium.org/3915004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@63253 0039d316-1c4b-4281-b951-d872f2087c98
* Marking GeneralMixMemoryTest.FiveTabTest flaky on Win bottyoshino@chromium.org2010-10-181-1/+7
| | | | | | | | | | R=yutak BUG=59335 TEST=none Review URL: http://codereview.chromium.org/3781013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@62909 0039d316-1c4b-4281-b951-d872f2087c98
* Mark GeneralMixMemoryTest.TwelveTabTest flaky only on win bottyoshino@chromium.org2010-10-151-1/+7
| | | | | | | | | | R=hayato BUG=59335 TEST=none Review URL: http://codereview.chromium.org/3744014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@62727 0039d316-1c4b-4281-b951-d872f2087c98
* GTTF: Uncrashy memory_test.phajdan.jr@chromium.org2010-08-301-4/+9
| | | | | | | | | | | | | It's still going to fail randomly, but at least shouldn't crrrrrash. TBR=huanr BUG=53882 TEST=memory_test Review URL: http://codereview.chromium.org/3248005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@57926 0039d316-1c4b-4281-b951-d872f2087c98
* GTTF: Extract performance-testing-specific parts of UITestBase to UIPerfTest.phajdan.jr@chromium.org2010-08-261-2/+2
| | | | | | | | | | | In the future this may even be used to tune some settings/behaviors (like timeouts) for performance tests. TEST=ui_tests, page_cycler_*, etc BUG=none Review URL: http://codereview.chromium.org/3137040 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@57552 0039d316-1c4b-4281-b951-d872f2087c98
* CommandLine: add a CopySwitchesFrom() and AppendSwitchPath()evan@chromium.org2010-07-291-2/+1
| | | | | | | | | | | These are two common patterns in Chrome code: copying a subset of switches from one CommandLine to another, and appending a FilePath to a CommandLine. This sets me up to do a lot more deprecation in a follow-up change. Review URL: http://codereview.chromium.org/3012021 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@54218 0039d316-1c4b-4281-b951-d872f2087c98
* Re-apply http://codereview.chromium.org/1622012timurrrr@chromium.org2010-04-301-1/+1
| | | | | | | | | It was reverted as http://codereview.chromium.org/1822001 the fix in Valgrind scripts has been commited as http://codereview.chromium.org/1736026 TEST=trybots Review URL: http://codereview.chromium.org/1763023 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@46070 0039d316-1c4b-4281-b951-d872f2087c98
* Revert "[Third time landing] Python implementation of sync server, for testing."phajdan.jr@chromium.org2010-04-301-1/+1
| | | | | | | | | | This broke the memory waterfall, failed to import protobuf. TBR=nick Review URL: http://codereview.chromium.org/1822001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@46048 0039d316-1c4b-4281-b951-d872f2087c98
* [Third time landing] Python implementation of sync server, for testing.nick@chromium.org2010-04-301-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | Implement the server side of chromium sync inside of testserver.py. The implementation supports at most one account (and ignores authentication credentials), but is otherwise reasonably full featured. Make the sync_integration_tests run by default against the test server. An externally-provided --sync-url will give the old behavior. Protocol buffers stuff: The test sync server requires Python generated code for .proto files. I've put generated code, as well as the python protocol buffers runtime library, in the output directory + "/python" (e.g, on windows, src/chrome/Debug/python/google/protobuf). Flakiness fix: In the InProcessBrowserTest framework, improve the mechanism for tests that want to manually set up a user data directory. The new way ensures that the user data directory is always wiped; tests can't accidentally forget to do this anymore. Flakiness fix: Make testserver try to /kill any old instance that might be hogging the port. Very useful if a test failure leaves a server running. Tested this against all combos of protocols, and it seems to work. Flakiness fix: Port sync_integration_tests to the out-of-process test runner. Flakiness fix: For IN_PROC_BROWSER_TESTS, don't run the test body if the setup triggered a fatal (ASSERT_) failure. BUG=20905,40980 Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=44708 Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=45916 Review URL: http://codereview.chromium.org/1622012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@46040 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 45916 - Python implementation of sync server, for testing.nick@chromium.org2010-04-291-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | Implement the server side of chromium sync inside of testserver.py. The implementation supports at most one account (and ignores authentication credentials), but is otherwise reasonably full featured. Make the sync_integration_tests run by default against the test server. An externallyprovided syncurl will give the old behavior. Protocol buffers stuff: The test sync server requires Python generated code for .proto files. I've put generated code, as well as the python protocol buffers runtime library, in the output directory + "/python" (e.g, on windows, src/chrome/Debug/python/google/protobuf). This might be a bad place, or a bad name open to suggestions. The main thing is that there will be runtime dependencies on it, so it didn't seem right to put it in obj/. Flakiness fix: In the InProcessBrowserTest framework, improve the mechanism for tests that want to manually set up a user data directory. The new way ensures that the user data directory is always wiped; tests can't accidentally forget to do this anymore. Flakiness fix: Make testserver try to /kill any old instance that might be hogging the port. Very useful if a test failure leaves a server running. Tested this against all combos of protocols, and it seems to work. Flakiness fix: Port sync_integration_tests to the outofprocess test runner. Flakiness fix: For IN_PROC_BROWSER_TESTS, don't run the test body if the setup triggered a fatal (ASSERT_) failure. BUG=20905,40980 Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=44708 Review URL: http://codereview.chromium.org/1622012 TBR=nick@chromium.org git-svn-id: svn://svn.chromium.org/chrome/trunk/src@45918 0039d316-1c4b-4281-b951-d872f2087c98
* Python implementation of sync server, for testing.nick@chromium.org2010-04-291-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | Implement the server side of chromium sync inside of testserver.py. The implementation supports at most one account (and ignores authentication credentials), but is otherwise reasonably full featured. Make the sync_integration_tests run by default against the test server. An externally-provided --sync-url will give the old behavior. Protocol buffers stuff: The test sync server requires Python generated code for .proto files. I've put generated code, as well as the python protocol buffers runtime library, in the output directory + "/python" (e.g, on windows, src/chrome/Debug/python/google/protobuf). This might be a bad place, or a bad name -- open to suggestions. The main thing is that there will be run-time dependencies on it, so it didn't seem right to put it in obj/. Flakiness fix: In the InProcessBrowserTest framework, improve the mechanism for tests that want to manually set up a user data directory. The new way ensures that the user data directory is always wiped; tests can't accidentally forget to do this anymore. Flakiness fix: Make testserver try to /kill any old instance that might be hogging the port. Very useful if a test failure leaves a server running. Tested this against all combos of protocols, and it seems to work. Flakiness fix: Port sync_integration_tests to the out-of-process test runner. Flakiness fix: For IN_PROC_BROWSER_TESTS, don't run the test body if the setup triggered a fatal (ASSERT_) failure. BUG=20905,40980 Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=44708 Review URL: http://codereview.chromium.org/1622012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@45916 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 44708 - Python implementation of sync server, for testing.nick@chromium.org2010-04-151-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | Implement the server side of chromium sync inside of testserver.py. The implementation supports at most one account (and ignores authentication credentials), but is otherwise reasonably full featured. Make the sync_integration_tests run by default against the test server. An externallyprovided syncurl will give the old behavior. Protocol buffers stuff: The test sync server requires Python generated code for .proto files. I've put generated code, as well as the python protocol buffers runtime library, in the output directory + "/python" (e.g, on windows, src/chrome/Debug/python/google/protobuf). This might be a bad place, or a bad name open to suggestions. The main thing is that there will be runtime dependencies on it, so it didn't seem right to put it in obj/. Flakiness fix: In the InProcessBrowserTest framework, improve the mechanism for tests that want to manually set up a user data directory. The new way ensures that the user data directory is always wiped; tests can't accidentally forget to do this anymore. Flakiness fix: Make testserver try to /kill any old instance that might be hogging the port. Very useful if a test failure leaves a server running. Tested this against all combos of protocols, and it seems to work. Flakiness fix: Port sync_integration_tests to the outofprocess test runner. Flakiness fix: For IN_PROC_BROWSER_TESTS, don't run the test body if the setup triggered a fatal (ASSERT_) failure. BUG=20905,40980 Review URL: http://codereview.chromium.org/1622012 TBR=nick@chromium.org Review URL: http://codereview.chromium.org/1633015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@44714 0039d316-1c4b-4281-b951-d872f2087c98
* Python implementation of sync server, for testing.nick@chromium.org2010-04-151-1/+1
| | | | | | | | | | | | | | | | | | | | | | Implement the server side of chromium sync inside of testserver.py. The implementation supports at most one account (and ignores authentication credentials), but is otherwise reasonably full featured. Make the sync_integration_tests run by default against the test server. An externally-provided --sync-url will give the old behavior. Protocol buffers stuff: The test sync server requires Python generated code for .proto files. I've put generated code, as well as the python protocol buffers runtime library, in the output directory + "/python" (e.g, on windows, src/chrome/Debug/python/google/protobuf). This might be a bad place, or a bad name -- open to suggestions. The main thing is that there will be run-time dependencies on it, so it didn't seem right to put it in obj/. Flakiness fix: In the InProcessBrowserTest framework, improve the mechanism for tests that want to manually set up a user data directory. The new way ensures that the user data directory is always wiped; tests can't accidentally forget to do this anymore. Flakiness fix: Make testserver try to /kill any old instance that might be hogging the port. Very useful if a test failure leaves a server running. Tested this against all combos of protocols, and it seems to work. Flakiness fix: Port sync_integration_tests to the out-of-process test runner. Flakiness fix: For IN_PROC_BROWSER_TESTS, don't run the test body if the setup triggered a fatal (ASSERT_) failure. BUG=20905,40980 Review URL: http://codereview.chromium.org/1622012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@44708 0039d316-1c4b-4281-b951-d872f2087c98
* [GTTF] Reduce number of automation methods ending with WithTimeout.phajdan.jr@chromium.org2010-03-221-6/+2
| | | | | | | | | | | | | | | | | | | | | They are just too easy to misuse. People started inventing their own hardcoded timeouts all over the place. Also, the is_timeout return parameter was not checked consistently. Additionally, some calls actually had no timeout at all, making hangs possible. This change also removes useless DLOG statements. We should get the required info from the ASSERT/EXPECT macros in test code, which is quite well checked by WARN_UNUSED_RESULT. TEST=all ui-based BUG=none Review URL: http://codereview.chromium.org/1076005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42213 0039d316-1c4b-4281-b951-d872f2087c98
* [GTTF] Make automation framework more solid by making sure thatphajdan.jr@chromium.org2010-03-161-7/+10
| | | | | | | | | | | | | | | | | | | important return values are not ignored. The macro used here, WARN_UNUSED_RESULT, takes effect only for GCC, but that's enough since we have bots for all platforms. Adding these warnings already detected some cases where a return value was ignored. In some of them the test was trying to get the information about success "some other way", in some it could sometimes confuse test failure with test success. TEST=ui_tests BUG=none Review URL: http://codereview.chromium.org/948002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@41696 0039d316-1c4b-4281-b951-d872f2087c98
* Make running chrome process detection in ui tests more reliable.phajdan.jr@chromium.org2010-01-131-2/+2
| | | | | | | | | | | Also drops fragile code. TEST=Covered by ui_tests. BUG=10840 Review URL: http://codereview.chromium.org/545006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@36119 0039d316-1c4b-4281-b951-d872f2087c98
* Make the commit_charge the important statistic (displayed on thesgk@google.com2009-11-211-1/+2
| | | | | | | | | perf overview dashboard) for memory_test, but not for page_cycler. BUG=none TEST=none Review URL: http://codereview.chromium.org/418034 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@32714 0039d316-1c4b-4281-b951-d872f2087c98
* Convert memory_test to use the common stats-reporting methods in UITest.sgk@google.com2009-11-201-129/+10
| | | | | | | | | | | | This adds IO stats to memory_test, and renames most of the memory_test traces to match the names used by page_cycler so that (after the historical memory_ data is converted) we can do apples-to-apples comparisons of stats across all the tests that use these methods. BUG=none TEST=none Review URL: http://codereview.chromium.org/402104 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@32632 0039d316-1c4b-4281-b951-d872f2087c98
* Use GetSwitchValuePath.evan@chromium.org2009-11-161-3/+3
| | | | | | | | | | BUG=24672 TEST=unit_tests Patch by Thiago Farina <thiago.farina@gmail.com>. Review URL: http://codereview.chromium.org/375016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@32093 0039d316-1c4b-4281-b951-d872f2087c98
* Spellchecker: call init *after* constructor.estade@chromium.org2009-11-161-13/+3
| | | | | | | | | This fixes the error where PostTask would post the task to the file thread and release its reference before the constructor returned. credit for fix goes to jam@ and thestig@ Review URL: http://codereview.chromium.org/399011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@32089 0039d316-1c4b-4281-b951-d872f2087c98
* Disable memory test on 64bit Linux since it sometimes crashes right now.vandebo@chromium.org2009-11-141-3/+3
| | | | | | | | | TEST=none BUG=none Review URL: http://codereview.chromium.org/391065 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@31988 0039d316-1c4b-4281-b951-d872f2087c98
* Mark memory_test as flaky on 64bit linuxvandebo@chromium.org2009-11-141-3/+13
| | | | | | | | | BUG=none TEST=none Review URL: http://codereview.chromium.org/386034 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@31975 0039d316-1c4b-4281-b951-d872f2087c98
* Fix cut-and-paste typo for KByte => byte memory stat conversion on print.sgk@chromium.org2009-11-091-1/+1
| | | | | | | | BUG=none TEST=none Review URL: http://codereview.chromium.org/372058 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@31436 0039d316-1c4b-4281-b951-d872f2087c98
* More memory stats code cleanup:sgk@chromium.org2009-11-091-4/+3
| | | | | | | | | | | | Move GetSystemCommitCharge() into bsae\process_util*. Kill PrintChromeMemoryUsageInfo(), which was only used by reliability_tests.exe on Windows and whose stats are obsolete. Delete the now-unnecessary chrome\test\perf\mem_usage* files. BUG=none TEST=none Review URL: http://codereview.chromium.org/371025 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@31423 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 31333 - For memory_test:willchan@chromium.org2009-11-071-30/+25
| | | | | | | | | | | | | | | | Change the RESULT output format. Add an option to collect memory statistics after each navigation. Fix a type error in Linux CommitCharge calculation. BUG=none TEST=none Review URL: http://codereview.chromium.org/376005 TBR=vandebo@chromium.org Review URL: http://codereview.chromium.org/374020 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@31340 0039d316-1c4b-4281-b951-d872f2087c98
* For memory_test:vandebo@chromium.org2009-11-071-25/+30
| | | | | | | | | | | | | Change the RESULT output format. Add an option to collect memory statistics after each navigation. Fix a type error in Linux CommitCharge calculation. BUG=none TEST=none Review URL: http://codereview.chromium.org/376005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@31333 0039d316-1c4b-4281-b951-d872f2087c98
* Get rid of GetMemoryInfo() in favor of using base::ProcessMetrics.sgk@chromium.org2009-11-051-18/+34
| | | | | | | | | | Use a test-specific subclass to isolate the stopgap use of 'ps' to collect memory stats on Mac. BUG=none TEST=none Review URL: http://codereview.chromium.org/342070 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@31144 0039d316-1c4b-4281-b951-d872f2087c98
* Implement membuster in memory_test.vandebo@chromium.org2009-11-051-19/+171
| | | | | | | | | BUG=none TEST=none Review URL: http://codereview.chromium.org/356003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@31107 0039d316-1c4b-4281-b951-d872f2087c98
* Refactor memory_test so that it can easily support additional workloads.vandebo@chromium.org2009-10-301-165/+206
| | | | | | | | | BUG=none TEST=none Review URL: http://codereview.chromium.org/340041 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@30606 0039d316-1c4b-4281-b951-d872f2087c98
* Fix memory_test's temporary user data directory path, the base namesgk@chromium.org2009-10-091-5/+8
| | | | | | | | | of which is copied into the containing temporary directory. BUG=none TEST=Useful mem test stats in the perf graph. Review URL: http://codereview.chromium.org/266047 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@28625 0039d316-1c4b-4281-b951-d872f2087c98
* Fix memory_test to use the correct temporary user_data_dir_, so itsgk@chromium.org2009-09-281-6/+11
| | | | | | | | | | | reports valid memory stats for browser and {ws,vm}_final_{browser,total}. Add a sanitary assert for returned browser process id so the test will actually fail if it breaks again. BUG=none TEST=none Review URL: http://codereview.chromium.org/245030 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@27428 0039d316-1c4b-4281-b951-d872f2087c98
* Hack to make tests work if out is a symlink: see if the current dir is the ↵mattm@chromium.org2009-09-101-3/+1
| | | | | | | | | | | | | source root. Fix some tests that were manually getting sourcedir from DIR_EXE instead of using DIR_SOURCE_ROOT. BUG=none TEST=rm -r out, ln -s /somedir/out out, run tests Review URL: http://codereview.chromium.org/192064 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@25898 0039d316-1c4b-4281-b951-d872f2087c98
* Second part of memory_test for Mac.paul@chromium.org2009-08-261-5/+2
| | | | | | | | | | | This CL implements the actual memory measurements. BUG=16434 (http://crbug.com/16434) TEST=memory_test should now run and report accurate memory numbers on Mac. Review URL: http://codereview.chromium.org/173454 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@24549 0039d316-1c4b-4281-b951-d872f2087c98
* First part of getting memory_tests running on Mac.paul@chromium.org2009-08-251-17/+3
| | | | | | | | | | | This CL provides the scaffolding for subsequent changes. BUG=16434 (http://crbug.com/16434) TEST=Nothing yet. Review URL: http://codereview.chromium.org/174402 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@24313 0039d316-1c4b-4281-b951-d872f2087c98
* Add automation call to wait for multiple navigations.phajdan.jr@chromium.org2009-08-191-1/+1
| | | | | | | | | | | | | Convert one ErrorPage UI test to use it. The rest of the tests will require more work. TEST=Covered by ui_tests. http://crbug.com/19361, http://crbug.com/19395 Review URL: http://codereview.chromium.org/174015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@23729 0039d316-1c4b-4281-b951-d872f2087c98
* Revert "Add automation call to wait for multiple navigations."phajdan.jr@chromium.org2009-08-191-1/+1
| | | | | | | | | | Broke the page cyclers. TBR=tony Review URL: http://codereview.chromium.org/174065 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@23717 0039d316-1c4b-4281-b951-d872f2087c98
* Add automation call to wait for multiple navigations.phajdan.jr@chromium.org2009-08-191-1/+1
| | | | | | | | | | | | | Convert one ErrorPage UI test to use it. The rest of the tests will require more work. TEST=Covered by ui_tests. http://crbug.com/19361, http://crbug.com/19395 Review URL: http://codereview.chromium.org/174015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@23711 0039d316-1c4b-4281-b951-d872f2087c98
* Don't grant unnecessary handle privileges in OpenProcessHandle.phajdan.jr@chromium.org2009-06-191-1/+1
| | | | | | | | | This patch makes it harder for process handles with more privileges to leak to untrusted places. Review URL: http://codereview.chromium.org/125260 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@18802 0039d316-1c4b-4281-b951-d872f2087c98
* Start to get memory test compiling on mac & linux.thomasvl@chromium.org2009-06-151-20/+43
| | | | | | | | | | | | Block some memory checks with #if defined(win) to get things compiling. Switch some things over to file paths. Test doesn't work yet, but this atleast gets it compiling/linking now. TEST=none BUG=14098 Review URL: http://codereview.chromium.org/125124 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@18418 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-01-31 09:21:19 +0000