Bug 426685
| Summary: | firefox hangs in on bugzilla query page | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | John Ellson <john.ellson> | ||||||||||||
| Component: | firefox | Assignee: | Gecko Maintainer <gecko-bugs-nobody> | ||||||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||
| Priority: | low | ||||||||||||||
| Version: | rawhide | CC: | ajax, mcepl, selinux | ||||||||||||
| Target Milestone: | --- | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | x86_64 | ||||||||||||||
| OS: | Linux | ||||||||||||||
| URL: | https://bugzilla.redhat.com/query.cgi?format=simple | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2008-02-16 18:32:56 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
John Ellson
2007-12-24 11:57:59 UTC
This happens for me if I'm using the nv driver. If I switch to the vesa driver, I don't hang... I'm using GeForce 7600GT with the NVidia 169.07 drivers on kernel-2.6.23.9-85.fc8 with xorg* from fc8. I know, I'm a bad boy ;) I'm relieved you were able to recreate the bug with the nv drivers. Can you try the mesa and nv drivers for reference? Does nv help? Does mesa help? This could be a driver issue... I assume you meant "vesa", not "mesa" ?
I get the same problem with: nvidia, nv, and vesa drivers.
If I wait long enough (~2min) the "component" box on the web page get bigger
with some text in it, but greayed out still. if I wait longer still (+~2min) I
get the error popup:
A script on this page may be busy, or it may have stopped responding.
You can stop the script now, or you can continue to see if the script
will complete.
Script: https://bugzilla.redhat.com/js/product_query.js:53
This happens with all three drivers.
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach your X server config file (/etc/X11/xorg.conf) 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. Could you please also try to run without any /etc/X11/xorg.conf whatsoever and let X11 autodetect your display and video card? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please. We will review this issue again once you've had a chance to attach this information. Thanks in advance. Created attachment 290657 [details]
/etc/X11/xorg.conf
Created attachment 290658 [details]
/var/log/Xorg.0.log (nvidia)
Created attachment 290659 [details]
/var/log/Xorg.20.log (nvidia)
Created attachment 290660 [details]
/var/log/Xorg.21.log
confirming that the problem still occurs with firefox-3.0-0.beta2.4.fc9.x86_64 will do the fresh /etc/X11/xorg.conf next... Created attachment 290663 [details]
/var/log/Xorg.0.log - using automatic configuration
Same browser problem still exists with the automatic configuration (which only finds one of the two monitors, but I guess you know that.) top says that although ff3 is using astonishing amounts of X CPU time normally, when this hang happens it's all in firefox. *** Bug 431078 has been marked as a duplicate of this bug. *** Minor shenanigans ensue trying to get usable xulrunner-debuginfo. Still looking into it... Ajax, unless you violently oppose to the idea (and reopen this bug) I am closing this as duplicate of bug 431162 *** This bug has been marked as a duplicate of 431162 *** |