Closed
Bug 21697
Opened 25 years ago
Closed 25 years ago
Cancel on Password Cache
Categories
(SeaMonkey :: Passwords & Permissions, defect, P3)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: sterling, Assigned: morse)
References
()
Details
Logged into Novell GroupWise WebAccess and Mozilla asked me if I wanted to enable password caching. I clicked 'Cancel' (a poorly labled button, if you ask me) and it crashed Mozilla.
Assignee | ||
Comment 1•25 years ago
|
||
The poorly-labelled button is temporary -- awaiting completion of a Yes/No dialog box (see bug 12728) The crash is surprising. This had been working and indeed works on the last tree that I built. But that was over a week ago so I'm pulling a new tree and will try it. If it still works for me, then this may have been a non-reproducible crash (too bad you didn't get a stack trace) for which there's not much we can do at this time.
Status: NEW → ASSIGNED
Reporter | ||
Comment 2•25 years ago
|
||
I don't know if this will help, but this is the CPU dump from the Close Program box. I can reproduce the error if I delete the User50 folder, restart mozilla, log into WebAccess and hit Cancel again. MOZILLA caused an invalid page fault in module GKHTML.DLL at 023f:00f6f6fa. Registers: EAX=00000000 CS=023f EIP=00f6f6fa EFLGS=00010246 EBX=80000000 SS=0247 ESP=0063ed88 EBP=0063f024 ECX=0063f014 DS=0247 ESI=01d82ef0 FS=7b3f EDX=0063f008 ES=0247 EDI=60b3679d GS=0000 Bytes at CS:EIP: 8b 08 ff 51 24 6a ff 6a 00 68 58 00 fa 00 8d 8d Stack dump: 00000000 0063f008 00f7a544 00000000 017a93d0 60b3f873 0063ee56 00f9cc0c 0000003f 00000000 00000040 01e1ac70 006d7d54 00000000 bff7b9b6 816b3a68
Assignee | ||
Comment 3•25 years ago
|
||
No, that CPU dump doesn't help. But the fact that you say it is reproducible is encouraging -- that means we can debug it. I'll look further as soon as my build finishes. BTW, you probably don't need to delete your entire user50 folder. Just removing the signon.Notified entry from your prefs.js file is all you need to do in order to force the dialog to occur again.
Reporter | ||
Comment 4•25 years ago
|
||
I did assumed that the signon.notify entry in prefs.js was the line to remove and so I removed it, but it didn't seem to help. I may be mistaken though. I don't mind deleting the folder anyway, I'm only trying Mozilla out to see what kind of CSS/HTML/XML support it will have.
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Comment 5•25 years ago
|
||
My build finished and I tested it. It does not crash for me. I deleted the entire profile directory and even threw away my mozregistry.dat file. Then I started the browser. Got to a page that asked for a password. Supplied one and then I got to the dialog that asks if I want the password-saving feature enabled. I pressed cancel. The browser did not crash -- it continued executing normally. I have no choice but to close this bug out as works-for-me. If Sterling can provide the url of an actual site (external to his firewall) that is demonstrating the problem, I'll check again. Also, how recent is the browser that you are running?
Comment 6•25 years ago
|
||
Bulk move to Single Signon component, which has subsumed Password Cache.
Component: Password Cache → Single Signon
Updated•20 years ago
|
Product: Browser → Seamonkey
Comment hidden (collapsed) |
You need to log in
before you can comment on or make changes to this bug.
Description
•