152823 - Visiting www.novatv.nl crashes my X-server

Status: RESOLVED WORKSFORME

(SeaMonkey :: General, defect)

Description

[Wim van Cappellen]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020529
BuildID:    2002052918

If I visit http://www.novatv.nl mozilla crashes my X-Server before anything is
displayed (white screen). X Server is XFree86 4.1.0 running on Suse Linux 7.3. 
The X-Server log file shows the following:

Fatal server error:
Caught signal 11.  Server aborting

Due to the X-server crash, all data in other applications/documents is lost.

Reproducible: Always
Steps to Reproduce:
1.Visit http://www.novatv.nl
2.
3.

Actual Results:  X-Server dies completely, automatically restart and prompts
with kdm login screen.

Expected Results:  Show the page correctly, not crashing my X-Server.

It seems that www.novatv.nl uses BrowserHawk.

Comment 1

[Frederic Bezies]

WFM using build 2002061806 - WinXP.

Comment 2

[Andrew Schultz]

you might be seeing bug 150339, which was recently fixed.

Comment 3

[Tim]

Works for me, Debian/sid, Athlon, Xfree 4.1.0 (I use xfstt but get most fonts
direct from X--the server is last in line for font retrieval).
2002061708 (trunk), Shockwave Flash 5.0 r47 plugin

Note to testers that you have to accept its cookies to view the site (ugh). 
Also, it's got (at least) flash content.

Reporter: can you give more details about your X setup?  Are you using a
separate font server?  As a side note, X getting a sig11 (segmentation fault)
seems to imply the problem is not with Mozilla.  Does that site work in other
browsers (mozilla-based galeon, konq, etc.)?

Also, indicate what plugins/versions you have (about:plugins).

RE: comment 2, the page doesn't utilize any large font sizes (also, bug 150339's
effect was filling memory, not segfaulting).

Comment 4

[Andrew Schultz]

actually, bug 150339 was an abort (although it probably fixed other problems
that might have included memory usage), but that is also inconsistent with the
signal 11.  The URL redirected a lot before it ended up somewhere and I thought
that an intermediate page might have had large fonts.

Comment 5

[Wim van Cappellen]

Accepting all cookies from the site solves the crash. The content is displayed
correctly, including the flash content.
If I reject all cookies from the site, the X-server crashes.

Following plugins are installed:
Java(TM) Plug-in 1.4.0_01-b03
Default Plugin
nppdf.so (Acrobat 5)
Shockwave Flash 5.0 r48
RealPlayer(tm) 7.0 LiveConnect-Enabled Plug-In

Viewing the site with Netscape 6.1 (Mozilla/5.0 (X11; U; Linux i686; en-US;
rv:0.9.2) Gecko/20010726 Netscape6/6.1) results in what seems an infite loop of
redirections (this seems to be a problem of the site). The screen remains white.
However, the X-Server does NOT crash.

Konqueror (with KDE 2.2.2) shows same result as Netscape 6.1 (infite loop), also
does not crash X-server.

About the font server: I am not aware of running a separate font server, but how
can i check?

Comment 6

[Aleksey Nogin]

WFM on Red Hat Linux 7.2 using BuildID 2002061018 (trunk)

Comment 7

[Tim]

Wow.  The HTML that pours from that site is rich with such gems as NOSCRIPT and
DIV tags outside of the BODY, search engine spoofers, and a form that
auto-submits from the onload routine.  I can't isolate any abuse of font
settings on the redirecting sites.

Also, WFM 2002061908/trunk, Debian/sid. I sat there for 5 minutes letting it
redirect (cookies set to reject). Memory usage steadily rose, but only in a
minor way (at a rate of less than 0.6%/minute on my machine with 256MB of RAM).
 After that, I tried it with other browsers and observed the same behavior
(infinite loop) in Galeon, Konqueror, and W3m (though w3m noticed the loop and
stopped).

I experienced no crashes.

RE: how to check for a font server, check the output of 'ps ax' for some
variation of /usr/(...)/bin/xfs (mine is xfstt). If you don't find something,
you probably aren't using a font server.

Comment 8

[R.K.Aa.]

WFM, current CVS, Linux.

Comment 9

[Tim]

Reporter: can you still reproduce this?  It's been here a while and it seems
that nobody else can reproduce it.

Comment 10

[Matthias Versen [:Matti]]

-> wfm

Comment 11

[Wim van Cappellen]

Upgrading to Mozilla 1.1 (Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1)
Gecko/20020826) solved the problem for me.
(I was not running a font server).

Wim.