187235 - Registry file coexistence mozilla 1.2.1 and Netscape 7.0.1

Status: RESOLVED WORKSFORME

(Core :: XPCOM, defect)

Description

[Joseph Van Cauwenbergh]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130

Platforms Win2k professional, Linux Mandrake 9.0, Win98 SE.
When both browsers are intalled on the same platform at a given time, may be
after launching Netscape with a Mozilla profile or after Launching Mozilla with
a Netscape profile the  Registry.dat file in .Mozilla directory grows in size. I
experimented registry files of more than 5MB. If this happens startup of both
browsers is very long.  This happens very often after Netscape installation.
Directly after installation Netscape is launched and use the "default" profile
which is a Mozilla profile if Netscape is installed after Mozilla.

Reproducible: Sometimes

Steps to Reproduce:
1. Install Mozilla 1.2.1 use default profile.
2. Install Netscape 7.0.1 
There are other ways look at the details.

Actual Results:  
A big registry.dat file

Expected Results:  
Twoo separated Profile and Mozilla directories one for Netscape one For Mozilla.
It's very quickly done to use a Mozilla profile with Netscape or vice versa.
If the twoo structures are separated this will be less frequent.
At installation user should be asked where to put the Mozilla structure and if
he does not choose of a particular directory then actual .Mozilla  or Mozilla
default directory in WIN profile directories or in Home directory should be
used. Shortly give user a better control over placement of these structures at
installation.

-

Comment 1

[Matthias Versen [:Matti]]

-> invalid

We don't accept Netscape bugs (!) and also NSCP is based on the 1.0.x branch.
Please reopen if you get something like this with Mozilla 1.2.1 and 1.3a.

1.0.x is old and we fixed many between 1.x and 1.3a (this also includes
registry.dat grow)

Comment 2

[Joseph Van Cauwenbergh]

Ok Matti I agree this can be or is a NSCP bug. But Still stays the second part.
It's not "sain" that twoo different products use the same basic structures. Even
if both are issued of same roots. So why not allowing users to break this
sharing of basic structures such as the registery avoiding corruptions of te
common structures such as the registry by one of te browsers. Grow of registery
is fixed    in Mozilla but not in Netscape. Netscape uses Mozilla registry and
corrupts it. How can I escape to this problem today? Deinstall Netscape? Why
should I? I use both. Is there any parameter I can change so it would be
possible to create a .mozilla directory for Mozilla and a .netscape for
Netscape? Avoiding also a profile manager with Netscape profiles and Mozilla
profiles "mélangés".

Comment 3

[Joseph Van Cauwenbergh]

Sorry Matti I have to reopen this bug. 
First of all I reported the same bug to Netscape on their site. 
But It's a real mess these twoo browsers together on the same platform.I
installed mandrake 9.0 with Mozilla 1.1(which is the bundled version with
mandrake 9.0) using mozilla alone is a wonderfull world.
I installed Netscape 7.0.1.on mandrake using Netsacpe installer I refused to
connect to their site after installation and created a Netscape profile before
using the browser. So far so good . Afterwards I installed Mozilla 1.2.1 with
the mozilla installer and my Netscape profile disapeared.(I did not deinstall
the mandarke package first so I have now Mozilla 1.1 and 1.2.1 and Netscape
7.0.1 running at the same time). 
I am sorry but if the twoo browsers continue  to use the same structure this
famous .Mozilla directory in the user home directory there is a high risk of
mutual corruption if both browsers are not at the same technology level.(Which
is the case).
I am a little bit surprised with your answer this is not a Mozilla bug. Well
then look at it as a request for enhancement and avoidance of trouble to be polite. 

Happy New Year.

Comment 4

[Matthias Versen [:Matti]]

This should be fixed in recent mozilla builds.