Closed Bug 268052 Opened 20 years ago Closed 19 years ago

css font-size: 10000% causes browser window to close

Categories

(SeaMonkey :: General, defect)

Product:
SeaMonkey
Component:
General
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 192397

People

(Reporter: hopeful.maverick, Unassigned)

Details

(Keywords: crash) 

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040917 Firefox/0.9.3
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040917 Firefox/0.9.3

cascading style sheet _files_ with font size of "10000%" (or over) cause the
firefox browser window to close, i'm not sure if css rules in the head or body
of the html file is the same (havnt checked.. very busy).

Reproducible: Always
Steps to Reproduce:
1. create a simple html file with a table
2. make an external cascading style sheet and try the css rule: table {
font-size:  10000%; }
3. make the simple html file use the stylesheet and load the page.

Actual Results:  
the browser window closed

Expected Results:  
ignored the css rules and informed me of the error perhaps

firefox version: 0.9.3
distribution: Debian Testing 3.1 (Sarge)
I tried to create the described testcase, but current Linux trunk does not crash.
Component: Web Site → DOM: CSSOM
Product: Firefox → Browser
Summary: css font percentage browser window to close → css font-size: 10000% causes browser window to close
Version: unspecified → Trunk
worksforme with linux trunk 2004110605 and FF 1.0rc1
you're probably seeing bug 192397.  you'll need to get a stacktrace.
also please attach html that does crash for you.
Assignee: bugs → general
Component: DOM: CSSOM → Browser-General
Keywords: crash
QA Contact: general
ah yeah, sorry about that i was a little rushed at the time, try
http://www.atda31.dsl.pipex.com/closewindow.html,
it could be Debian specific.
this also seems to affect mozilla 1.7.3.. i don't get you on the stacktrace
thing.. let me know how that goes if you can't reproduce this, i've let the
debian package maintainer know about the problem too.
the bug does occur with the official linux build
To be more precise, it says:
The application 'Gecko' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
what version of X are you running?
XFree86 version 4.3.0.dfsg.1-8, being a 4.3.0 deeply modified by Debian ; the
one currently in sid and probably in sarge as well.
No crash with comment 3 URL with gtk2+xft 2004110621 trunk on SuSE 9.1/XFree86
4.3.99
No crash with comment 3 URL with FF nightly 20041106 on SuSE 9.1/XFree86 4.3.99
Yeah, Sarge is using the same version of XFree86
ok, i just tried it on tonights build with --sync, still closes: 

The program 'firefox-bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadLength (poly request too large or internal Xlib length erro'.
  (Details: serial 8822 error_code 16 request_code 139 minor_code 20)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Product: Browser → Seamonkey
hmm actually the fix mentioned in 
<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=192397">bug 192397</a> for
 /etc/fonts/fonts.conf seems to have to worked.
Note that the same thing happens with html code like
<html><body><big><big><big><big><big><big><big><big><big>BANG</big></big></big>
</big></big></big></big></big></big></body></html>

i.e. the problem is with requesting too big font sizes.
dupe of "Font sizes over 300pt crash mozilla built with xft and gtk2"

*** This bug has been marked as a duplicate of 192397 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.