Closed Bug 134517 Opened 23 years ago Closed 22 years ago

Running Netscape 6/7 concurrently with Mozilla breaks cache

Categories

(Core :: Networking: Cache, defect, P4)

Product:
Core
Component:
Networking: Cache
Platform:
x86
Windows XP
Type:
defect

Tracking

()

Status:
VERIFIED INVALID
Milestone:
mozilla1.2beta

People

(Reporter: megabyte, Assigned: gordon)

References

Details

(Keywords: dataloss, relnote) 

If I run Mozilla and browse some pages and then run Netscape 6.2.2 and go back
to Mozilla, when I try to visit cached pages, they don't show up until I clear
the cache.
OS: WinXP
Mozilla build 2002032919-GMAKE
Netscape 6.2.2 build 20020314
Aaron, are you using Mozilla and Netscape with the same profile ?
In the affirmative, it is bug 76431
So.. you're running Mozilla and Netscape at the same time?  (you don't quit 
Mozilla before starting Netscape)
Yes and Yes


*** This bug has been marked as a duplicate of 76431 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
*** Bug 146269 has been marked as a duplicate of this bug. ***
*** Bug 146758 has been marked as a duplicate of this bug. ***
*** Bug 146778 has been marked as a duplicate of this bug. ***
Reopening since it still happens after bug 76431 fix landing.
Blocks: profile-corrupt
Status: RESOLVED → REOPENED
Keywords: dataloss
Resolution: DUPLICATE → ---
Summary: Netscape 6.2.2 breaks Mozilla cache → Netscape 6/7 breaks Mozilla cache
This is especially troublesome in this case:
Say I want to use Mozilla for my web browser, but Netscape 7 for my AIM/ICQ
client.  My web cache becomes unusable in Mozilla because Netscape 7 is open
(but not its web browser).  Now if I clear the cache in Mozilla to fix that
problem, it erases stuff in Netscape 7 and it forgets my logins for AIM/ICQ.
Keywords: mozilla1.0.1, nsbeta1, nsCatFood
*** Bug 146877 has been marked as a duplicate of this bug. ***
*** Bug 146879 has been marked as a duplicate of this bug. ***
Not good...  Numerous dupes since Netscape 7.0PR1 was released...
Upping priority since this is about to become a really big problem.
CC'ing ccarlen for triage (possible component reassignment)
Severity: normal → critical
Keywords: mozilla1.0
Summary: Netscape 6/7 breaks Mozilla cache → Running Netscape 6/7 concurrently with Mozilla breaks cache
Yes. Clearing the cache fixed it. Sorry I thought that I had done that already
before posting the earlier bug (146879). 

Also did not realize is was cache related, hence the dupe.
This needs to be a relnote if its not fixed by release time.
Keywords: relnote
*** Bug 147661 has been marked as a duplicate of this bug. ***
Dumb question, but does Netscape PR 1.0 include the fix in bug 76431? If it
does, then this bug should remain open. If not, then this bug should be resolved
as a duplicate of that bug. 
If not I was hoping a fix could be designed so that the running Mozilla can
protect its own stuff and not let others break it instead of a fix that only
stops new versions from breaking it.  Until then, we do need a relnote at the least.
Priority: -- → P4
Target Milestone: --- → mozilla1.2beta
I don't think this is an issue anymore. Start Mozilla 1.3 alpha on Windows 98.
Start Netscape 7.01. Try to make Netscape use the same profile Mozila is using.
Error message.

Recommend that this be resolved worksforme or invalid.
yes that is correct, you will get a message like "Mozilla can't use same profile
when it is in use."

marking INVALID
Status: REOPENED → RESOLVED
Closed: 23 years ago → 22 years ago
Resolution: --- → INVALID
v
Status: RESOLVED → VERIFIED
Read comment 16.  Should I open a bug specifically for that?
Status: VERIFIED → REOPENED
Resolution: INVALID → ---
Can you explain what you meant in comment 16 a little clearer please?  It does
appear as though the problem described in the summary cannot possibly happen now.
Basically, the newest versions of Netscape do not break the cache because they
cannot share the profiles due to locking.  However, older versions do not honor
the profile locking mechanism and will still break the cache.  So, Mozilla
should do something to actively, not just passively, stop the cache from being
corrupted.
> So, Mozilla
should do something to actively, not just passively, stop the cache from being
corrupted.

There's not a way to lock a directory on the OS level that will prevent access
to files within it by any other random program. I think the only protection
against older builds would be to have a different set of profiles which were
unknown to builds created before advisory locking was implemented. That's not
very practical. Also, since advisory locking was in place by mozilla1.0, it's
less of an issue as time goes by. I think this should be closed again.
If there is absolutely no other way to prevent cache corruption, then close it.
 I still think there needs to be a relnote though.
ok then, re-closing as INVALID per Conrads comment 23.
Status: REOPENED → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → INVALID
v
Status: RESOLVED → VERIFIED
No longer blocks: profile-corrupt
You need to log in before you can comment on or make changes to this bug.