179369 - excessive resource consumption at specific URL, Xlib: Maximum number of clients reached

Status: RESOLVED WORKSFORME

(SeaMonkey :: General, defect)

Description

[Holger Marzen]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.1) Gecko/20020826

When I sorft to the page http://www.innen.saarland.de then mozilla grows to more
than 100 MB and gets slow (machine is Celeron 1700 with 256 MB AM). Additionally
no other X client can connect to the X-server (xfree 4.1.0) until Mozilla is
closed. X clients get:

hm@maus:~$ xclock
Xlib: connection to ":0.0" refused by server
Xlib: Maximum number of clients reached
Error: Can't open display: :0.0

Additional info:
lsof shows more than 1400 lines of the kind
mozilla-b 5776   hm  mem    DEL        0,5         134545687 /SYSV00000000








Reproducible: Always

Steps to Reproduce:
1.http://www.innen.saarland.de
2.try to start any X client, e.g. xclock
3.Xlib: Maximum number of clients reached



Expected Results:  
Use fewer resources. Konqueror shows tha page without any problems.

Comment 1

[Boris Zbarsky [:bzbarsky]]

worksforme, linux trunk build 2002-11-01-21.  1.1 is very old; please test with
a newer build....

Comment 2

[Holger Marzen]

Got build 2002101612 today. Fresh install, no plugins. Same results, sorry.

Comment 3

[Boris Zbarsky [:bzbarsky]]

Do you have any cookies set for the site?  Which exact build are you using (SEA?
 Installer?  .tar.gz?  rpm?  xft-enabled?).  What X server version?  Are you
using a font server?

Comment 4

[Holger Marzen]

I installed mozilla-i686-pc-linux-gnu-1.2b-sea.tar.gz on my Debian Woody with
xfree 4.1.0. No font server, but pixel, type1 and truetype fonts.

Comment 5

[Holger Marzen]

When I comment out the TrueType-dir from the font path then I have no problem.
Must be a problem with the many truetype fonts. But what does it trigger?

Comment 6

[Holger Marzen]

I used another set of TrueType fonts, the one from my Windows XP.
No problems with Mozilla.

Maybe some of the fonts were buggy.

Let's close this bug.

Comment 7

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

as requested