146014 - steps to crash browser [@ nsEventStateManager::SendFocusBlur]

Status: VERIFIED WORKSFORME

(Core :: DOM: Events, defect)

Description

[Ajay Gautam]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.0.0+) Gecko/20020514
BuildID:    2002051408

Non required

Reproducible: Always
Steps to Reproduce:
1. Goto
http://www.kohls.com/products/product_page_multiple1.jsp?PRODUCT%3C%3Eprd_id=9178799&FOLDER%3C%3EbrowsePath=11362103&FOLDER%3C%3EbrowsePath=11362143&FOLDER%3C%3EbrowsePath=12818249&FOLDER%3C%3Efolder_id=12818249&bmUID=1022006361457&WebLogicSession=POqUS51TA1tyzIKrw8ds9xtJdtqiUqUG9221DKf4TZS1uQjVGACO|761636131130864843/167888907/5/7005/7005/7002/7002/-1|445514588872443097/167888921/5/7005/7005/7002/7002/-1|761636131130869794
2. scroll down to where it shows price
3. On the left of price, click on the link: "Trifari® Heart Birthstone Charm"
4. A new window opens, showing the item.
5. Click on the "Close" link in the new window

Actual Results:  browser crash

Expected Results:  well, should not crash :)

tried 3 times - crashed always. IE 6 does not crashes (tried once)

Comment 1

[Michael Lefevre]

confirming because it crashed for me too, but clicking on the window that had
popped up (or possibly after a slight delay)

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0+) Gecko/20020519
build 2002051908

talkback ID TB6517181G

not sure of correct component.

Comment 2

[[e-mail] (gone - use [e-mail] instead)]

nsEventStateManager::SendFocusBlur [nsEventStateManager.cpp, line 3848]
nsEventStateManager::SetContentState [nsEventStateManager.cpp, line 3574]
nsGenericHTMLElement::HandleDOMEventForAnchors [nsGenericHTMLElement.cpp, line 1447]
nsHTMLAnchorElement::HandleDOMEvent [nsHTMLAnchorElement.cpp, line 431]
nsGenericDOMDataNode::HandleDOMEvent [nsGenericDOMDataNode.cpp, line 903]
PresShell::HandleEventInternal [nsPresShell.cpp, line 6122]
PresShell::HandleEvent [nsPresShell.cpp, line 6040]
nsViewManager::HandleEvent [nsViewManager.cpp, line 2076]
nsView::HandleEvent [nsView.cpp, line 306]
nsViewManager::DispatchEvent [nsViewManager.cpp, line 1887]
HandleEvent [nsView.cpp, line 83]
nsWindow::DispatchEvent [nsWindow.cpp, line 893]
nsWindow::DispatchWindowEvent [nsWindow.cpp, line 910]
nsWindow::DispatchMouseEvent [nsWindow.cpp, line 4756]
ChildWindow::DispatchMouseEvent [nsWindow.cpp, line 5011]
nsWindow::ProcessMessage [nsWindow.cpp, line 3658]
nsWindow::WindowProc [nsWindow.cpp, line 1155]
USER32.DLL + 0x1b60 (0x77e11b60)
USER32.DLL + 0x1cca (0x77e11cca)
USER32.DLL + 0x83f1 (0x77e183f1)
nsAppShellService::Run [nsAppShellService.cpp, line 451]
main1 [nsAppRunner.cpp, line 1472]
main [nsAppRunner.cpp, line 1808]
WinMain [nsAppRunner.cpp, line 1826]
WinMainCRTStartup()
KERNEL32.DLL + 0xd326 (0x77e8d326) 

Comment 3

[Ajay Gautam]

Does not crash if the new (small) window is closed by click on the "X" (close
window icon) on the top right corner of the title bar

Thanks

Ajay

Comment 4

[R.K.Aa.]

this is very similar to the stack in bug 53763, fixed over a year and a  half ago

Comment 5

[Mason]

WFM Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0rc2) Gecko/2002051006

Comment 6

[joakim_46]

WFM with build 2002051006 under Windows ME.

Comment 7

[Matthias Versen [:Matti]]

-> Events

Comment 8

[Andrew Schultz]

also crashes linux build 20020520.  branch build is fine.
regression between builds 2002041621 and 2002041707

Comment 9

[Andrew Schultz]

Attachment: testcase

need a link with onmousedown=top.close() to crash.

Comment 10

[Andrew Schultz]

worksforme on the testcase with linux trunk build 20020817
the URL has changed somewhat, but other links on the page open a new window with
a "Close" link.  doing that worked as well.

Comment 11

[Adam Hauner]

Testcase WFM 2002081612/trunk/W2K

Comment 12

[Michael Lefevre]

WFM 2002081716/1.1branch/win2k.

reporter (Ajay): can you reproduce this bug with a recent build of mozilla? if
not, please resolve this bug as WORKSFORME. otherwise, please comment with
details. thanks.

Comment 13

[Ajay Gautam]

Hello,

I tried this with 2002072408 and it worked fine. Resolved as requested.

I guess, this was related to the "OnClose()" bug, which was fixed earlier.

Thanks a ton guys,

Ajay Gautam

Comment 14

[Michael Lefevre]

i think you're probably right. thanks for getting back.

verified.