summaryrefslogtreecommitdiffstats
path: root/chrome/browser/process_singleton_mac_unittest.cc
Commit message (Collapse)AuthorAgeFilesLines
* Move scoped_temp_dir from base to base/filesbrettw@chromium.org2012-11-161-1/+1
| | | | | | | | | | Also add to base namespace. BUG= Review URL: https://codereview.chromium.org/11359217 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@168281 0039d316-1c4b-4281-b951-d872f2087c98
* Move eintr_wrapper.h from base to base/posixbrettw@chromium.org2012-11-141-1/+1
| | | | | | Review URL: https://codereview.chromium.org/11366229 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@167739 0039d316-1c4b-4281-b951-d872f2087c98
* Refactor ProcessSingleton so that it may be used distinctly from a full ↵erikwright@chromium.org2012-04-051-11/+19
| | | | | | | | | | | | | | | | | browser process. The main effect is that ProcessSingleton is much more restricted to its basic functionality, which is to ensure that a single instance of Chrome runs per profile directory and to pass messages from new Chrome invocations to the existing instance. Exactly how those messages were handled has been moved from the implementations of ProcessSingleton into ChromeBrowserMain where (I think) it more rightly belongs. This will allow the Chrome Frame net tests to use ProcessSingleton to implement a stub Chrome for the purpose of handling network-related IPC from Chrome Frame without having to launch the rest of Chrome, upon which ProcessSingleton previously depended directly. BUG=None TEST=None Review URL: http://codereview.chromium.org/9968053 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@130853 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
* Added WARN_UNUSED_RESULT to ScopedTempDir methods.cbentzel@chromium.org2011-01-131-2/+1
| | | | | | | | | BUG=NONE TEST=all targets build, tests pass. Review URL: http://codereview.chromium.org/6042009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@71322 0039d316-1c4b-4281-b951-d872f2087c98
* [Mac] Lock profile against multiple uses.shess@chromium.org2010-10-141-0/+149
Mac uses Launch Services to make sure one Chrome is started from the GUI, and AppleEvents and Launch Services to pass in URLs. When a developer or test launches multiple browsers against a profile, it fails in mysterious ways. This adds a profile lock to flush out any hidden assumptions. BUG=22163,58986,59061 TEST=Run Chromium twice with same --user-data-dir. Second instances shouldn't launch. Review URL: http://codereview.chromium.org/3777003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@62659 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-05-20 03:00:37 +0000