Patching Mozilla to run multiple instances

[Tim Wunder]

On 9/3/2002 10:45 AM, someone claiming to be Net Llama! wrote:
> On Mon, 2 Sep 2002, Tim Wunder wrote:
> 
>>On Monday 02 September 2002 10:37 pm, Net Llama! wrote:
>>
>>>AFAIK, Mozilla-1.x has this built in already.
>>>
>>
>>I was thinking that, too. But I've labelled my build Mozilla1.0+, so I'm
>>thinking it's a post-1.0 build, and I can't run multiple instances.
> 
> 
> Perhaps i'm not understanding what you mean by multiple instances.  What i
> assume this to mean is when you go to run Mozilla a 2nd time, it spwans an
> entirely new instance of Mzoilla that is seprate from the first one.
> 
> That's what i get with 1.x.
> 

No, you don't misunderstand. This doesn't happen with my current build, which is either 1.0, or 1.0 RC2 or 3, compiled. If Moz is open already, and I click a link in Kmail, I'm presented with the profile manager as it won't let me open a new instance of Mozilla under the already open profile. IIRC, that's what brought about the composition of the SxS I referenced. I do seem to remember that the problem was temporary and the SxS page was created as a stop-gap for addressing a specific problem that was going to get fixed...
It hasn't been a real issue for me since I'd been using Konqueror to load any links from Kmail. As I've really become accustomed to tabbed browsing while at work, I'll be switching to Mozilla for that now, at least until I evaluate Konqueror's implementation of tabbed browsing once KDE 3.1 gets released.

> 
>>>compiled for i686?
>>
>>Nope, not unless that's recently changed. There was a noticable improvement
>>after I compiled Moz with the optimizations.
> 
> 
> The tarball has always had i686 in its name, for as far back as i can
> remember.

OK, I misunderstood you. I believe there are other optimizations that you can do to boost the performance under linux besides just compiling for i686 that the standard builds don't do.

Performance with Mozilla under linux had always been worse for me than the performance I got at work under Winders, at least until I compiled it myself with whatever optimizations I did that I can't remember 'cuz I didn't write it down...

You know, as I sit here writing this, I'm thinking that the performance issue may be specific to running nightly builds (I tend to run nightlies), the releases may be optimized. Jeez, my brain *used* to be able to remember a whole lot better than it does now...

Hopefully, as the day progresses, I'll get a better handle on what it was that I did, and why...

Regards, 
Tim