bugzilla.mozilla.org will be intermittently unavailable on Saturday, March 24th, from 16:00 until 20:00 UTC.

Javascript using i810 driver causes xserver lock




11 years ago
9 years ago


(Reporter: Michael Blinn, Unassigned)


1.5.0.x Branch

Firefox Tracking Flags

(Not tracked)





11 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv: Gecko/20070313 Fedora/ Firefox/
Build Identifier: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv: Gecko/20070313 Fedora/ Firefox/

Using the i810 XServer (diskless Dell Optiplex GX110) and loading a javascript/resource intensive page will cause the xserver to crash back to console. If I switch to virtual terminal while rendering occurs the crash does not occur, however reloading/navigating to the next page render will then cause a crash. Switching to another workspace during render still crashes. Disabling javascript will make the crash not occur.

Reproducible: Always

Steps to Reproduce:
1. Load Firefox
2. Open overstock.com
Actual Results:  
Back to console screen with "Please also check the logfile at /tmp/mnt/xorg.log for additional information. xserver failed, press <enter> to continue" - As I am in a terminal-server environment (LTSP.org), the console is completely locked and I cannot get to xorg.log


11 years ago
Version: unspecified → 1.5.0.x Branch

Comment 1

11 years ago
This problem also occurred in FC5 and

Comment 2

11 years ago
we have this issue on our terminals machines that are connected to a server (as part of the LTSP.org project).they all run X version 6.9 (was build on kernel 2.6.9) and the server runs X version 7.1.1 (fedora 6 distro)

running the terminals with i810 driver crashes the Firefox and the X as described  in the main bug report and on some other sites as well. disabling the JavaScript does not make any difference :-(

switching to vesa driver on the terminal's X solve the crashes.

the terminals machine are Compaq P3 64MB + intel 810 1MB vga card

Comment 3

11 years ago
Apologies. Turning off Javascript only delays the crash. The opening page of overstock.com _will_ open with javascript disabled, however the next click (I did 'Equipment') will cause the same crash behavior.

Comment 4

11 years ago
opening FF and immediately surfing to http://del.icio.us/myschool and pressing ANY link will crash the X

if i open a second Tab and surf to http://del.icio.us/myschool all goes well :-)
if i change the X driver to VESA all goes well too :-)

(on COMPAQ Celeron 430 + 65MB RAM + i810E 4MB RAM)

Comment 5

11 years ago
If "Xserver crash" means: screen shows random nonsense images, making all desktop unusable, then yes, I also experienced this problem many times and can provide URLs or downloaded HTML code to demonstrate the problem.

I cannot even use a console session, because the video chip gets so upset that they won't even display the login prompt. The "cleanest" way to recover that I found is to force a reboot using Ctrl-Alt-Del. When the BIOS kicks in with its welcome screen, I get a clear image again, probably because the video chip is reset at this point.

Is this really a Firefox problem? - Can a non-privileged process legitimately do something to the X server that causes it to fail? - Or is this actually a problem in X or even in the device driver, since it appears to occur only with i810?

Anything I can do to help (limited Linux knowledge here, but programming experience on other platforms)? - I'd appreciate this highly annoying issue to be solved soon.

(Dell Optiplex G110, 933MHz, 512MB)

Comment 6

9 years ago
This bug was reported using a version of Firefox that security and stability updates are no longer provided for.  All users are strongly encouraged to upgrade to Firefox 3 by selecting 'Check for Updates' in the Help menu or by going to http://www.mozilla.com/en-US/firefox/firefox.html

If you can no longer reproduce this bug using the latest Firefox 3.0.x version, please change the status of this bug to 'RESOLVED' 'WORKSFORME'.

If you can still reproduce this bug, please provide additional details to help resolve this issue.
Resolving as WORKSFORME.  If the issue appears in Firefox 3.5, we will reopen it.
Last Resolved: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.