Closed Bug 201459 Opened 23 years ago Closed 23 years ago

Mozilla crash if I try to enter http://xinehq.de

Categories

(SeaMonkey :: General, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 186704

People

(Reporter: tom.gufler, Assigned: blizzard)

References

()

Details

(Keywords: crash)

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030401 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030401 When I try to enter http://xinehq.de mozilla crashs. I have no problems on other sites(using mozilla 1.3 since release). Reproducible: Always Steps to Reproduce: 1. type xinehq.de into the navigation tool bar 2. press enter 3. Actual Results: mozilla close itself - no error message - no mozilla process running Expected Results: show the page
Sorry, I can't reproduce this with 2003040722 on Linux and 2003040908 on Win. No crash and no other problems. Maybe you try this again with a newer build.
Works fine for me too on Linux with cvs 20030410. You need to provide at least a stack trace by running mozilla under gdb if you want to figure out what your problem is.
I really want the locate the bug. Who do I provide a stack trace with gdb? I have already gdb installed?
Backtrace: ... [New Thread 344086 (LWP 8634)] [New Thread 360471 (LWP 8635)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 8611)] 0x40771b45 in XftLockFace () from /usr/lib/libXft.so.2
*** Bug 201589 has been marked as a duplicate of this bug. ***
the xinehq URL was reported to have the same problems in bug 186704, but the problem there was actually different (X error instead of seg fault). The XftLockFace crash is bug 183729. do you have any ttf fonts that are not world-readable?
Assignee: asa → blizzard
Blocks: xft_triage
Keywords: crash
This is what I get under gdb. (I don't have a build with debug information so this is all the information I have.) The program '<unknown>' received an X Window System error. This probably reflects a bug in the program. The error was 'BadIDChoice (invalid resource ID chosen for this connection)'. (Details: serial 12087 error_code 14 request_code 1 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... Program exited with code 01.
No, I have no fonts that are not world(if you mean system wide) readable and I didn't install new fonts in the last 2 months. But I found an other problem: I upraded my system with freetype 2.1.4 and xft-2.0.1-r2(gentoo) and from that time I got the crashs. Today I reinstalled fontconfig and my problems are gone. So this could be a gentoo specific problem where you have to re-emerge fontconfig after upgrading freetype and/or xft.
I'd just like to confirm the bug, as it just happened to me; the web page opens fine in lynx. I get the same error tajohnson did when I run mozilla from the command line. I am using the latest Debian package of Mozilla, Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030327 Debian/1.3-4. This is most frustrating.
the problem tajohnson and Rick are seeing is bug 186704 and is actually a bug in X, not Mozilla. Thomas might not have been seeing that bug, but it's working for him now, so there's much use in trying to diagnose it. marking dupe *** This bug has been marked as a duplicate of 186704 ***
No longer blocks: xft_triage
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.