Closed Bug 219149 Opened 21 years ago Closed 21 years ago

Mozilla hangs on international fonts

Categories

(Core Graveyard :: GFX: Gtk, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 136362

People

(Reporter: knitterb, Assigned: blizzard)

References

()

Details

(Keywords: hang)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Build Identifier: Mozilla 1.4 and Mozilla 1.5a When trying to access pages with international fonts, Mozilla hangs. This is reproduceable on XFree86 4.2.1 and 4.3.0. XFree86 4.2.0 appears to be fine. The XFree86 group suspects this may be a Mozilla issue and I need help finding where the hanging is so that I may help both the XFree86 group and the Mozilla group identify the issue. Reproducible: Always Steps to Reproduce: 1.Start Mozilla 2.Goto http://www.fsv.jp/ 3.Browser hangs Actual Results: Browser hangs Expected Results: Display the page either with the correct international fonts, or display ugly characters. I cannot get Mozilla to start in debug mode. Assistance is requested and I will do anything to provide you and the XFree86 group more information.
I have filed a complementary bug with the XFree86 group as bug number 628. http://bugs.xfree86.org/show_bug.cgi?id=628
I don't see the problem using the Mozilla 1.4 release and Red Hat's XFree86 4.3.0-2 RPMs. (Nor do I see the problem with an Xft build, but that's unrelated.) The appropriate component for this bug is the core X font code, which I guess means Gfx:Gtk.
Assignee: font → blizzard
Component: Layout: Fonts and Text → GFX: Gtk
are you using Xinerama by chance? (bug 136362) you can get a Mozilla stack with gdb (assuming you're not running RPMs) with: % mozilla -g -d gdb the stack will be more useful if you're not running a stripped binary build.
Keywords: hang
Xinerama? As in a bual head display. If so, yes I am running a dual head machine. I will attempt the steps in bug 136362 (on Monday) and see if that helps out: 1. disabling Xinerama (single display) 2. putting in prefs.js: user_pref("font.scale.aa_bitmap.enable", false); 3. configure/compile 1.4/1.5a with: --enable-xinerama 4. configure X to use fonts directly (not xfs) - How do I do this? Just add in all the FontPath entries that my xfs config uses? Thanks for a confirmation on item 4. And more to come on Monday. If this reports back as an issue, we can safely mark this as a duplicate of 136362, and I will reenter my notes over there at that time. Thanks, this is all great info. Have a great weekend. Cya Monday!
> 3. configure/compile 1.4/1.5a with: --enable-xinerama I believe that xinerama is enabled by default if it can find the libraries on your machine (which is "always"). You might try with --disable-xinerama > 4. configure X to use fonts directly (not xfs) - How do I do this? Just add in all the FontPath entries that my xfs config uses? right, add them to your XF86Config-4 file in place of the "unix/:7100" (xfs). your dual-head display is a useful tidbit you should share with the XFree86 folx
Depends on: 136362
I have found that the --xinerama option doesn't matter. The important factor is having a xinerama display (2 monitors). I have to run mozilla under VNC if there is any chance of hitting international characters (especially email because of all the foreign spam). :-(
Status: UNCONFIRMED → NEW
Ever confirmed: true
this should probably be a duplicate of bug 136362.
I was able to workaround (not a fix?) this issue by doing *either* of the two: 1) in my XF86Config-4, I simply set: Option "Xinerama" "false" 2) in my XF86Config-4, I removed: FontPath "unix/:7100" and set a bunch of FontPath entries which mirror my /usr/X11R6/lib/X11/fs/config Obviously step 2 was more usable as number 1 lead to no dragging between screens. I'll mark this as a duplicate of 136362 and post more notes over there. Thanks a ton for the help. *** This bug has been marked as a duplicate of 136362 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
No longer depends on: 136362
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.