Closed Bug 206993 Opened 22 years ago Closed 22 years ago

Crashes while page loads. You can see the site come up with images and text, then suddenly it crashes.

Categories

(Core Graveyard :: GFX: Gtk, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 180309

People

(Reporter: dhuv, Assigned: blizzard)

References

()

Details

(Keywords: crash, stackwanted)

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030313 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030313 It is something with the pages at http://www.news.com and http://www.zdnet.com I have tried looking at the source and have not found anything yet. This only happens when mozilla 1.3 or firebird 0.6 had xft enabled. Without xft the page loads fine and everything is normal. Reproducible: Always Steps to Reproduce: 1. install mozilla or phoenix with xft enabled on any linux system 2. go to http://www.news.com 3. or go to http://www.zdnet.com Actual Results: Browser crashes during the page load. Expected Results: Render the page and not crash. This only happens when you have xft enabled.
please try again with latest 1.4 build.
Severity: normal → critical
Keywords: crash, stackwanted
If Mozilla still crashes, please provide Talkback incident ID or stacktrace...
Mozilla still crashes (CVS build from yesterday). Tried to figure out how to create a backtrace of mozilla without success. Which PID should I hook gdb to (first, last or someone else of those 5 that gets started)?
With your debug build (given you didn't compile with --disable-debug), start Mozilla with "mozilla -g" then "run" and "backtrace" when it crashes.
for me, Mozilla can't resolve www.news.com or www.zdnet.com (although lynx works fine) if you're using the RPMs, "mozilla -g" won't work. you can attach gdb to the first process. xft only ==> gtk
Assignee: dom_bugs → blizzard
Component: DOM HTML → GFX: Gtk
QA Contact: desale → ian
Probably a dup of an existing xft bug. Please make sure that you don't have any font files that aren't world readable in your font path. Also, make sure you don't have any .fon files in your path. Also check the output of: NSPR_LOG_MODULES=XftFontLoad:5 ./mozilla That will give you a clue as to which font or set of fonts is causing problems.
Blocks: xft_triage
Im not sure what I should be looking for, the last output from mozilla was: matched the following (1) fonts: MS Sans Serif "MS Sans Serif" is a very common font, and was listed several times without crash. I tried to do a debug enabled build, but it failed early during compilation with a missing "__strcpy_small" error. Retried the build after a "make clean" and a "make distclen", both builds failed with exactly the same error.
Thanks for the details, please reopen if you disagree. Getting read of this .fon file should workaround the crash. *** This bug has been marked as a duplicate of 180309 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
I must disagree, or I missread the fontconfig bugzilla. This bug was in the 2.1x serie, Im using fontconfig 2.2 ("fc-cache -V"). Still, *I think*, Mozilla should not crash on bogus response from fontconfig. And whats on these pages that make mozilla use 100% CPU (Ive no plugins installed).
Ehh I should have tested before posting. After removing ""sserife.fon" and "sseriff.fon" Im able to load these two URLs. Still *I think* Mozilla should survive a bad (?) ".fon" file. Sorry for the noise.
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.