Closed Bug 47448 Opened 25 years ago Closed 25 years ago

mozilla hangs and then crashes if you click the security icon (bottom right)

Categories

(Core Graveyard :: Security: UI, defect, P3)

1.0 Branch
x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: bar_kelly, Assigned: ddrinan0264)

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; m18) Gecko/20000802 BuildID: 2000080220 I have found that mozilla fails to respond and eventually crashes due to an access violation caused in psm.exe when you click on the security icon (the open lock at the bottom right hand corner). The problem seems to happen repeatedly. Reproducible: Always Steps to Reproduce: 1.Click on the security icon 2.wait . . . 3. Actual Results: program crashed Expected Results: Opened the psm
On linux 2000080108 I get this message on the console: JavaScript error: line 0: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsSecureBrowserUI.displayPageInfoUI]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://communicator/content/securityUI.js :: displayPageInfo :: line 43" data: no] But mozilla does not crash or lose stability.
Summary: mozilla hangs and then crashes if you click the security icon (bottom right) → mozilla hangs and then crashes if you click the security icon (bottom right)
->Crypto.
Assignee: mstoltz → ddrinan
Component: Security: General → Security: Crypto
QA Contact: czhang → junruh
Worksforme. I'm not getting crashes with any build. Presently using Mozilla 080820 with PSM 1.1. PSM 1.2 beta with the same Mozilla build doesn't crash either.
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Verified worksforme.
Status: RESOLVED → VERIFIED
Mass changing Security:Crypto to PSM
Component: Security: Crypto → Client Library
Product: Browser → PSM
Version: other → 2.1
Mass changing Security:Crypto to PSM
Product: PSM → Core
Version: psm2.1 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.