Closed Bug 424649 Opened 16 years ago Closed 16 years ago

"Firefox is already running" launching link if Firefox started with -no-remote

Categories

(Toolkit :: Startup and Profile System, defect)

x86
Windows Vista
defect
Not set
major

Tracking

()

RESOLVED INVALID

People

(Reporter: ravenousbugblatterbeast, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9b4) Gecko/2008030714 Firefox/3.0b4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9b4) Gecko/2008030714 Firefox/3.0b4

If you start Firefox with the -no-remote command line options, whenever you click an HTTP link in a 3rd party application you get a message:

 "Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system."

Reproducible: Always

Steps to Reproduce:
1. Run firefox.exe -no-remote
2. Click on a hyperlink from a 3rd party application e.g. MSN messenger

Actual Results:  
An error message "Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system."

Expected Results:  
I'd expect the link to appear in the existing Firefox window in a new tab, as it does without the -no-remote option.

If I have two Firefox processes simultaneously running under different profiles by using the -P and -no-remote options, I would expect the link to open in the window that is running under the default profile.
I'm afraid this _very annoying_ behavior is related to an underlying operating system, and there's little Firefox can do about it. :[
(Oh please someone tell me I'm wrong!)

Nonetheless this has my vote.
The *whole point* of -no-remote is *not* to open the link in the existing process, but in a new process. You need to have a different profile for each process. INVALID.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
So apparently the question stands whether ability to use more instances/profiles concurrently *must inevitably* lead to inability of opening URLs from other applications.
(In reply to comment #3)
> So apparently the question stands whether ability to use more
> instances/profiles concurrently *must inevitably* lead to inability of opening
> URLs from other applications.

Wrong. :)
With FF3b5 links seem to work fine even with -no-remote.
Product: Firefox → Toolkit

11 years of this bug and no fix...
Awesome...

Ping to reopen this task!
It was not properly fixed.

You need to log in before you can comment on or make changes to this bug.