Closed Bug 539369 Opened 15 years ago Closed 15 years ago

The URL below (webaim.org...) crashes FF 3.5.7 and even the X server when opened (redhat 5.3)

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: bugzilla, Unassigned)

References

(
URL
)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 Build Identifier: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 That should be enough Reproducible: Always
Summary: The URL above crashes FF 3.5.7 when opened (redhat 5.3) → The URL below (webaim.org...) crashes FF 3.5.7 and even the X server when opened (redhat 5.3)
Using also Firebug (latest as of now)
Yes, the link http://www.webaim.org/techniques/javascript/eventhandlers.php&rct=j&q=javascript+handlers&ei=DzlNS53hO4yOkQWkrJmoDQ&usg=AFQjCNF0utaCF07qDXlfJaWhP-qH6qM0hw&sig2=-sWrPSMP_5J2RG1nvI48aQ gives a 404, in curl as well (as I don't have the time to see 404 in FF). In FF, crash occurs after 1-2 seconds, and the X server dies as well. (about:crashes gives nothing) Since X dies, I started FF from a console window (eg ^alt-F1) with the "--display=:0.0 -g" options. All threads seem to close "normally", and finally I get in the gdb console window: ---- Gecko: Fatal IO error 104 (Connection reset by peer) on X server :0.0 Thread 0x.... (LWP...) exited. Thread 0x.... (LWP...) exited. ... Program exited with code 01. ---- It doesn't seem to be a "crash" per say... but maybe a X server communication problem(?).
If you are talking about the X server, it's X Window System Version 7.1.1 :-) If we are talking about the video card and its drivers, this is the output from lspci -v 00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Unknown device 02e0 Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at fdf00000 (32-bit, non-prefetchable) [size=512K] I/O ports at ff00 [size=8] Memory at d0000000 (32-bit, prefetchable) [size=256M] Memory at fdb00000 (32-bit, non-prefetchable) [size=1M] Capabilities: [90] Message Signalled Interrupts: 64bit- Queue=0/0 Enable- Capabilities: [d0] Power Management version 2 In 6 months of use (RHEL 5.3, Dell Latitude), this is the *only* site that caused a problem...
*shrug*. http://viper.haque.net/~timeless/blog/143/ roughly speaking, the x11 server dropped your egg. sorry to hear that, but you're going to need to find someone on their side to ask them 'why did you drop my egg'.
Well... only one site is causing this. And the X server never got any weird behavior besides that problem from FF. So I thought it could be that FF is sending strange orders to the X server that may have him "giving up" (you know, like the equivalent of Control-Alt-Backspace which [if configured, and it is] kills X])
we really can't do anything w/o someone who understands that side explaining what's going on. contact red hat and ask them for help. if it turns out it's our fault, someone from their side will explain to us what we need to do.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
I see. No problem with me. FF is the *only* app that crashes X, and the URL above is the *only* URL that makes FF crash X. Sorry but I won't have time to debug it myself on the X side. I think my description of the problem should be enough to start a check on your side, possibly trying on RHEL 5.3 (with latest patches). As this very page itself is only made of some text, that is only rendered by FF, it seems clear that FF behaves strangely at some point with X.
Resolution: INVALID → WONTFIX
Not, WONTFIX. That is a peer decision. This is INVALID as it is not a bug in firefox.
Resolution: WONTFIX → INVALID
You need to log in before you can comment on or make changes to this bug.