This happens when there is a mozregistry.dat, but no profile directory to go with it. Deleting the mozregistry.dat launches the profile manager and then the browser comes up fine.
Bhuvan, I didn't find any duplicates of this in the open bugs. I had thought this was fixed, but maybe recent changes broke it again. Steve
Summary: mozilla.exe crashes if there's no profile directory. → [DOGFOOD]mozilla.exe crashes if there's no profile directory.
If there is a mozregistry.dat file but the profile directory has been deleted, the profiles in the mozregistry.dat will be listed in profile manager window. If you select one, you will exit - since there are no profile files associated with the entry
accepting the bug.
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
The crash occurred in the past, as the profile directory was deleted and app couldn't find prefs file. This is Fixed. Code has been added to recreate the entire directory structure that is lost. The directory path is obtained from the registry. Contents of the defaults/profile folder gets copied into the newly created folder.
*** Bug 14941 has been marked as a duplicate of this bug. ***
*** Bug 12107 has been marked as a duplicate of this bug. ***
Moving all Profile Manager bugs to new Profile Manager Backend component. Profile Manager component to be deleted.
You need to log in before you can comment on or make changes to this bug.