90362 - crash on opening an https:// web site [@ nsScriptLoader::EvaluateScript]

Status: VERIFIED WORKSFORME

(Core :: Layout, defect)

Description

[Madhur Bhatia]

When I am directed to a secure site, the browser crashes

Buiild ID : 20010711-0.9.2 branch build, 20010711-07-trunk build
OS : win2000

steps to reproduce:
1. go to  http://www.aeacu.com
2. click on "My account"
3. click on "login to 24x7 Banking"

actual:
you are directed to a secure document - https://.....
the browser crashes immidiately

reproducible always.
Note: I do not see the crash in yesterday's build.

Comment 1

[Chris Hiner]

It crashed for me on on the "are you sure you have a secure browser" page, using
a linux tip build from around 1pm EDT.
I'll attach the stack.

Comment 2

[Chris Hiner]

Attachment: Linux stack

Comment 3

[timeless]

vidur owns the top of the stack..

Comment 4

[Madhur Bhatia]

RTM build id : 20010719 window2000

I am still experiencing a crash when i try to access a secure site. 

steps to reproduce:
1. go to  http://www.aeacu.com
2. click on "My account"
3. this time i clicked on "24x7 Banking Help" or "Enroll for 24x7 Banking"

actual:
the browser crashed when i click OK to the dialog box stating "You have 
requested a secure document...."

This time i did not experience any crash upon clicking "login to 24x7 login".

NOTE: 
The crash occurs only in some secure sites (like the one stated above). I tried 
to go to other secure sites and did not experience any crash. For Eg. i went to  
http://www.home.com/ready.html - entered information and clicked on submit .... 
I was taken to a secure site  - i did not experience a crash here.
it actually does not happen with all the https:// sites.

Comment 5

[lchiang]

Does this happen to all secure sites or this particular one?

Comment 6

[Madhur Bhatia]

this problem is only on this particular site. I tried to access a few 
other secure sites and they were working fine. 

I tested this website- www.aeacu.com on linux and macOS 8.6 as well. 
Linux - no crash
Mac - i see a crash
window2000 - it crashes

Comment 7

[Madhur Bhatia]

adding the stack trace :-

Stack Trace
0x02cbf040
PresShell::`scalar deleting destructor'
nsTextInputListener::Release 
[d:\builds\seamonkey\mozilla\layout\html\forms\src\nsGfxTextControlFrame2.cpp, 
line 235]
nsCOMPtr_base::~nsCOMPtr_base 
[d:\builds\seamonkey\mozilla\xpcom\base\nsCOMPtr.cpp, line 50]
GlobalWindowImpl::Focus 
[d:\builds\seamonkey\mozilla\dom\src\base\nsGlobalWindow.cpp, line 1783]
nsEventStateManager::PreHandleEvent 
[d:\builds\seamonkey\mozilla\content\events\src\nsEventStateManager.cpp, line 
594]
PresShell::HandleEventInternal 
[d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 5561]
PresShell::HandleEvent 
[d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 5493]
nsView::HandleEvent [d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 377]
nsViewManager::DispatchEvent 
[d:\builds\seamonkey\mozilla\view\src\nsViewManager.cpp, line 2056]
HandleEvent [d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 68]
nsWindow::DispatchEvent 
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 724]
nsWindow::DispatchWindowEvent 
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 741]
nsWindow::DispatchFocus 
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 4429]
nsWindow::ProcessMessage 
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 3345]
nsWindow::WindowProc 
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 989]
USER32.DLL + 0x3eb0 (0x77e13eb0)
USER32.DLL + 0x591b (0x77e1591b)
USER32.DLL + 0x595d (0x77e1595d)
ntdll.dll + 0x1fb83 (0x77f9fb83)
GlobalWindowImpl::Focus 
[d:\builds\seamonkey\mozilla\dom\src\base\nsGlobalWindow.cpp, line 1773]
nsWebShellWindow::HandleEvent 
[d:\builds\seamonkey\mozilla\xpfe\appshell\src\nsWebShellWindow.cpp, line 530]
nsWindow::DispatchEvent 
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 724]
nsWindow::DispatchWindowEvent 
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 741]
nsWindow::DispatchFocus 
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 4429]
nsWindow::ProcessMessage 
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 3341]
nsWindow::WindowProc 
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 989]
USER32.DLL + 0x3eb0 (0x77e13eb0)
USER32.DLL + 0x591b (0x77e1591b)
USER32.DLL + 0x595d (0x77e1595d)
ntdll.dll + 0x1fb83 (0x77f9fb83)
USER32.DLL + 0x69a7 (0x77e169a7)
USER32.DLL + 0x3eb0 (0x77e13eb0)
USER32.DLL + 0x6469 (0x77e16469)
USER32.DLL + 0xa6f8 (0x77e1a6f8)
nsWindow::WindowProc 
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 1000]
USER32.DLL + 0x3eb0 (0x77e13eb0)
USER32.DLL + 0x591b (0x77e1591b)
USER32.DLL + 0x595d (0x77e1595d)
ntdll.dll + 0x1fb83 (0x77f9fb83)
nsWebShellWindow::Destroy 
[d:\builds\seamonkey\mozilla\xpfe\appshell\src\nsWebShellWindow.cpp, line 1744]
nsChromeTreeOwner::Destroy 
[d:\builds\seamonkey\mozilla\xpfe\appshell\src\nsChromeTreeOwner.cpp, line 228]
GlobalWindowImpl::ReallyCloseWindow 
[d:\builds\seamonkey\mozilla\dom\src\base\nsGlobalWindow.cpp, line 2395]
GlobalWindowImpl::CloseWindow 
[d:\builds\seamonkey\mozilla\dom\src\base\nsGlobalWindow.cpp, line 3163]
nsJSContext::ScriptEvaluated 
[d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp, line 1367]
nsJSContext::CallEventHandler 
[d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp, line 949]
nsJSEventListener::HandleEvent 
[d:\builds\seamonkey\mozilla\dom\src\events\nsJSEventListener.cpp, line 140]
nsEventListenerManager::HandleEventSubType 
[d:\builds\seamonkey\mozilla\content\events\src\nsEventListenerManager.cpp, line 
1162]
nsEventListenerManager::HandleEvent 
[d:\builds\seamonkey\mozilla\content\events\src\nsEventListenerManager.cpp, line 
2134]
nsXULElement::HandleDOMEvent 
[d:\builds\seamonkey\mozilla\content\xul\content\src\nsXULElement.cpp, line 
3635]
PresShell::HandleDOMEventWithTarget 
[d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 5614]
nsButtonBoxFrame::MouseClicked 
[d:\builds\seamonkey\mozilla\layout\xul\base\src\nsButtonBoxFrame.cpp, line 181]
nsButtonBoxFrame::HandleEvent 
[d:\builds\seamonkey\mozilla\layout\xul\base\src\nsButtonBoxFrame.cpp, line 128]
PresShell::HandleEventInternal 
[d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 5583]
PresShell::HandleEventWithTarget 
[d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 5538]
nsEventStateManager::CheckForAndDispatchClick 
[d:\builds\seamonkey\mozilla\content\events\src\nsEventStateManager.cpp, line 
2465]
nsEventStateManager::PostHandleEvent 
[d:\builds\seamonkey\mozilla\content\events\src\nsEventStateManager.cpp, line 
1551]
PresShell::HandleEventInternal 
[d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 5587]
PresShell::HandleEvent 
[d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 5493]
nsView::HandleEvent [d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 377]
nsViewManager::DispatchEvent 
[d:\builds\seamonkey\mozilla\view\src\nsViewManager.cpp, line 2056]
HandleEvent [d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 68]
nsWindow::DispatchEvent 
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 724]
nsWindow::DispatchWindowEvent 
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 741]

Comment 8

[lchiang]

Madhur - search the bugzilla database for other instances of
"nsGfxTextControlFrame2.cpp" in the description to see if there are any similar
dupes to this.  That may help seeing what it is on this page that may be causing
the problem.  I don't think it has to do with https:

Comment 9

[Madhur Bhatia]

this bug looks similar to bug 88120 and bug 88613
I was able to reproduce these bugs. the crash happened on similar grounds - when 
the site is getting directed to a secure site.

Comment 10

[vidur (gone)]

I can't reproduce this on the 7/23 branch build. Please verify that this bug
still exists.

Comment 11

[vidur (gone)]

Sorry, I was able to reproduce this. SSL warnings had to be turned on to get the
"You have entered a secure site..." dialog. 

Comment 12

[vidur (gone)]

I'm in the process of pulling a commercial tree to debug. The original Linux
stack (the one that caused this bug to get assigned to me) is bogus. Since it
isn't clear who the appropriate owner would be based on the Windows stack
included (saari?), I'll do some more investigation.

Comment 13

[selmer (gone)]

Jay, Shiva, is this showing up in the talkback?

Comment 14

[Jay Patel [:jay]]

This hasn't shown up in the topcrash reports, but there are a few entries in the
Talkback database:

http://climate/reports/searchstacksignature.cfm?stacksig=nsScriptLoader%3A%3AEvaluateScript

Comment 15

[hico2]

Seems there wasn't much activity here lately. I didn't find other similar bugs,
so please correct me if this is not the right place to report.

What I see is mozilla crash (memory at 0x00000 couldn't be read) when trying to
open a https:// page. I use recent builds on WinNT, tried it also with today's
talkback and sent the report. The page is https://mail.fphil.uniba.sk, and I'm
its webmaster, so I can do more testing if you tell me what to look for.

Comment 16

[Dmitri Alexeev]

I am experiencing a crash when i try to access a secure site:
https://my.advance.de

As a developer of this site, I could test it with 
nonsecure connection. Result: all is absolutely ok.

Comment 17

[lchiang]

talkback folks - can you get the talkback reports recently submitted and see if
the stack trace is the same one which Madhur filed?

Comment 18

[Jay Patel [:jay]]

lisa:  do you mean the stack from 7/20/01?  it might be hard to find other
crashes with that stack b/c the stack signature is not a normal one.  does
anyone have a more recent incident we can use as a reference?

Comment 19

[vidur (gone)]

Reassigning to [e-mail]. I do not own the DOM.

Comment 20

[Adam Hardy]

I had 0.9.7 and was getting this bug until today. Moz was crashing as soon as I
typed in the URL and hit enter. I was trying to get to www.joker.com.

I saw this bug and then saw 0.9.8 was out, so I downloaded it. The crash has
gone. I now don't have to use IE to access joker.com

On nt4 sp6. Could have been a setting? I didn't change anything on the security
options after installing 0.9.7 or 0.9.8.

Hope it helps. 

Mozilla roolz, 

Peace
Adam

Comment 21

[Jay Patel [:jay]]

Adam:  I looked up your crashes and the ones you experienced at www.joker.com
were actually bug 114292.  That crash was fixed on 1/18 for M098.  I don't think
they're related to this crash.

Comment 22

[Heikki Toivonen (remove -bugzilla when emailing directly)]

Moving nsbeta1+ to 1.0

Comment 23

[Heikki Toivonen (remove -bugzilla when emailing directly)]

Worksforme, Win2k opt build from today.

Comment 24

[Chris Petersen]

Marking verified wfm in the April 12th Windows ME trunk build (2002-04-12-10).