Bug 486675
Summary: | Firefox exits on an X error for no particular reason | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Derek Atkins <warlord> | ||||||||||
Component: | cairo | Assignee: | Behdad Esfahbod <behdad> | ||||||||||
Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
Severity: | medium | Docs Contact: | |||||||||||
Priority: | low | ||||||||||||
Version: | 10 | CC: | behdad, gecko-bugs-nobody, hugh, mcepl, walters | ||||||||||
Target Milestone: | --- | ||||||||||||
Target Release: | --- | ||||||||||||
Hardware: | All | ||||||||||||
OS: | Linux | ||||||||||||
Whiteboard: | |||||||||||||
Fixed In Version: | 1.1.91-6.fc10 | Doc Type: | Bug Fix | ||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2009-05-09 04:21:51 UTC | Type: | --- | ||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||
Documentation: | --- | CRM: | |||||||||||
Verified Versions: | Category: | --- | |||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
Embargoed: | |||||||||||||
Attachments: |
|
Description
Derek Atkins
2009-02-20 22:37:39 UTC
Well, firefox isn't calling exit directly. That's coming from gdk_x_error since there's an X error. Any application that encounters one will exit like you see. It's like a result of a real bug in Firefox, but finding the cause of the X error will be a little tricky.... Can you quantify lots of windows? Also, if you can run firefox with the --sync command line option, and then break on gdk_x_error and provide a backtrace there, it would be a little more useful. (Please provide it as an attachment, not as a comment if you can). Lots of windows == 56 Total tabs... probably around 200 or so. Next time it crashes I'll run with --sync and set that breakpoint. I presume this will make performance suck hairy monkey balls? I was breaking on exit to get that last backtrace, but I can break in gdx_x_error instead. And sure, I can attach instead of comment. Created attachment 333095 [details]
backtrace from gdk_x_error with firefox --sync
It took a LOT longer to exhibit this problem under --sync, but I did eventually trap a call to gdk_x_error. Here's the full backtrace and the error.
Looks like X issue. Could we get more information on that side of your computer? Please attach your X server config file (/etc/X11/xorg.conf, if available) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. Thanks in advance. Created attachment 333128 [details]
X.Org conf file
Created attachment 333129 [details]
Xorg Logfile
Done. Heres the Xorg.conf and most recent Xorg.0.log file. Created attachment 333171 [details]
Another backtrace from gdk_x_error
This looks like a slightly different backtrace. I also ran firefox from the commandline and got some interesting output:
The program 'firefox' 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 258810104 error_code 14 request_code 149 minor_code 4)
(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.)
Per discussion on IRC reassigning to cairo. I keep getting firefox terminating with the BadIDChoice message (Fedora 10 x86_64). The good news is that there is a fix. The BadIDChoice error is a bug in libxcb. I think that this means that either there are multiple bugs in this bz or cairo is the wrong assignment. Please see upstream: http://bugs.freedesktop.org/show_bug.cgi?id=20254 (I started that one to record information discovered elsewhere.) An actual fix exists. This has more activity: https://bugzilla.mozilla.org/show_bug.cgi?id=458092 I also think that this bz is a different program provoking the same bug: https://bugzilla.redhat.com/show_bug.cgi?id=458657 I've created https://bugzilla.redhat.com/show_bug.cgi?id=494091 against libxcb. There is a chance that some of the reports in the current bz entry are for a different problem. FYI, I've been running firefox against a libxcb with the patch in bug #494091 and I haven't seen an X Protocol Error. I highly recommend getting this patch into libxcb, because it does seem to work for me! libxcb-1.1.91-6.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/libxcb-1.1.91-6.fc10 libxcb-1.1.91-6.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update libxcb'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-3865 libxcb-1.1.91-6.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report. |