322967 - Running multiple instance on HP-UX doesnot work as expected.

Status: RESOLVED DUPLICATE of bug 312154

(Firefox :: General, defect)

Description

[Gowri Kandasamy]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5
Build Identifier: Mozilla/5.0 (X11; U; HP-UX ia64; en-US; rv:1.8) Gecko/20060103 Firefox/1.5

Started firefox in background by running ./firefox &.
The firefox browser came up without any issues.
But when I started another instance of firefox as the same user & profile by running ./firefox, the new browser doesn’t come up. When I closed the firefox that I first started, I get a popup with the following 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. " 

This error message is thrown by the second instance of the browser.  This error message should be thrown as soon as I started the new instance . But message is thrown when I close the browser that I opened first.

When I tun with MOZ_NO_REMOTE=1 , I could open multiple browser instances

Reproducible: Always

Steps to Reproduce:
1.Start firefox in background "./firefox &"
2.Start new instance of firefox "./firefox "
Actual Results:  
Nothing happened when the second instance is started. But when I close the first instance, the following warning message is thrown by the second instance 

"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. " 

If I don't close the first instance, I don't know what's happening with the second instance.

Expected Results:  
That warning message should be thrown by the second instance before closing the fist instance .

On Linux , every time when I start a new instance , a new browser is coming up , but when I close one browser , all the browser instance are getting closed. I think this is expected behavior.

Comment 1

[Gowri Kandasamy]

When I backported the fix for Bug ID: 312154 , it works fine.

*** This bug has been marked as a duplicate of 312154 ***