131014 - Profiles used with MachV/N6.2 get corrupted and cause N6.2+to hang

Status: RESOLVED INVALID

(Core Graveyard :: Profile: BackEnd, defect)

Description

[Grace Bush]

starting with Profiles, please reassign if that is wrong place


steps to reproduce:You will need a profile that has been used with N6.2(or 
earlier) and MachV.  
1. install 6.2.1  ( full)
2. Install 6.2.2 (full upgrade)

actual results: 6.2.2 hangs-using task manager, you see it uses 100%cpu

expected results: launch with regularly used profile

creating a new profile allows a launch
some people have reused the profile with MachV and then can launch 6.2.2

Comment 1

[Grace Bush]

moving to bugscape

Comment 2

[Grace Bush]

v

Comment 3

[Grace Bush]

reopening and transferring  comments from bug 12579 in bugscape
------- Additional Comment #2 From Patty Mac 2002-03-14 15:48 -------

Grace, I saw the similar behavior like you whether using the existing
profile or creating a new profile. 

1. install 6.2.1  (full)
2. Install 6.2.2 (full upgrade)
3. Launch 6.2.2 with the existing profile.
4. Visit http://java.sun.com
5. It loads fine.
6. Visit another site: http://java.sun.com/applets/other/Bullets/huebullet.html
   or any url that might hang. If it does not hang immediately, click "reload" 
   buttons. Then the the browser hangs!!!
7. Hit "CTR, ALT+DEL" keys to kill the process.
8. Relaunch 6.2.2 again using the same existing profile.
10. Revisit http://java.sun.com
11. It hangs!
12. Creat a new profile at this time. 
13. Repeat step#10.
14. Applet does not load.



------- Additional Comment #3 From Patty Mac 2002-03-14 15:50 -------

Seen on my windows 98.



------- Additional Comment #4 From Lisa Chiang 2002-03-14 16:24 -------

This is critical to get fixed for 6.2.2.  Prashant has seen this as well. cc'ing
him.

Pls email [e-mail] with this bug so that it gets on the team's radar
right away (if not already).

I'm not sure who to assign this bug to.

So, there is a problem with 6.2/6.2.1 going to 6.2.2?  (Let's try to take MachV
out of the equation since our customers won't have MachV.)




------- Additional Comment #5 From Michael Buckland 2002-03-15 08:14 -------

AOLTW-ing.



------- Additional Comment #6 From Scott Putterman 2002-03-15 14:43 -------

From the testing that's been done, it sounds like this doesn't happen when Mach
V isn't on the system.  

Conrad, would you have any idea about why profiles aren't backward compatible? 
It would be great if we knew why this happened so we could know for sure that
systems without Mach V are ok.



------- Additional Comment #7 From Conrad Carlen 2002-03-15 15:05 -------

> Conrad, would you have any idea about why profiles aren't backward compatible?

No. The profile mgr knows nothing about the contents of files within a profile
dir - it just allows consumers to find out where their files are located. Every
consumer of profile data is independent. So, we need to find out *which* item in
the profile dir isn't backward compatible. Usually, you try getting rid of one
file at a time, until the particular file or dir is known. Start with
localstore.rdf, history.dat, prefs.js, Cache, etc.



------- Additional Comment #8 From Simon Fraser 2002-03-19 17:53 -------

Shouldn't this bug be a 6.2.2 blocker? Lots of folks may try running 6.2.2 after
running a more recent Mozilla (or internal Netscape commercial) build, and are
going to get bitten by this. We need to make our profile data more future-proof.



------- Additional Comment #9 From Lisa Chiang 2002-03-19 19:30 -------

reassign to ccarlen since this is in profiles.

We should figure out what is happening as ccarlen suggests.  We will have folks
running into this and need to be ready with any workarounds or answers.



------- Additional Comment #10 From Paul Wyskoczka 2002-03-20 07:04 -------

Grace is the qa contact and that is appropriate. Grace, once 6.22 is released
lets move this bug to bugzilla so we can track the problem.



------- Additional Comment #11 From [e-mail] 2002-03-20 10:50 -------

sent information to doc team for relnote



------- Additional Comment #12 From [e-mail] 2002-03-25 15:38 -------

When the profile used is one migrated from 4.x I can reproduce this reliably by 
installing and running commercial trunk builds along with branch builds for 
6.2.2
What I found after doing diffs on profiles used from the upgrade process vs 
profile migrated in 6.2.2 launch was that my bookmarks file grew to 34 mb in one 
case- 88mb in another (from 20kb in both instances).  removing that file allowed 
me to launch and maintain all my other files.  
I am trying to determine where this growth takes place and cannot make it 
happen with a newly created profile.

Comment 4

[Grace Bush]

see also bug 127856 and bug 133223 that discuss the huge bookmark file

Comment 5

[Simon Paquet [:sipaq]]

Obsolete bug. Netscape no longer works on Mozilla and especially not on MachV.
-> INVALID