Closed Bug 81807 Opened 23 years ago Closed 23 years ago

Mozilla hung at startup

Categories

(Core Graveyard :: Profile: BackEnd, defect)

Other
Windows 98
defect
Not set
major

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: hwaara, Assigned: ccarlen)

Details

While loading the chrome for the initial window, it hangs. This is in new win32 talkback builds from mozilla.org I have no idea where this belongs, hence why I file against Profile Manager Backend.
This is a smoketest blocker.
Keywords: smoketest
On a Win32 build from earlier today, as well as one completed since this bug was filed, it works for me. This is true with either skin and whether or not profile mgr dialog comes up or not. I'll wait to see if this happens for anybody else or with any other builds before marking WFM.
Can you please try this with a nightly from mozilla.org, rather than something home-built? Thanks
Everything works in a new profile so it must be profile corruption of some sort. Downgrading severity and removing smoketest keyword. Ccarlen, turns out to be a profile-manager bug after all. :)
Severity: blocker → major
Keywords: smoketest
> Can you please try this with a nightly from mozilla.org, rather than > something home-built? A up-to-the-minute build from the tip of the tree is what's most relevant. A nightly is already water under the bridge. > Ccarlen, turns out to be a profile-manager bug after all. Not nescesarily. Many components store many files in a profile dir and the problem could be in any one of them. You need to find out which file of the profile was the problem - then we could know the component.
Reporter, if you can still make this happen, start removing files 1 at a time from the corrupted profile dir and see if you can determine what is corrupted. Then we might be able to do something.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
wfm - verify on build 20010530
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.