Closed Bug 116206 Opened 23 years ago Closed 21 years ago

FIFA site crashes mozilla

Categories

(Core :: DOM: Events, defect, P1)

x86
All
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: u32858, Assigned: joki)

References

()

Details

(Keywords: crash, testcase)

Attachments

(3 files)

From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20010914 BuildID: 2001092020 Go to that page and it either crashes imediatly or when you click on "other" in the new user section in the middle of the page not sure if this is significant but i get this error when running form command line, even though shockwave.com works fine $ mozilla LoadPlugin: failed to initialize shared library /usr/lib/netscape/plugins/ShockwaveFlash.class [/usr/lib/netscape/plugins/ShockwaveFlash.class: invalid ELF header] is there a way to get more debug output from mozilla? i looked on mozilla --help but there is not Reproducible: Always Steps to Reproduce: 1.go to the site 2.wait, or click "other" country 3.see it give a segmentation fault
WorksForMe on Linux 0.9.7 branch 2001122908. Your build is a bit old, chances are good that this already has been fixed. Could you try a new buil? Thanks for testing mozilla.
WFM 2001121909/WinNT4 Correcting URL, Key: +crash
WFM, trunk build 2001-12-19-08 on Linux.
WFM on Linux 0.9.7 branch 2001121808.
WFM. Build ID: 2001 12 18 03. Windows 2000.
I crash too, win98SE, 2001121803 Talkback ID : TB714737M Confirming, OS->All.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
OK, I've just had a very cautious poke around the source, and it looks like they're in need of some heavy-duty tech evangelism, too. I'll log a separate bug for that. Meantime, I think it should be noted that this is a very high-profile site: this is the website to apply for tickets to the 2002 football (soccer) world cup.
This crashes for me on Solaris too, with nightly 20011219, but only after I have clicked on one of the languages in the header (which don't look like links), and then click on say, the 'other' option in the middle of the page, or one of the language links at the bottom.
asa, any idea which component/engr this should go to? pchen no longer works here... plugins? talkback info: MSVCRT.DLL + 0xd377 (0x7800d377) MSVCRT.DLL + 0xcc7f (0x7800cc7f) MSVCRT.DLL + 0x12d9 (0x780012d9) js_NewObjectMap [d:\builds\seamonkey\mozilla\js\src\jsobj.c, line 1564] js_NewObject [d:\builds\seamonkey\mozilla\js\src\jsobj.c, line 1646] JS_NewObject [d:\builds\seamonkey\mozilla\js\src\jsapi.c, line 1994] XPCWrappedNative::Init [d:\builds\seamonkey\mozilla\js\src\xpconnect\src\xpcwrappednative.cpp, line 713] XPCWrappedNative::GetNewOrUsed [d:\builds\seamonkey\mozilla\js\src\xpconnect\src\xpcwrappednative.cpp, line 349] XPCConvert::NativeInterface2JSObject [d:\builds\seamonkey\mozilla\js\src\xpconnect\src\xpcconvert.cpp, line 835] nsXPConnect::WrapNative [d:\builds\seamonkey\mozilla\js\src\xpconnect\src\nsXPConnect.cpp, line 502] nsJSEventListener::HandleEvent [d:\builds\seamonkey\mozilla\dom\src\events\nsJSEventListener.cpp, line 166] nsEventListenerManager::HandleEventSubType [d:\builds\seamonkey\mozilla\content\events\src\nsEventListenerManager.cpp, line 1203] nsEventListenerManager::HandleEvent [d:\builds\seamonkey\mozilla\content\events\src\nsEventListenerManager.cpp, line 2195] nsXULElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\xul\content\src\nsXULElement.cpp, line 3427] nsXULCommandDispatcher::UpdateCommands [d:\builds\seamonkey\mozilla\content\xul\document\src\nsXULCommandDispatcher.cpp, line 381] GlobalWindowImpl::UpdateCommands [d:\builds\seamonkey\mozilla\dom\src\base\nsGlobalWindow.cpp, line 2588] nsFocusController::UpdateCommands [d:\builds\seamonkey\mozilla\dom\src\base\nsFocusController.cpp, line 138] nsFocusController::SetFocusedElement [d:\builds\seamonkey\mozilla\dom\src\base\nsFocusController.cpp, line 111] nsFocusController::Blur [d:\builds\seamonkey\mozilla\dom\src\base\nsFocusController.cpp, line 318] nsEventListenerManager::HandleEvent [d:\builds\seamonkey\mozilla\content\events\src\nsEventListenerManager.cpp, line 1694] nsWindowRoot::HandleChromeEvent [d:\builds\seamonkey\mozilla\dom\src\base\nsWindowRoot.cpp, line 182] GlobalWindowImpl::HandleDOMEvent [d:\builds\seamonkey\mozilla\dom\src\base\nsGlobalWindow.cpp, line 632] nsXULDocument::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\xul\document\src\nsXULDocument.cpp, line 2437] nsXULElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\xul\content\src\nsXULElement.cpp, line 3415] nsXULElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\xul\content\src\nsXULElement.cpp, line 3408] nsXULElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\xul\content\src\nsXULElement.cpp, line 3408] nsXULElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\xul\content\src\nsXULElement.cpp, line 3408] nsXULElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\xul\content\src\nsXULElement.cpp, line 3408] nsXULElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\xul\content\src\nsXULElement.cpp, line 3408] nsXULElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\xul\content\src\nsXULElement.cpp, line 3408] nsXULElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\xul\content\src\nsXULElement.cpp, line 3408] nsXULElement::HandleChromeEvent [d:\builds\seamonkey\mozilla\content\xul\content\src\nsXULElement.cpp, line 4634] GlobalWindowImpl::HandleDOMEvent [d:\builds\seamonkey\mozilla\dom\src\base\nsGlobalWindow.cpp, line 632] nsDocument::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\base\src\nsDocument.cpp, line 3058] nsGenericElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\base\src\nsGenericElement.cpp, line 1854] nsGenericElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\base\src\nsGenericElement.cpp, line 1848] nsGenericElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\base\src\nsGenericElement.cpp, line 1848] nsHTMLFormElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\html\content\src\nsHTMLFormElement.cpp, line 498] nsGenericElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\base\src\nsGenericElement.cpp, line 1848] nsGenericElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\base\src\nsGenericElement.cpp, line 1848] nsGenericElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\base\src\nsGenericElement.cpp, line 1848] nsGenericElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\base\src\nsGenericElement.cpp, line 1848] nsGenericElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\base\src\nsGenericElement.cpp, line 1848] nsGenericElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\base\src\nsGenericElement.cpp, line 1848] nsGenericElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\base\src\nsGenericElement.cpp, line 1848] nsGenericElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\base\src\nsGenericElement.cpp, line 1848] nsGenericElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\base\src\nsGenericElement.cpp, line 1848] nsGenericElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\base\src\nsGenericElement.cpp, line 1848] nsGenericElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\base\src\nsGenericElement.cpp, line 1848] nsGenericElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\base\src\nsGenericElement.cpp, line 1848] nsGenericElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\base\src\nsGenericElement.cpp, line 1848] nsGenericElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\base\src\nsGenericElement.cpp, line 1848] nsGenericElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\base\src\nsGenericElement.cpp, line 1848] nsGenericElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\base\src\nsGenericElement.cpp, line 1848] nsGenericElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\base\src\nsGenericElement.cpp, line 1848] nsGenericElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\base\src\nsGenericElement.cpp, line 1848] nsGenericElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\base\src\nsGenericElement.cpp, line 1848] nsGenericElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\base\src\nsGenericElement.cpp, line 1848] nsGenericElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\base\src\nsGenericElement.cpp, line 1848] nsHTMLInputElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\html\content\src\nsHTMLInputElement.cpp, line 1150] nsEventStateManager::SendFocusBlur [d:\builds\seamonkey\mozilla\content\events\src\nsEventStateManager.cpp, line 3533] nsEventStateManager::SetContentState [d:\builds\seamonkey\mozilla\content\events\src\nsEventStateManager.cpp, line 3304] nsHTMLInputElement::SetFocus [d:\builds\seamonkey\mozilla\content\html\content\src\nsHTMLInputElement.cpp, line 745] nsGenericHTMLElement::SetElementFocus [d:\builds\seamonkey\mozilla\content\html\content\src\nsGenericHTMLElement.cpp, line 4334]
Assignee: pchen → asa
Component: XP Apps → Browser-General
QA Contact: sairuh → doronr
WFM, Linux trunk build 2001121921, plugin "Shockwave Flash 5.0 r47" installed.
Now WFM, Win98SE, 2001121909 (BTW, I've logged 116229 about the lack of standard DOM support on this site)
More of a note, but anyway it works fine on netscape, till i saw i need my passport number anyway :) is it possible to add a --debug-printf option to the mozilla command line? it would be SO useful to see whats really going on in there. JG
my guess is the context or something is bad. cc brendan since he has touched some code near the victimized functions and can probably help whomever was causing the crash. [or he can tell me i'm wrong in my prognosis] The choices are DOM Events (middle) or DOM Mozilla Extensions. tentatively picking the first.
Assignee: asa → joki
Component: Browser-General → DOM Events
QA Contact: doronr → vladimire
timeless, when you see focus, don't think brendan, think bryner. bryner, you wanna take this bug? /be
rats. still crashes me, win98SE 2001122703. My WFM above must have been a fluke. Just in case another talkback will help, TB996936G
The hazards of time-limited sales sites : The site referred to in this bug is now down, since the tickets are not available at this time. The site will re-open on 1st Feb 2002, and presumably close again once all the tickets are sold.
can't move on this w/ out repro test case.
Yeah, it's a real swine when they take the page away, isn't it? :( Well, the site is apparently opening again in a coupla days. I'll try to poke around then and see what happens. I'll try to make a standalone testcase if I get time.
works for me on linux (2002-02-04-03-trunk) and win2000 (2002-02-06-03-trunk)
Well, the site is operational again, but the page that caused the crash isn't there any more. This bug should probably be resolved->wfm, since there's no way to reproduce, unless any hardy soul reckons they can trace it from the talkbacks alone?
Yeah, this is why attaching testcases is often a good idea... resolving worksforme.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
Hello I was just trying to access the site as its back http://www.fifa-tickets.com/WebTCK_INS_Coll/startENG_2.htm but when i click on the link at the bottom i get this error "unknown socket type, loading aborted" Its odd, my mozilla 0.97 does not seem to work for any https site, i have my SSL proxy setup so I am surprised it does not work. Can anyone else access the site? another option is to use web.archive.org to get the pre 15th January version of this site JG
I just installed 0.98 and it does not crash anymore WFM
dont know why this is resolved wontfix, but verifying anyways
Status: RESOLVED → VERIFIED
Crash with Linux 2002031506 !! The site crashes again, with "Segmentation fault", either just clicking around on the page or clicking on "other" and trying to continue. No talkback appears. Somebody care to reopen ? And investigate further ? This will be a rather high visibility site.
WONTFIX have to be WORKSFORME (see comment #23), so REOPENING because still crashing (comment #25). Anybody have got fresh stacktrace?
Status: VERIFIED → REOPENED
Keywords: stackwanted
Resolution: WONTFIX → ---
Can someone make a test case? We should catch this bug before FIFA take the site down again. i tried wget -r https://www.fifa-tickets.com/webtck_INS/defaultENG.htm and got some files but i can not get my build to crash now! please can some one upload a zip/tgz of the files that make mozilla crash please? Regards JG
Once again, the procedure how to crash (Linux 2002031808): - Click 3 times on the background in the left frame (below "Ticketing Application"), - Try to change "country of residence" in the right frame. After a couple of seconds Mozilla crashes. Infinite recursion ? I18n ? I'll try to produce a reduced testcase (got the files).
Reduced testcase, crashes for me on Linux 2002032306. (Apologies for posting inline, attachments are so inconvenient for frames.) Main file, index.html: <html> <head> <title>Bug_116206_testcase</title> </head> <frameset cols="276px, 1*" > <frame name="frame1" src="frame1.html" > <frame name="frame2" src="frame2.html" > </frameset> </html> File frame1.html: <html><head> <script language="JavaScript"> document.onMouseDown = _MouseDown; function _MouseDown(e) { var clickType = e.which; if (clickType!=1) return false; return true; } </script></head> <body bgcolor="#882994"> <table width="270" align="left"> <tbody><tr> X </tr> </tbody></table> </body></html> File frame2.html: <html><head> <script language="JavaScript"> function InitialFocus(){ document.frmSelectUser.radResidence[0].focus(); } </script></head> <body bgcolor="#88d77b" onfocus="javascript: InitialFocus();" > <form id="frmSelectUser" name="frmSelectUser" method="post"> <table width="460"> <tbody> <tr> <td width="20"><input class="input" name="radResidence" type="radio" value="KOR"></td> <td width="400" align="left">Korea Republic</td> </tr> <tr> <td width="20"><input class="input" name="radResidence" type="radio" value="JPN "></td> <td width="400" align="left">Japan</td> </tr> <tr> <td width="20"><input class="input" name="radResidence" type="radio" value=""></td> <td width="400" align="left">Other</td> </tr> </body></html> Click once on the background of the right frame, click three times on the left frame, try selecting radio buttons in the right frame. Crash. DOM Events, apparently.
I can confirm that the files in comment #29 will reproduce the crash with Mozilla 1.0rc1 {Build ID: 2002041711} Debian Linux 2.4.17 kernel. This crash does not trigger talkback and gdb reported that the stack was 8731 frames long, so I am not attaching the output. Since there is a working testcase, perhaps the 'stackwanted' keyword should be removed.
Attached file reduced testcase (deleted) —
reduced testcase -- no frames. click on the second radio button -- hang (or crash if you wait long enough). the body has an onfocus handler that attempts to set the focus to the first radio button.
Attached file stacktrace (deleted) —
the part between the "-----------------" repeats indefinitely.
Attached file stacktrace (deleted) —
the part between the "-----------------" repeats indefinitely.
I submitted that once (although it took about 5 minutes to respond)! I've also noticed that the testcase works best if you open it from the commandline (to get the initial focus right). removing stackwanted keyword.
Keywords: stackwanted
Can somebody mark "testcase" ? This bug deserves attention, since the crash is still present in Linux 2002051009 RC2 branch, both on the URL and on the testcase in Comment #29. (I don't crash on the reduced testcase in the attachment, but I seem to remember that I crashed a couple of times too.) From what I can tell, there is some kind of race in focus setting, resulting in infinite recursion.
adding testcase keyword this is not getting attention because the fix is likely to be non-trivial and there are other nasty bugs people are working on for 1.0 also, the page is doing something a more than bit unusual. The standard way to do what it's trying to do would be to use onLoad instead of onFocus. onLoad's behavior is more in line with what they're trying to accomplish and would prevent the crash.
Keywords: testcase
the URL has changed again and the testcase worksforme with linux build 20020817. the relevant issues here are still covered in bug 137717
Worksforme with 1.1 branch build 20020824. (Also WFM with 1.1B back at least to build 2002072204.) Still crash with 1.0 branch build 2002082407, using my testcase in Additional Comment #29. I haven't checked on the trunk, but it is likely fixed too, considering that it works on 1.1 branch, and Additional Comment #37. I suppose this can be marked WORKSFORME (i.e. ignore the persisting problem on 1.0 branch). Any comments?
if this bug got fixed on the trunk, but 1.0 branch still crashes, it would be nice to get that patch onto the branch (assuming it would not cause other problems)
this was fixed on the trunk by the patch in bug 130969
WFM 2002120808, Windows 2000
1.0 branch only
Version: Trunk → 1.0 Branch
Priority: -- → P1
But will there really be a new Mozilla release from the 1.0 branch?
Not from mozilla.org. Move to the 1.4 branch if you're on the 1.0 branch for extra stability. /be
-> WORKSFORME
Status: REOPENED → RESOLVED
Closed: 23 years ago21 years ago
Resolution: --- → WORKSFORME
Version: 1.0 Branch → Trunk
Flags: in-testsuite+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: