Comment 3 for bug 308605

(In reply to comment #2)
> > How the "unresponsive" Firefox is started before the "unresponsive" problem?
> Steps:
> 1) firefox -P profile1
> 2) firefox -P profile1 -no-remote

Problem was re-created very easily, with Fx Trunk on MS Win-XP SP3.
(I have multiple profiles, so only "multiple profile exist" case is tested)
> Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b1pre) Gecko/20080910043000 Minefield/3.1b1pre
Following dialog was issued when "2) firefox.exe -no-remote -P profile1" is kicked after "1)".
> 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.
This dialog was displayed even when "2) firefox.exe -no-remote -P profileX", where profileX doen't exist.
If profile name is not supplied("2) firefox.exe -no-remote -P" is used), profile manager's profile selection window is displayed.

I set "firefox.exe -P"(currently same behavior as "firefox.exe -ProfileManager"), because I want to choose profile manually always, so I couldn't meet the phenomenon.
If both are "Remote Mode"(without -no-remote), behaviour looks to be "as desinged".
See 459535 Comment #5 for Fx 3's behaviour when both are "Remote Mode"(without -no-remote switch).
This is possibly next problem:
  If -P "profile_name" is specified, "-no-remote" works only when already
  running Fx instance without -no-remote(Fx with Remote mode) doesn't exists.
I guess that this is because "-no-remote" is a circumvention of inconvenience due to design change of "kill -remote switch and force use of MOZ-NOREMOTE=1".