207835 - Mozilla freezes when using fucntionality of this page.

Status: RESOLVED INCOMPLETE

(Core :: DOM: Core & HTML, defect)

Description

[David Bobroff]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030529
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030529

This page is for tracking lost luggage.  When a reference number and name are
entered into their respective fields and "start query" button is clicked a new
window pops up (as it should) but then Mozilla freezes.  It works with, ahem,
Internet Explorer.  The example number/name will demonstrate the problem.

Reproducible: Always

Steps to Reproduce:
1. Go to http://www.globeground.com/en/pub/services/lostluggage.cfm
2. Fill in the example values given.
3. Click "start query"

Actual Results:  
New window pops up.  Nothing fills new window.  Mozilla is now "not responding"
according to Windows Task Manager.

Expected Results:  
New window should have displayed results of lost baggage search.

Using the example values should return saying that it cannot find a valid file
for your entry.  Using a real value gave me information about a real lost bag
(in Internet Explorer), but froze Mozilla.

Comment 1

[Kai Lahmann (is there, where MNG is)]

same with FB0.6 on Linux!

Comment 2

[me]

This page hard locks the browser too:

http://www.thebigbikebook.co.uk/order.asp?Page=/clothing.asp&section=2&subsection=9&Price=0&Start=1&Keyword=&SearchDescription=&Zone=&product=1217

Comment 3

[Dan Backes]

Confirmed 2003053008 winXP

Comment 4

[Mats Palmgren (inactive)]

Bug occurs in trunk Linux 2003-05-30-08 and in Mozilla 1.0.2

Comment 5

[Mats Palmgren (inactive)]

Attachment: Testcase #1

This is what all those CPU-cycles are doing:
while (popupWindow.frames.length < 2){;}

Comment 6

[Mats Palmgren (inactive)]

Looks like bug 135793

Comment 7

[Wayne Mery (:wsmwk)]

(In reply to comment #6)
> Looks like bug 135793

still see this problem, but bug 135793 (which references a related? issue bug 226711) fixed ~2003-11-25

Comment 8

[Wayne Mery (:wsmwk)]

it now goes to "unresponsive script"

Comment 9

[Wayne Mery (:wsmwk)]

testcase gone