User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051216 Fedora/1.5-3 Firefox/1.5 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051216 Fedora/1.5-3 Firefox/1.5 Using a pango enabled firefox, if the SIL graphite pango modules are installed - the website listed in the URL crashes firefox. Uninstall the SIL graphite pango modules, and the browser does not crash (but also doesn't render the IPA) Reproducible: Always Steps to Reproduce: 1. Install the silgraphite pango modules 2. Install the Doulos SIL ttf font 3. visit http://www.travelphrases.info/gallery/Test_IPA.html Actual Results: Mozilla crashes Expected Results: No crash, proper rendering of the IPA text I'm running Firefox in Fedora Rawhide, up2date - firefox-1.5-3 (x86 32-bit) The pango modules are from http://mpeters.us/silgraphite/ (for non Fedora - you need the svn checkout from http://sourceforge.net/projects/silgraphite/ - build + install library, build + install the pango wrapper, register wrapper with pango) -=-=- I'd love to give a gdb backtrace - but I can't figure out how to get gdb to run firefox. When I try: gdb /usr/lib/firefox-1.5/firefox-bin it informs me that libmozjs.so can't be loaded (I guess it needs the wrapper shell script to set some stuff) -=- The pango wrapper works with other pango enabled software, only firefox (at least that I've tried) crashes.
./run-mozilla.sh -g -d gdb ./firefox-bin please read the unix debugging faq
I can reproduce this bug on a machine running the latest Debian unstable packages. Another URL which results in a segfault is http://en.wikipedia.org/wiki/Dash
still see this problem? if not please close this bug accordingly (probably worksforme)
http://google.us/codesearch/p?hl=en#YhhfyXiTacI/wrappers/pangographite/graphitecache.cpp&q=graphite_GetLogAttr&exact_package=svn://scripts.sil.org/graphite/graphite/trunk so... this code isn't in our tree. someone should figure out if it's relevant and send it to whomever owns pangographite.
No reply, INCO. Reporter, please reopen this bug if you can see this issue with Firefox 3.5 or later in Firefox Safe Mode (http://support.mozilla.com/kb/Safe+Mode) or a new profile (http://support.mozilla.com/kb/Profiles)