Build ID: 1999061708 Platform: Windows NT If you launch apprunner.exe a second time, a new instance of apprunner is created in a new process. Expected behavior is that focus is switched to the already-running instance of apprunner and a new browser window is created.

Bill, is this out bug?

Putting on Browser-General until you'all figure out who it belongs to :-)

I guess this our bug (or "feature", depending on your point of view). Note that Unix always let you have multiple processes in 4.x. Mac takes care of this for us (I think). We need to sort out what's the right thing for each platform and figure out how to implement it in an XP fashion. Also, the Win32 4.x versions dealt with this via DDE, support for which is lacking in the current apprunner.exe.

Updating QA Contact

Pushing out. Now that we're more XP, we really need to address this historic discrepancy between the Windows and Unix flavors of the browser.

I'm moving this way out. Some consider this a feature, not a bug and it will require much effort to fix.

Move to M15.

Still a problem in the 2000032719 build under Windows 2000. Due to the large memory requirements of 6 (~25 M bytes per instance), this could conceivably be a pretty bad thing for beginning users that keep double-clicking on the app icon to launch a new browser window.

Move to M16 for now ...

spam: qa contact to jrgm@netscape.com

Nominated for b2 to prevent two processes from accessing the same profile

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

Dutifully marking as verified duplicate (although, as always, I will point out that this bug was filed nine months before the other bug was filed).