Closed Bug 230215 Opened 21 years ago Closed 21 years ago

Mozilla crashes when I visit this web page

Categories

(SeaMonkey :: General, defect)

Other
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: chris, Unassigned)

References

()

Details

(Keywords: crash, stackwanted)

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031202 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031202 I'm using the DAG Mozilla 1.5 RPMS on a Fedora 1 box (with all the latest updates): $ rpm -qi mozilla Name : mozilla Relocations: /usr Version : 1.5 Vendor: Dag Apt Repository, http://dag.wieers.com/apt/ Release : 2.rhfc1.dag Build Date: Tue 02 Dec 2003 17:07:12 GMT Install Date: Mon 05 Jan 2004 15:40:30 GMT Build Host: localhost Group : Applications/Internet Source RPM: mozilla-1.5-2.rhfc1.dag.src.rpm Size : 39175153 License: MPL/NPL/GPL/LGPL Signature : DSA/SHA1, Tue 02 Dec 2003 22:47:35 GMT, Key ID a20e52146b8d79e6 Packager : Dag Wieers <dag@wieers.com> URL : http://www.mozilla.org/ Summary : A Web browser. Description : Mozilla is an open-source Web browser, designed for standards compliance, performance, and portability. The page that causes the crash is valid XHTML 1.0 served as text/html: http://validator.w3.org/check?uri=http%3A%2F%2Fwww.multikulti.org.uk%2F It also has valid CSS2: http://jigsaw.w3.org/css-validator/validator?uri=http%3A%2F%2Fwww.multikulti.org.uk%2F I _don't_ have a problem with Mozilla running in XP in VMWare (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007) and in addition this web site was developed using Mozilla... Reproducible: Always Steps to Reproduce: 1. Visit http://www.multikulti.org.uk/ 2. Browser crashes Actual Results: There is no output to the terminal I start Mozilla from when it crashes. Expected Results: Not crashed :-)
Keywords: crash
can you try latest XFT Firebird pre-0.8 build ? Simple tarball that can be in a dummy directory (I assume your build is XFT otherwise you can use Mozilla pre-1.6 nightly builds): http://ftp.mozilla.org/pub/mozilla.org/firebird/nightly/latest-0.8/ this may be bug 213734. If still crashing, please attach a stack trace by running 'mozilla -g' and 'bt' after crashing within GDB. do you have Microsoft .fon fonts in your fonts directories ? Does deleting (or archiving) them prevent from crashing ? Could be bug 180309.
Keywords: stackwanted
WFM Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7a) Gecko/20040106
Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7a) Gecko/20040107 It works for me.
I don't have any .fon fonts -- the following doesn't match anything: $ locate fon | grep -i fon$ The lastest Firebird doesn't crash: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6b) Gecko/20040106 Firebird/0.7+ I'll mail the freshrpms list about the linux rpm version that is crashing to see if others are having this problem.
does your 1.5 build crash on URL mentioned in bug 213734 ? http://4c.ucc.ie/~cbosch/mozcrash.txt
Blocks: xft_tracking
My DAG 1.5 RPM Mozilla does also crash on http://4c.ucc.ie/~cbosch/mozcrash.txt Also it has been suggested that upgrading from RedHat 9 to Fedora 1 might cause some fonts to be installed that cause crashes: http://lists.freshrpms.net/pipermail/freshrpms-list/2004-January/007117.html
can you attach a stacktrace from your 1.5 build ? if you're using the standard mozilla startup script, just do % mozilla -g -d gdb (gdb) run [wait for mozilla to crash] (gdb) bt (attach the output from "bt" via "create a new attachment") This could be related to bug http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=111973 too.
Sorry for being stupid but I don't understand how to do that stack trace, I can get this far: [chris@snowball chris]$ mozilla -g -d gdb [23]+ Exit 11 mozilla But I don't understand how to run the bt command?
This might be caused by a Chinese TTF -- I have been removing all the fonts installed on my system one-by-one and restarting xfs and then trying Mozilla and after removing this one: # rpm -e ttfonts-zh_CN-2.13-0 Mozilla no longer crashes :-)
I have just reinstalled the font that *appeared* to cause the problem (apt-get install ttfonts-zh_CN) but I don't have the crashes any more. These are all the font RPMS that I have removed: fonts-hebrew-0.80-1 fonts-ISO8859-2-100dpi-1.0-11 fonts-ISO8859-2-1.0-11 fonts-ja-8.0-9 fonts-KOI8-R-1.0-5 fonts-KOI8-R-75dpi-1.0-5 freebanglafont-0.5-1 taipeifonts-1.2-23 ttfonts-ja-1.2-29 ttfonts-zh_TW-2.11-22 XFree86-100dpi-fonts-4.3.0-42 XFree86-cyrillic-fonts-4.3.0-42 XFree86-ISO8859-14-100dpi-fonts-4.3.0-42 XFree86-ISO8859-14-75dpi-fonts-4.3.0-42 XFree86-ISO8859-15-100dpi-fonts-4.3.0-42 XFree86-ISO8859-15-75dpi-fonts-4.3.0-42 XFree86-ISO8859-2-75dpi-fonts-4.3.0-42 XFree86-ISO8859-9-100dpi-fonts-4.3.0-42 XFree86-ISO8859-9-75dpi-fonts-4.3.0-42 XFree86-syriac-fonts-4.3.0-42 And these are the ones I have left: bitmap-fonts-0.3-2 chkfontpath-1.9.10-2 fontconfig-2.2.1-6.1 fonts-ISO8859-2-75dpi-1.0-11 fonts-KOI8-R-100dpi-1.0-5 ghostscript-fonts-5.50-9 mplayer-fonts-1.1-2.fr tetex-fonts-2.0.2-8 ttfonts-ko-1.0.11-29 ttfonts-zh_CN-2.13-0 urw-fonts-2.1-5.1 xawtv-tv-fonts-3.88-6 XFree86-75dpi-fonts-4.3.0-42 XFree86-base-fonts-4.3.0-42 XFree86-font-utils-4.3.0-42 XFree86-ISO8859-2-100dpi-fonts-4.3.0-42 XFree86-truetype-fonts-4.3.0-42
out of curiosity: do you use apt-get (.deb Packages) and RPMs (not that this is generally wrong)?
apt (and yum) are used by _lots_ of people for updating Fedora and Red Hat boxes, in fact yum is now the official updater for Fedora, for more info see Freshrpms: http://www.freshrpms.net/ I have never tried installing a .deb on a Red Hat or Fedora machine. (Sorry for getting off-topic!)
WFM Linux gtk1 1.6 on SuSE 8.2 and Mandrake 9.2 xft/gtk2 1.4 release.
Hi I fixed this buy deleting my ~/.mozilla directory and upgradeing to the latest DAG RPM: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040124 Sorry not to have a more helpful bug report...
marking WFM as per reporter comments.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.