Closed Bug 10501 Opened 26 years ago Closed 26 years ago

Almost anything with Wallet crashes Seamonkey

Categories

(Toolkit :: Form Manager, defect, P3)

Product:
Toolkit
Component:
Form Manager
Platform:
x86
Windows 95
Type:
defect

Tracking

()

Status:
VERIFIED DUPLICATE of bug 9600

People

(Reporter: kevinyen, Assigned: morse)

Details

I cleaned my machine (e.g., removed old Seamonkey files) and installed Friday's build. These things crash seamonkey: 1. View Wallet contents 2. Using Autofill 3. Try to save a form's info I sent it in via Talkback for the the gorey details. thx, kevin
I retried it. I think the crash occurs when the Installation is in the non-default directory, e.g., in a user specified one, such as "c:\seamonkey". I reintalled in the default c:\program files, etc.; works fine.
Kevin, did you also delete your mozregistry.dat file?
I did not delete the mozregistry.dat in c:\windows.
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → INVALID
Well that was your problem. The mozregistry was saying that you already had a profile whereas in fact you blew away your profile. So any actions that require accessing your profile directory were bound to fail. Had you also deleted your mozregistry.dat, then the next execution of the browser would have invoked the profile manager for you. This is not a problem the users will ever encounter since they don't go throwing away their profile directory when they upgrade to a new version. But if it is a problem, it's a general browser problem and not a wallet one. Closing this report out as invalid.
Agreed this is an error case for profiles not existing. Still we shouldn't crash. We should detect that and trigger the profile manager. Is this a crash in wallet or profile code. If this is in wallet, I steve should still protect against the failure case and then reassign the bug to profile folks. Am I mistaken ?
This is not a wallet issue. Kevin didn't include a stack trace but, if he did, I'm sure you would see the crash was at a lower level than wallet where some unprotected code was trying to accessing a non-existent directory. If Kevin could provide us with the stack trace, I will re-open this and assign it to the appropriate group.
There is already bug 9600 on the fact the the profile manager does not do the right thing when you delete your profile directory but don't delete mozregistry.dat, which points to the profile directory. So if I understand it correctly, this bug is a duplicate of that one. Please confirm.
paulmac correctly indicates that bug 9600 also addresses this issue. So this bug could be considered to be a duplicate of that one if you like. I guess I should have been clearer as to why I was marking this as invalid. I agree that anything that causes a crash is serious and should be fixed. It's just that this bug was specifically addressing wallet and as such was invalid. The correct bug is one that addresses the profile code and that is what 9600 is doing.
Status: RESOLVED → REOPENED
Status: REOPENED → RESOLVED
Closed: 26 years ago → 26 years ago
Resolution: INVALID → DUPLICATE
*** This bug has been marked as a duplicate of 9600 ***
Status: RESOLVED → VERIFIED
verified as a dup
Product: Core → Toolkit
QA Contact: paulmac → form.manager
You need to log in before you can comment on or make changes to this bug.