Closed
Bug 17984
Opened 26 years ago
Closed 26 years ago
With psm.exe loaded, Mozilla crashes on exit.
Categories
(Core :: Security, defect, P3)
Tracking
()
VERIFIED
INVALID
People
(Reporter: junruh, Assigned: dougt)
Details
1.) Start psm.exe from the command line, then Mozilla.
2.) Visit a few secure sites, then exit Mozilla.
What happens: Mozilla crashes. Here is a list of suggested sites.
https://www.amazon.com/exec/obidos/account-access-login2/002-3506636-6665013
https://www.amazon.co.uk/exec/obidos/account-access-login2/026-8793701-3491657
https://www.amazon.de/exec/obidos/account-access-login2/028-8569013-7493439
https://www.angelstouch.com
https://www.bankofamerica.com
https://www.bbvnet.com/bbvnet
https://www.borders.com
https://enigma.barclaycard.co.uk
https://ez.ic3.com/pages/borlandco/inprise/order.htm?borlandco+CPB17
Reporter | ||
Updated•26 years ago
|
QA Contact: dshea → junruh
Assignee | ||
Comment 1•26 years ago
|
||
are you using the psm that come with the 5.0 install? Is there a stack crawl?
Updated•26 years ago
|
Severity: normal → critical
Reporter | ||
Comment 2•26 years ago
|
||
Yes, I am using the psm.exe that comes with Seamonkey. I don't know what a stack
crawl is, but this is still happening with the 11/9 build.
Reporter | ||
Comment 3•26 years ago
|
||
I have included the stack trace:
nsEventListenerManager::HandleEvent
[d:\builds\seamonkey\mozilla\layout\events\src\nsEventListenerManager.cpp, line
830]
nsXULDocument::HandleDOMEvent
[d:\builds\seamonkey\mozilla\rdf\content\src\nsXULDocument.cpp, line 1645]
nsXULElement::HandleDOMEvent
[d:\builds\seamonkey\mozilla\rdf\content\src\nsXULElement.cpp, line 2576]
nsXULElement::HandleDOMEvent
[d:\builds\seamonkey\mozilla\rdf\content\src\nsXULElement.cpp, line 2569]
nsXULElement::HandleDOMEvent
[d:\builds\seamonkey\mozilla\rdf\content\src\nsXULElement.cpp, line 2569]
nsXULElement::HandleDOMEvent
[d:\builds\seamonkey\mozilla\rdf\content\src\nsXULElement.cpp, line 2569]
nsXULElement::HandleDOMEvent
[d:\builds\seamonkey\mozilla\rdf\content\src\nsXULElement.cpp, line 2569]
GlobalWindowImpl::HandleDOMEvent
[d:\builds\seamonkey\mozilla\dom\src\base\nsGlobalWindow.cpp, line 2961]
nsDocument::HandleDOMEvent
[d:\builds\seamonkey\mozilla\layout\base\src\nsDocument.cpp, line 2369]
nsHTMLHtmlElement::HandleDOMEvent
[d:\builds\seamonkey\mozilla\layout\html\content\src\nsHTMLHtmlElement.cpp, line
193]
PresShell::HandleEvent
[d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 2412]
nsView::HandleEvent [d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 838]
nsView::HandleEvent [d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 823]
nsView::HandleEvent [d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 823]
nsView::HandleEvent [d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 823]
nsViewManager::DispatchEvent
[d:\builds\seamonkey\mozilla\view\src\nsViewManager.cpp, line 1743]
HandleEvent [d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 67]
nsWindow::DispatchEvent
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 411]
nsWindow::DispatchWindowEvent
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 428]
nsWindow::DispatchKeyEvent
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 2056]
nsWindow::OnKeyDown
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 2261]
nsWindow::ProcessMessage
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 2607]
KERNEL32.DLL + 0x41fb (0xbff741fb)
0xc29bcc44
Reporter | ||
Updated•26 years ago
|
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → INVALID
Reporter | ||
Comment 4•26 years ago
|
||
Marking invalid. After some more testing, it is apparent that SilkTest is what
is crashing mozilla, not the fact that psm.exe is loaded.
Reporter | ||
Updated•26 years ago
|
Status: RESOLVED → VERIFIED
Reporter | ||
Comment 5•26 years ago
|
||
Verified invalid.
Bulk moving all Browser Security bugs to new Security: General component. The
previous Security component for Browser will be deleted.
Component: Security → Security: General
You need to log in
before you can comment on or make changes to this bug.
Description
•