Open Bug 888233 Opened 12 years ago Updated 3 years ago

Change multiple instance detection to only check for instances running the same profile

Categories

(Toolkit :: Startup and Profile System, defect)

22 Branch
x86_64
Windows 7
defect

Tracking

()

UNCONFIRMED

People

(Reporter: will.pittenger1+mozbugzilla, Unassigned)

Details

(Keywords: dupeme)

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:22.0) Gecko/20100101 Firefox/22.0 (Beta/Release) Build ID: 20130618035212 Steps to reproduce: Currently we have a detection mechanism that complains if that app is already running. So if the app is Firefox, any existing instances of Firefox will be detected and cause the new instance of Firefox to simply display an error and quit unless the -no-remote switch was specified. Many IRC users don't know about that switch and have to be told about it. My suggestion is to change the system to work as described below. Please note that Bug 78431 may have been related. Also, a similar issue might arise with multiple instances open at once: Users would need different icons on the task bar to keep them separate. Actual results: Firefox (in this example) would complain if another instance is already running. It would display an error and do nothing else unless the -no-remote switch is used. Expected results: 1. The app (say Firefox) would check only to see if the request profile was in use. 2. If it isn't in use, the app would run normally using that profile. 3. If the profile is in use, the app would instead display the profile manager. Options would exist to run a different profile, create a new profile, or exit.
Component: General → Startup and Profile System
Product: Core → Toolkit
Whiteboard: [dupeme]
Severity: normal → S3
Keywords: dupeme
Whiteboard: [dupeme]
You need to log in before you can comment on or make changes to this bug.