275892 - After importing client certificate, viewing certificates would crash firefox.

Status: RESOLVED EXPIRED

(Firefox :: Settings UI, defect)

Description

[Yen-Wei Liu]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

After generating and importing client certificates, or importing other
certificates, immediately viewing certificates would crash Firefox. A reboot
would bring everything back to normal, however.

Reproducible: Always

Steps to Reproduce:
1.Generate client certificate (via <KEYGEN>) and import it. Or import other
certificates.
2. Close any preference window. Or even close Firefox then re-run firefox.
3. Go to tools->preferences->Advanced -> Manage Certificates


Actual Results:  
Firefox GPF'ed.

Comment 1

[Jean-Marc Desperrier]

I can not reproduce with Firefox 1.0, that you used according to the user agent,
by importing a pkcs#12 files neither under win2000, nor Win 98 SE.

Are the certificates used for your testing test only certificates ? If so, can
you attach one to the bug entry ?

It's strange that rebooting changes anything wrt just restarting Firefox.
Firefox 1.0 does not have the "keep in memory" option ?

What happens with a fresch profile ?

Comment 2

[Jean-Marc Desperrier]

Yen-Wei Liu, it's great that you report a problem, but here we do need more
info, or this bug will never progress.

Comment 3

[Yen-Wei Liu]

Hi,

I still struggle to find some way to do more testing on my production win98 box.
When I have more progress, I sure will post here. Thanks for your attention !!

Comment 4

[OstGote!]

I guess it is related to bug 225034. See bug 225034 comment 20 for details. I
had recently the same problem with Mozilla 1.8b, see bug 225034 comment 28. For
the first time after import (without restart) I crash if I want to view the
certificates. Later (after restart) it works. This was not with previously
installed certificates. Crash stack was the same as for bug 225034.

Comment 5

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 6

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.

Comment 7

[Mike Connor [:mconnor]]

sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs,
filter on "beltznerLovesGoats" to get rid of this mass change