Closed Bug 183750 Opened 22 years ago Closed 22 years ago

[Xft]? Open the above url and scroll down the source listing, at about line 265 the browser will crash.

Categories

(Core :: XUL, defect)

Product:
Core
Component:
XUL
Version:
Other Branch
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED DUPLICATE of bug 173204

People

(Reporter: meherenow, Assigned: blizzard)

References

(
URL
)

Details

(Keywords: hang) 

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021202
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021202

There's something wrong with the way mozilla handles
http://www.darkglobe.org/moz/check.html ironically this is the output from the
w3c's validator (validator.w3c.com) when pointed at www.redhat.com :o)

Reproducible: Always

Steps to Reproduce:
1. Click on above url
2. Scroll down to the source listing part of the page, continue scrolling until
you reach line 265 (ish)


Actual Results:  
The browser locks up horribly.

Expected Results:  
The browser should render the page without crashing.
Keywords: crash
WFM, day old trunk CVS, Linux.
Keywords: crash → hang
Version: Trunk → Other Branch
WFM, Mozilla 1.2.1, Linux
I can replicate the crash on a second machine, both are RH8 and both are using
the XFT rpm's.

One machine can be prevented from crashing by selecting the "fixed font" as
"courier 10 pitch" in the preferences section.
changing component
Assignee: asa → jaggernaut
Component: Browser-General → XP Toolkit/Widgets
QA Contact: asa → jrgm
Summary: Open the above url and scroll down the source listing, at about line 265 the browser will crash. → [Xft]? Open the above url and scroll down the source listing, at about line 265 the browser will crash.
and reassign
Assignee: jaggernaut → blizzard
Blocks: xft_tracking
Probably a dup of 

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